The build also includes the new WinUI 3 Windows Search, a Battery Status widget, IAKerb turned on by default and several smaller fixes. Here's what changed, who it affects, and what it doesn't do.
The build at a glance
- Build: 26340.9616, Experimental channel. The ElevenForum release thread lists it as KB5127753 Windows 11 Insider Experimental (26H2) build 26340.9616
- Base: Microsoft's release notes say it is based on Windows 11, version 26H2, delivered through an enablement package
- Architectures: WindowsForum's build tracker lists it as a Feature update, Oct 7, 2026, amd64, arm64
- Rollout: Microsoft releases many of these features through Controlled Feature Rollout. A small group of Insiders gets them first, and the share grows over time. Installing the build doesn't mean you'll see every feature right away.
- Caveat: Microsoft says Experimental features may change, be removed or never ship beyond the Insider program.
It came out the same day as Beta build 26220.9606 and the 26H1 Experimental build 28120.3181. Neowin noted that Build 26340.9616 also adds a new Battery Status widget, new Task Manager process grouping, File Explorer font preview and installation support, and some bug fixes.
Summary: This is a staged Insider release on the 26H2 enablement-package track, not a general Windows 11 update.
Task Manager: apps can now group their own processes
Task Manager has always grouped processes mostly by parent and child. That works until an app runs several separate background processes that aren't linked that way. You then see a scattered list of entries and have to work out which ones belong to the same product.
Microsoft's fix is to let the app decide. In the release notes' wording, Task Manager is expanding process grouping to allow apps to combine otherwise separate background processes into a single unified category rather than relying solely on traditional parent-child trees. Microsoft says this makes an app's resource usage easier to understand. Microsoft Defender is the first app to use this capability.
Defender is a logical first test. Security software runs several always-on components, and "why is my PC slow?" threads often end with someone pointing at an antivirus process. Seeing Defender's activity under one heading could help users judge its overall footprint without adding up separate rows.
What Microsoft hasn't said
Microsoft's description is short. Windows Report took it to mean the change should make it easier to understand the total CPU, memory, and other resources consumed by an application. That's a fair guess, but the official notes don't confirm it. Microsoft doesn't say:
- What the grouped entry looks like, or which columns are added together
- Whether users can expand, split or override a group
- What third-party developers need to do to use it
- Whether it works in the Details tab or only on the Processes page
It also helps to be clear about what this is not. Nothing in the notes says Defender uses fewer resources. This changes how Task Manager shows processes, not how much they consume. Grouping by app is also a choice the app makes about itself, so it's fair to ask how Task Manager will handle a misbehaving or malicious program that groups itself in a misleading way. Microsoft hasn't addressed that, and admins who check processes during incident response should keep using the Details view and tools like Process Explorer until it's documented.
Summary: This is a useful readability change that starts with Defender. How much it helps depends on how many developers adopt it and on details Microsoft hasn't published yet.
Windows Update error 0x80073712 on Sandbox-enabled PCs
The second main item is a narrow fix. Microsoft's notes say: Fixed the issue causing some Insiders with Windows Sandbox enabled to get error 0x80073712 when attempting to install the latest updates.
Windows Sandbox is the throwaway virtual desktop built into Windows 11 Pro, Enterprise and Education. Testers, developers and IT staff use it to run suspicious installers or try configuration changes safely. Those are exactly the people likely to be on Insider builds, so an update failure tied to Sandbox hit the people Microsoft most wants testing.
Scope
- Who it affects: Some Insiders with Windows Sandbox enabled who got 0x80073712 when installing recent updates
- What Microsoft didn't publish: The cause, a workaround, which update packages were affected, or whether retail Windows 11 builds had the same problem
- What it doesn't mean: 0x80073712 is an old code that shows up in many situations. Based on general Windows servicing knowledge rather than this release note, it usually indicates a problem with the component store. This fix covers one Insider scenario, not every case of that error.
If you still see the error
Here's a cautious approach based on general Windows troubleshooting practice, not Microsoft guidance specific to this bug:
- Install the build first. If you're an Experimental Insider hitting this error with Sandbox on, getting to 26340.9616 is what Microsoft says fixes it.
- Check whether Sandbox is the trigger. If you can't wait, temporarily turning off the Windows Sandbox optional feature is a reasonable test, though Microsoft hasn't documented it as a workaround.
- Repair the component store. On any Windows 11 PC, running DISM's RestoreHealth and then System File Checker from an elevated terminal is the standard response to component-store errors.
- Report it. If the error continues after updating, file it in Feedback Hub with your build number and Sandbox status so Microsoft can tell whether the fix missed a case.
Summary: This is a targeted fix for a specific Insider problem. Treat it as that, not as a cure-all for 0x80073712.
A cleaner security key PIN screen
Microsoft also removed the "other user" icon from the screen where you enter a security key PIN, describing the result as a clearer sign-in experience. It's a visual change only. The notes don't describe any change to how FIDO2 security keys authenticate. Still, a less cluttered prompt can mean fewer confused support calls in organizations moving to passwordless sign-in.
Everything else in Build 26340.9616
The rest of the build is worth knowing about, especially the authentication change:
| Area | Change |
|---|---|
| Windows Search | New WinUI 3 interface with inline actions (dark mode, Bluetooth, brightness, mute, window arrangement) and better matching for typos and synonyms. English only at first; restart after upgrading before the feature flag appears. |
| Battery Status widget | One view of battery levels for the PC and peripherals. Add it via Widgets board > Add widgets > Battery Status. |
| Kerberos | IAKerb on by default for Windows clients, so Kerberos can work when a domain controller isn't directly reachable. The goal is less reliance on NTLM. |
| Taskbar | Fixed window previews that slowed down and lagged over time |
| Settings | Removed the backplate from the Settings icon when UAC is invoked from Settings |
| File Explorer | Font preview and installation from File Explorer and desktop context menus |
| Widgets | Notifications when a newly installed app adds a widget (enabled in an October 9 update) |
| Stability | Fixed an msmpeg2ac3dec.dll issue that crashed some apps and games |
To try the new Search early, NTCompatible says to upgrade to Experimental build 26340.9616 or 28120.3181, then head to Settings => Windows Update => Windows Insider Program => Feature flags.
Admins should pay most attention to the IAKerb change. Pureinfotech summarized it as improving authentication when a domain controller isn't directly reachable. It doesn't remove NTLM, and it doesn't apply to every authentication flow. It's one more step in Microsoft's long effort to retire NTLM, and the right time to test VPN and remote-access sign-ins against it is while it's still in preview.
The bottom line
Build 26340.9616 is a maintenance release in a good way. Task Manager grouping by app could make it much easier to answer "what is this app actually using?", once more developers adopt it and Microsoft documents how it works. The Sandbox fix removes an update blocker for testers. The security key, taskbar and codec fixes are smaller improvements.
None of it is guaranteed to reach the general Windows 11 release unchanged, and the staged rollout means two Insiders on the same build may see different features. If you're on the Experimental channel and use Windows Sandbox, install this build. For everyone else, it shows where Task Manager, Search and Windows authentication are probably headed in the 26H2 cycle.