Windows 11 is gaining a long-requested privacy upgrade. According to reporting from Windows Central, a new capability hidden inside the latest Experimental Insider Build 26340.9212 allows users to block camera and microphone access on a per-app basis for Win32 programs. This shift closes a notable gap in Windows privacy controls, bringing desktop app management closer to the granular toggles found on iOS and Android.
What Exactly Is Changing About Per-App Camera and Mic Permissions
For years, Windows 11 has offered privacy switches for system sensors like the camera and microphone. However, those controls were historically split by application type. UWP and MSIX applications could be managed individually, while traditional Win32 programs operated under a single, system-wide toggle. If you granted Chrome permission to use your webcam, every desktop application on your machine received the same access.
The update in Build 26340.9212 changes that architecture. Insiders running the Experimental channel can now revoke sensor access for specific Win32 applications directly from the Privacy & security settings panel. The change was first reported by X user @jakub25050, who noted the toggles appeared without requiring any additional configuration. Windows privacy researcher @phantomofearth independently verified the behavior, though they noted the feature requires enabling the Win32SignatureIdentity feature flag (ID 60730253) to activate. Microsoft has not mentioned the addition in the official release notes for the build, which began rolling out to Experimental channel Insiders on August 17, 2026.
Why This Shift Matters for Desktop Software
The distinction between UWP and Win32 has been a persistent friction point for Windows privacy advocates. Win32 encompasses the vast majority of legacy and modern desktop software, including web browsers like Google Chrome and Microsoft Edge, communication tools like Discord and Slack, and gaming platforms like Steam and Epic Games Store. Previously, these applications bypassed individual sensor controls entirely.
By extending granular toggles to Win32 executables, Microsoft is aligning Windows with mobile operating systems that have enforced app-specific privacy controls for years. Android and iOS require permission grants at the application level, and users quickly grew accustomed to denying background access to location services, cameras, and microphones. Windows is now adopting the same philosophy for desktop software.
From a technical standpoint, this requires Windows to track application identity at a deeper level. The reliance on the Win32SignatureIdentity flag suggests Microsoft is using code signing and package identity metadata to differentiate between trusted and untrusted Win32 processes. This approach mirrors how modern Windows security features validate software origins before granting elevated access, and it signals a broader move toward identity-based permission enforcement across the operating system.
What This Means for You
If you regularly switch between video calls, browse the web, or run background utilities, this change directly impacts your daily privacy posture. You will no longer need to choose between letting your browser use the webcam and accidentally granting that access to every other program running on your system. Applications that previously required system-wide sensor approval can now be restricted to a single, approved program.
For users who rely on virtual cameras, streaming software, or cross-platform communication tools, the ability to lock down microphone access on a case-by-case basis reduces the risk of unintended audio capture. It also simplifies troubleshooting. If an application begins recording video or audio without your consent, you can immediately identify which program bypassed your settings and revoke its access without disrupting other software.
How to Get It
The feature is currently available only to Windows Insider Program participants in the Experimental channel. To test it, you will need to run Build 26340.9212 or newer. If the toggles do not appear immediately after updating, you may need to enable the Win32SignatureIdentity feature flag through the Windows Insider settings or a registered system policy, depending on your channel configuration.
Microsoft typically stages privacy-related updates across the Insider rings before pushing them to the general public. Assuming the feature passes stability and compatibility testing, it will likely move through the Dev channel, then the Release Preview channel, before arriving in a future cumulative update for Windows 11 home and professional editions. Until then, the Experimental channel remains the only official path to access the new per-app camera and mic permissions.
Source: Latest from Windows Central
Build details:
- build 26340.9212
Over to you: Will you rely on the new per-app toggles, or do you prefer keeping system-wide sensor controls for simplicity?
