What IT Admins Need to Know About the Windows 11 August 2026 Update
Microsoft's Windows 11 August 2026 update, rolling out Aug. 11, adds Windows Hello ESS, AI model removal, and Voice Isolation for IT to plan around.
WINDOWS
8/4/20262 min read
Microsoft is set to ship the Windows 11 August 2026 security update on Tuesday, August 11, with identical feature parity across versions 24H2 and 25H2. It's a heavier release than a typical Patch Tuesday cumulative, bundling sign-in security changes, a first crack at letting users remove a built-in AI model, and a batch of File Explorer, Search, and input tweaks that helpdesk teams will start fielding questions about the moment it lands. As always, Microsoft is staging most of the new functionality through Controlled Feature Rollout, so don't expect every device in a ring to display identical behavior on day one even after the same KB is installed.
The change most worth flagging to your security team is the expansion of Windows Hello Enhanced Sign-in Security (ESS) to external fingerprint sensors. ESS isolates the biometric matching process into a protected memory space away from the rest of the OS, which is a meaningfully higher bar than standard Windows Hello encryption. Until this update, that protection was effectively limited to devices with built-in sensors, largely Copilot+ PCs. Organizations that issue USB fingerprint readers to standard hardware, rather than requiring a Copilot+ refresh, should recheck their Windows Hello for Business compliance policies in Intune once test-ring devices pick up the build, since ESS status is already exposed through device health attestation and worth surfacing in compliance reporting.
On the AI side, Microsoft is giving users the ability to uninstall the Image Generation model from Settings > System > AI Components. It's a narrow concession, only one model, not a master AI toggle, but it directly answers one of the more persistent complaints from admins managing locked-down or regulated endpoints where preinstalled generative AI components have been a compliance headache. Don't treat this as a substitute for policy enforcement: AppLocker or Windows Defender Application Control remain the reliable levers if you need to guarantee a component is unavailable rather than just uninstalled by default, since this is a per-user, self-service option rather than a managed setting exposed through Intune configuration profiles today.
The rest of the release is smaller but still worth a line in your release notes to end users. File Explorer's details view finally shows file sizes in the appropriate unit, KB, MB, or GB, instead of rendering everything in kilobytes, and middle-click now opens folders in a new tab from the address bar or Home page. Windows Search picks up better typo tolerance and now returns results from two-character queries, which changes what shows up if you've built any training material or screenshots around current search behavior. Touchpad settings gain configurable scroll and zoom speeds plus an accelerated-scrolling option, and Voice Access adds a "Voice Isolation" mode alongside a background-noise-only mode, both worth knowing about if your organization runs an accessibility program.
For deployment planning, the practical steps are the usual ones: add the August 11 cumulative to your Windows Update for Business test rings ahead of broad deployment, confirm your Windows Hello for Business and compliance policies in Intune correctly reflect ESS status once eligible external readers are in the field, and give the helpdesk a short heads-up on the File Explorer and Search changes so "why did my file sizes change" doesn't turn into a ticket queue. None of these changes require action before August 11, but each is small enough to slip past a change log if nobody flags it in advance.
Connect
Stay updated with latest Microsoft blog news
© 2025. All rights reserved.