Windows 11 Experimental build finally toggles Win32 camera access app by app

Windows 11 Experimental Build 26340.9212 now lists individual desktop apps such as Edge and Brave with their own camera, microphone and location toggles in Settings, ending the old all-or-nothing desktop bucket. The change arrived without any mention in Microsoft’s notes and still reaches only some Insiders.

Store apps have carried per-app switches for years. Traditional Win32 programs sat behind one shared control. That gap is closing in testing, and the deeper effect is Windows starting to treat open desktop software more like sandboxed Store apps.

What the new privacy page actually shows

On machines that received the feature, the single “Let desktop apps access your microphone” switch disappears. Edge, Brave and other Win32 titles appear as separate rows at the top of the same list that holds Teams, the Camera app and Xbox. Each gets its own on/off control.

Camera and location pages behave the same way. WindowsLatest confirmed the layout with Edge and Brave on an Experimental Insider PC. Neowin saw the same pattern and noted voice activation also falls under the new model.

• Before: one shared desktop-apps toggle controlled every Win32 program at once.
• After: each detected desktop app sits as its own entry with a dedicated switch.
• Permission prompts now appear as centered system dialogs the first time a desktop app requests camera or mic access.

The shared toggle that once applied to everything is simply gone on affected builds. Users can allow Discord while blocking Chrome without third-party tools or registry edits.

The practical layout change is modest on the surface. The same Settings pages remain. The difference is that Win32 titles no longer hide under a single master control; they share the main list with Store apps and first-party tools. That single visual shift is what makes selective allow and deny possible from the UI alone.

How the old and new controls compare

Microsoft’s own support pages still describe the pre-change world. Desktop apps “cannot be individually toggled,” and the master switch affects every listed program. The Experimental build quietly rewrites that rule for cameras, microphones and location.

The official camera and microphone privacy settings page continues to warn that turning off the desktop master switch can break features such as dictation. The new model keeps those system components separate while giving users finer choices for third-party software.

Support documentation lagging the Experimental build is normal. Insiders see behavior the public pages still deny. Until the notes catch up, the table above is the clearer guide to what the build actually does on machines that have the feature.

The 1903 list that never let you flip the switch

Desktop apps have appeared in a list under the shared toggle since Windows 10 version 1903. Users could see which programs had touched the camera or mic and even open the exact file path. They just could not allow one and deny another.

1. May 2019 (1903): Microsoft added the desktop-apps list and master switch for camera and microphone.
2. Windows 11 launch era: Store apps kept full individual controls; Win32 stayed grouped.
3. 2026 Capability Access Manager issues: the same component that logs these permissions ballooned to hundreds of gigabytes on some PCs.
4. 17 August 2026: Build 26340.9212 ships to Experimental Channel; per-app toggles surface for some Insiders.

Rafael Rivera, a longtime Windows researcher, pointed out the continuity on X. The list itself is old. The ability to toggle each entry individually is the new piece.

Err, this has actually been in the OS since Windows 10, 1903 give or take.

Rivera followed up that the real distinction now appears to involve signed versus unsigned apps, though he questioned the value when checks still run in-process and land in the current-user registry hive.

In other words, Microsoft spent years showing users which desktop programs had touched sensitive hardware without letting them act on that list entry by entry. Build 26340.9212 finally attaches a switch to names that were already visible. The continuity Rivera noted is why the change feels both overdue and familiar at once.

Permission prompts and the signature flag

When a desktop app first reaches for the microphone or camera, Windows now shows a centered dialog asking for permission. That prompt was previously rare or absent for classic Win32 software. Jakub, who first publicized the change, posted screenshots of both the toggles and the new dialogs.

Not every Insider on 26340.9212 sees the feature. Phantomofearth reported it appeared only after enabling the feature flag Win32SignatureIdentity (60730253). Jakub saw it without manual enablement. The uneven rollout matches Microsoft’s usual Controlled Feature Rollout pattern for Experimental builds.

The signature angle raises a practical split. Signed apps from known publishers may receive cleaner identity and cleaner toggles. Unsigned or side-loaded tools could stay harder to manage or easier to bypass if the checks remain in-process. That detail is still unconfirmed in any Microsoft documentation.

• Centered allow or deny dialogs now meet first camera or mic use by a desktop app.
• Win32SignatureIdentity (60730253) is the flag tied to the feature on some PCs.
• Signed publisher identity may shape how cleanly an app appears in the list.
• In-process checks and current-user registry storage still limit how strong the boundary can be.

Until Microsoft documents the signature rules, Insiders can only observe which apps show up cleanly and which do not. The flag name itself is the strongest public hint that identity, not only install type, feeds the new rows.

Why the timing collides with older privacy headaches

The same Capability Access Manager that powers these permissions drew attention earlier in 2026 when its write-ahead log file consumed up to 500 GB on affected machines. Microsoft acknowledged the storage bug. The component simply records which apps request camera, mic, location and similar capabilities.

500 GB peak reported size for CapabilityAccessManager.db-wal on some systems.

August 17 2026 Experimental build date with no privacy note in the changelog.

1903 original year the desktop list first appeared.

