The privacy feature is the main item, but it isn't new to this channel. Reports from last week say it already appeared in the previous Future Platforms build. This article covers what changed, who's affected, and what to check if you're running the build.
Where this build fits
The Future Platforms channel gets the earliest platform code Microsoft ships to Insiders. Microsoft's Flight Hub describes these builds as preview builds for Windows 11 that "are not aligned to any retail release of Windows." The Flight Hub lists 29704.1000 as dated 11/6/2026. Before it came 29698.1000 on October 30 and 29695.1001 on October 23.
Builds for the other Insider tracks came out the same day, according to Flight Hub:
| Track | Build released November 6, 2026 |
|---|---|
| Experimental (Future Platforms) | 29704.1000 |
| Experimental (26H2) | 26340.9882 |
| Beta (26H2) | 26320.9876 |
| Experimental (26H1) | 28120.3454 |
| Beta (26H1) | 28020.3445 |
Microsoft's usual warning applies here too. These builds can be unstable, may come with limited documentation, and contain features that "might never get released." Treat everything in this build as an experiment that could still change or be dropped.
In short: 29704.1000 is a weekly Future Platforms build. It doesn't map to any specific Windows release, and it shipped alongside updates to the 26H2 and 26H1 tracks.
Per-app privacy controls for desktop apps
Windows has long treated camera, microphone and location access for traditional desktop apps as one switch. You could choose individual Microsoft Store apps, but all Win32 programs shared a single setting. How-To Geek described the old approach as working like a master key: either every program got in or none did.
The build notes say Insiders can now allow or deny access for each desktop app separately. Microsoft lists these changes:
- Per-app control: allow or deny each desktop app individually.
- Where to find it: Settings > Privacy & security > Camera, Microphone, or Location.
- First-use prompts: an app that hasn't used a resource before asks for permission the first time it tries.
This feature isn't new to this channel
The 29704.1000 notes say Insiders "can now" manage these permissions. That wording makes it sound new, but it isn't, at least not in this channel. Neowin reported that the earlier Future Platforms build 29698.1000 brought the ability to control camera, microphone, and location permissions for individual desktop apps. This option has been available in other channels for quite some time now, and it finally arrives to the Future Platforms channel. 4sysops reported the same thing: Beta Build 26220.9836 (25H2) and Experimental (Future Platforms) Build 29698.1000 let you set camera, microphone, and location access separately for traditional Win32 desktop applications.
The feature has been in testing for months. In August, Windows Central found it hidden in an Experimental Insider build (26340.9212), and reported that it lets you block access to your camera and microphone on a per-app basis for Win32 apps.
Why repeat it in this week's notes? Microsoft doesn't say. The notes put the change under "gradually being rolled out," and Microsoft says many features in this channel use Controlled Feature Rollout, which starts with a subset of Insiders and expands over time. In practice, if you're on 29704.1000 and still see the old single desktop-app switch, your machine may not have the feature turned on yet. Microsoft doesn't publish a way to force it on, and you shouldn't trust any guide that claims to.
Your existing settings carry over
Microsoft lists what stays the same:
- Your existing permission decisions are kept.
- Apps that had access keep it.
- Apps that were denied stay denied.
- You don't need to do anything, and no settings are reset.
- Existing enterprise policies keep working as designed.
On that last point, Microsoft says it's "exploring additional management capabilities" but gives no details. If you're hoping for a per-app Intune or Group Policy setting, nothing has been announced. Your current policies should keep working, and that's all Microsoft has committed to so far.
What the new Settings pages look like
Coverage of the earlier build gives an idea of the interface. Windows Mode reported that on the Location page, each app now has its own switch, with a Last accessed time for apps that used it. Unsigned apps get a separate switch at the bottom. Windows Latest's screenshots, cited by TweakTown, showed the Privacy & security pages dropping the separate "Let desktop apps access…" toggle. TweakTown reported that the Settings app instead places each app in the same dropdown menu as native Microsoft Store apps.
App names may not be what you expect
Microsoft lists two limitations, and both affect what you'll see in the list:
- Different app names. Apps that use shared system components, browser-hosted experiences or similar technologies might show up under a different name than you expect. Before you deny access to something with an unfamiliar name, find out what it actually is. You might be blocking a component your video-calling app depends on.
- "Unsigned" entries. If Windows can't verify an app's publisher, the app may show up as Unsigned. Microsoft's advice is to grant access only to apps you recognize and trust.
How to check it on a 29704.1000 machine
- Press Win + I to open Settings.
- Go to Privacy & security, then open Camera, Microphone or Location.
- Look for individual desktop apps in the list, each with its own switch. If you only see one shared desktop-app toggle, the rollout hasn't reached your PC yet.
- Review apps you don't recognize and any Unsigned entries before changing them.
- Open an app that hasn't used the camera, microphone or location before, and confirm that Windows asks for permission the first time.
- Report problems in Feedback Hub (Win + F) under Settings > Privacy Settings.
What this protects against, and what it doesn't
This is a real improvement. You can now let your conferencing app use the microphone while blocking some background utility you forgot you installed, without turning off desktop-app access entirely. How-To Geek noted that if you use an Android phone, you'll find the per-app permission settings feel familiar.
The caveats still matter. On the old global switch, Microsoft has warned that desktop apps may not always appear in the list and might still reach the camera or microphone with the setting off. A WindowsForum guide on camera permissions noted that the setting provides only "limited control" over desktop apps that use supported methods to access the camera. Microsoft hasn't said whether the per-app version closes that gap. Until it does, treat these switches as useful privacy controls, not a guarantee against malware that's determined to get in. Nothing announced so far suggests otherwise.
In short: per-app desktop privacy controls are rolling out gradually, your current settings carry over, and the main thing to watch for is apps listed under unexpected names or as Unsigned.
Fix for a failed upgrade (0x80070057 - 0x20003)
Microsoft fixed an issue where some Insiders hit error 0x80070057 - 0x20003 when upgrading to the latest builds. The error message read: "The installation failed in the SAFE_OS phase with an error during INSTALL_UPDATES operation."
The SAFE_OS phase runs early in a feature upgrade, inside the setup environment, before your main installation is migrated. A failure there usually sends the PC back to the build it started on. If your Future Platforms machine kept failing to upgrade with this code, try updating to 29704.1000 again.
The notes don't say which builds were affected or how many Insiders ran into it. "Some Insiders" is as specific as Microsoft gets.
Fix for HDMI and DisplayPort audio on AMD graphics
Microsoft also fixed an issue where HDMI and DisplayPort audio playback might fail on certain AMD graphics cards after recent builds. That's the audio path to monitors with speakers, TVs and AV receivers.
The notes don't name GPU models, driver versions or the builds that introduced the problem. If your sound through a display output stopped working on a recent Future Platforms build, install 29704.1000 and test it before you start reinstalling drivers.
In short: two fixes for problems that were easy to notice, a blocked upgrade and silent display audio, though Microsoft doesn't say exactly which hardware or builds were affected.
Other notes for this channel
- Desktop watermark: the watermark in the lower-right corner is normal on Insider pre-release builds.
- Localization: some features in development may not be fully translated yet. Microsoft asks you to report localization issues through Feedback Hub.
- Rollout: Controlled Feature Rollout means two PCs on the same build number can show different features. Keep that in mind before you report something as missing.
Is it worth installing?
If you're already in the Future Platforms channel, yes. The upgrade fix and the AMD audio fix solve real problems, and the privacy controls are one of the more practical changes in this year's Insider builds.
If you're thinking of joining the channel just to get per-app desktop privacy controls, it's not a good reason. The same feature is already being tested in the Beta and Experimental channels, which are more stable and closer to an actual release. Future Platforms builds are for Insiders who want the newest platform code and accept that things will break.
For IT admins, the main points are that existing policies are preserved and that Microsoft says it's "exploring" more management options. Until those options are documented, plan around the controls you already have.