The News, Explained
On October 30, 2026, Microsoft announced new Windows 11 Insider preview builds. Beta-channel build 26220.9836 includes separate camera, microphone and location permissions for individual desktop apps. Insider is Microsoft’s program for testing features before a stable release; this announcement concerns those preview builds. Source Source
Desktop apps are traditional programs installed on a PC. Microsoft says access for these applications previously used a single device-wide setting. The new build lets users allow or deny access app by app. Source
The release notes point to Camera, Microphone and Location under Settings > Privacy & security. Apps that have not accessed a resource before prompt for permission when first requesting access. Source
Existing decisions are preserved. Previously allowed apps remain allowed, and previously denied apps remain denied. Settings are not reset, and existing enterprise policies continue to work. Microsoft says it is exploring additional management capabilities. Source
App names have limitations. Programs relying on shared system components or browser-hosted experiences may appear under a different name than expected. The notes say an app may appear as “Unsigned” when Windows cannot verify publisher information. That label describes the verification status of publisher information. Source
This Beta build is based on Windows 11 version 25H2 through a package that enables features. Preview features may change, be removed or never reach a stable release. Some may not yet be fully localized, and the notes provide no stable-release date. Source
OYOPICK’s Take
App-specific permissions could help users connect a task with the access they want to grant. As a hypothetical use, someone could allow camera access for a video-meeting program while reviewing other programs separately.
For those choices to be easy, the relationship between names in the permission list and installed apps needs to be clear. The documented possibility of unexpected names caused by shared components matters here. Alongside preserving previous decisions, we would like clearer explanations of which app accessed a resource through which component. Whether the feature reaches a stable release will depend on future testing and Microsoft’s subsequent announcements.