The new toggles also arrive not long after public discussion of Microsoft’s GDID tracking identifier. Users who already distrust telemetry now get a more granular Settings page for hardware access while the broader collection machinery remains largely untouched. The second-order result is a more consistent permission surface for apps, not a full reduction in Windows data gathering.

Microsoft’s Experimental Preview Build 26340.9212 release notes cover a redesigned File Explorer context menu, emoji updates, Magnifier refresh, WinRE networking and the removal of WMIC. Privacy controls for Win32 never appear. Experimental features can change or disappear before any public channel.

That silence in the notes matters. The build advertises shell and recovery work while a permission model change ships beside them for a subset of Insiders. People hunting changelog lines for privacy will miss it; people opening the Camera or Microphone pages will not.

Who gains control and who still works around it

Privacy-conscious users running multiple browsers, chat clients and creative tools gain the most immediate benefit. They can keep mic access for a work Discord client while denying it to a random game launcher or an older utility. System administrators who manage mixed fleets may eventually script or policy the same distinctions once the feature leaves Experimental.

Win32 developers face a quieter pressure. Apps that previously assumed silent hardware access now risk a prompt and a user denial. Store apps already lived under that model. The gap that made traditional installers feel freer is narrowing. Unsigned tools and those that hook hardware through less common paths may still evade the clean list, exactly as Rivera flagged.

Third-party privacy utilities that offered per-app blocking lose one of their selling points if Microsoft ships the native version. At the same time, any Windows 11 machine that never receives the feature, or that sees it pulled, still needs those tools. The change also sits alongside other Windows security moves such as Microsoft locking KMS activation to TPM hardware, which likewise tightens the environment around software identity.

Everyday users who simply want Zoom and Teams to work will notice little until an unexpected app tries the mic. Then the new dialog appears. That single interaction is the most visible day-to-day difference.

Desktop Apps Move Closer to Store Rules

Store apps have lived with individual camera, microphone and location switches for years. The Experimental build pulls listed Win32 programs into that same style of control for the hardware paths Settings already exposes. The old freedom of a single desktop bucket was the exception; the per-app row is becoming the default pattern in testing.

That shift does not turn every classic installer into a sandboxed Store package. It does mean silent hardware access is harder to take for granted when the feature is present. A centered prompt, a deny option, and a lasting toggle match the rhythm Store software already follows.

Rivera’s caution still applies. If identity checks run in-process and land in the current-user hive, determined software can still fight the model. The Settings page gets clearer. The enforcement story stays only as strong as those checks.

1. Store baseline: individual toggles and familiar prompt habits already in place.
2. Win32 on affected builds: separate rows, dedicated switches, first-access dialogs.
3. Unsigned or unusual paths: may stay off the clean list or easier to bypass.
4. System components: remain outside the third-party choices so dictation-style features can keep working.

For users, the implication is straightforward. Mixing browsers, chat clients and utilities no longer requires an all-open or all-closed desktop stance on machines that show the rows. For publishers of traditional software, the implication is a narrower gap with Store distribution on privacy UX, even while install mechanics stay different.

How the Capability Log Ties Into the Toggles

Capability Access Manager is the component that records which apps request camera, mic, location and similar capabilities. It is also the component whose write-ahead log swelled to extreme sizes on some systems earlier in 2026. The new per-app toggles sit on top of that same permission accounting, not apart from it.

When a desktop app is promoted into the main list, the system is surfacing identity data that logging already tracked. The 1903-era list proved the OS could name programs and paths. The Experimental work adds a control on top of names the platform was already willing to show.

The storage bug and the privacy UI therefore share a backbone. One failed loudly on disk. The other appears quietly in Settings for some Insiders. Both depend on Windows keeping a durable picture of which software asked for which capability.

• Logging identifies apps that touched camera, mic, location and related capabilities.
• The Settings list reuses that accounting to build per-app rows.
• System features stay carved out so a user denial to a third-party title need not kill dictation.
• Changelog silence leaves the link between log and toggles undocumented for now.

None of that repairs broader telemetry concerns such as debate around GDID. It does explain why finer hardware switches can ship without a new privacy platform: the bookkeeping layer was already there, even when it misbehaved on disk.

Whether the controls survive the Experimental channel

Microsoft has given no public commitment that per-app Win32 privacy toggles will reach Beta, Release Preview or general availability. The company routinely tests ideas in Experimental that never ship. Feature flags and gradual rollout already produce inconsistent results inside the same build number.

Jakub’s original post spotting the toggles framed the discovery as “huge changes.” Rivera’s reply tempered the novelty while acknowledging the individual switches are new. Crowd reaction on X has been hopeful but cautious: long-overdue if it sticks, easy to lose if feedback or engineering cost intervenes.

For now the practical advice is simple. Insiders on 26340.9212 can open Settings > Privacy & security and check Camera, Microphone and Location. If desktop apps appear as separate rows, the feature is live on that machine. Everyone else waits. Related Windows 11 servicing changes, including the Windows 11 update toggle that installs vendor fixes, show Microsoft continues to refine how optional and hardware-tied behaviors reach devices.

If the per-app model reaches stable Windows 11 in its current form, the old shared desktop switch becomes a historical footnote and traditional software loses one more privilege Store apps never had. Until Microsoft documents and expands it, the upgrade remains a test flight with real toggles for those who see them.