Windows 11 26H2: What Actually Changes for Your Mic, Speakers and Camera
Windows 11 26H2 does not move any of the audio or camera settings you rely on. Privacy controls, input device selection and spatial audio all stay where they are in 24H2 and 25H2. The risk with any feature update is driver regression, not relocated settings — so the useful preparation is recording what works now.
Where 26H2 stands right now
Version 26H2 reached the Release Preview channel on 27 August 2026 as build 26300.9278, with general availability expected in October 2026. Version 26H1 already shipped earlier in 2026, but it is scoped to new hardware and is not offered as a feature update to existing PCs, so most people are moving from 24H2 or 25H2 straight to 26H2.
Separately, the September 2026 cumulative update, KB5120998, is due on 8 September 2026 for both 25H2 and 24H2. That is a monthly quality update, not the feature update — worth distinguishing, because if something breaks this month it is far more likely to be the cumulative than 26H2.
Take a baseline before you update
The single most useful thing you can do before any feature update takes ten minutes and saves hours later. Run the microphone test and note your input level and which device is selected. Run the webcam test and note the resolution and frame rate it reports. Run the speaker test and confirm both channels.
Write those three results down. If audio or video misbehaves after the update, you will know immediately whether the hardware changed behaviour or whether you are misremembering what normal looked like. Without a baseline, most people spend the first hour establishing what should have been obvious.
What actually breaks after feature updates
In practice, three things account for most post-update audio and camera failures, and none of them are new in 26H2.
The first is a driver rollback: Windows replaces a vendor audio or camera driver with a generic one, and features that depended on the vendor driver disappear. Spatial audio options greying out is the classic symptom. Check the driver provider in Device Manager before assuming the feature was removed.
The second is a reset privacy permission. Microphone and camera access is per-app, and a feature update can leave an app that previously worked without access. Settings, Privacy and security, Microphone is the first place to look.
The third is default device reassignment: Windows picks a different output or input than the one you were using. It is the most common cause of "no sound after update" and the fastest to check.
If something did break
Work in this order. Confirm the hardware itself still works using a browser test, because that separates a hardware fault from a Windows configuration problem in about thirty seconds. Then check the per-app permission. Then check which device is selected. Then, and only then, look at drivers.
For microphones specifically, our guide on fixing a microphone on Windows 11 covers that order in detail, including the privacy permission that blocks access by default. If your speakers went silent instead, no sound from laptop speakers covers the equivalent output-side checks.
If the failure started within a day or two of an update, note the KB number from Settings, Windows Update, Update history. Uninstalling a cumulative update is quick and reversible, and it tells you definitively whether the update is responsible.
Sources: MDN — MediaDevices.getUserMedia() · Microsoft — Camera, microphone and privacy
Frequently asked questions
Will 26H2 change where audio and camera settings live?
No. The Settings paths are the same across 24H2, 25H2 and 26H2 — what changes between branches is the driver your OEM ships.
What should I do before a feature update?
Take a baseline. Note your microphone input level and selected device, the resolution and frame rate your webcam reports, and that both speaker channels work. If something misbehaves afterwards you will know whether the hardware changed or you are misremembering normal.
What actually breaks after feature updates?
Three things account for most of it: a vendor audio or camera driver replaced with a generic one, a reset per-app privacy permission, and a changed default device. Spatial audio options greying out is the classic symptom of the first.
In what order should I troubleshoot?
Confirm the hardware works with a browser test first, because that separates a hardware fault from a Windows configuration problem in about thirty seconds. Then the per-app permission, then the selected device, and only then drivers.