Windows 11 cumulative update KB5094126, released on June 9, 2026, for builds 26200.8655 and 26100.8655, is triggering a wave of user reports about system freezes, forced BitLocker recovery screens, and broken OneDrive integration in File Explorer on some devices.
While Microsoft positions the patch as a critical security and reliability update, early feedback suggests serious regressions that can render systems temporarily unusable or disrupt everyday workflows.
Windows 11 Update Causes System Freezes
Update KB5094126
KB5094126 is the June 2026 cumulative update for Windows 11 versions 24H2 and 25H2, bundling security fixes and reliability improvements for both consumer and enterprise deployments.
Microsoft highlights improvements such as better handling of hypervisor-related stop errors and enhanced startup reliability after boot file changes, especially around BitLocker-protected systems.
The update ships through Windows Update as a mandatory Patch Tuesday release. It is also available via the Microsoft Update Catalog for manual installation.
However, alongside the official changelog, community reports began surfacing within days of the release, indicating that KB5094126 may introduce new stability and compatibility issues on certain hardware and configuration combinations.
These problems span consumer laptops, domain-joined corporate endpoints, and managed Windows 11 tablets that rely on local accounts and custom group policies.
System Freezes and LAN Connectivity Failures
Multiple users report scenarios in which KB5094126 installs successfully but leaves their systems unstable or partially unusable afterward.
One Windows 11 Pro 25H2 user reports that the update consistently breaks local area network (LAN) access while leaving internet connectivity intact, effectively isolating the device from on-prem resources until the patch is manually removed.
Despite pausing updates via Settings and attempting to hide the patch with wushowhide, the update continues to reinstall itself after reboots and shutdowns, forcing the user into a loop of uninstalling KB5094126 to restore basic LAN functionality.
Other users report more severe outcomes: the update installs, then the machine freezes shortly afterward, requiring recovery actions.
Community advisors recommend rolling back the latest cumulative update from the Windows Recovery Environment by using the “Uninstall Updates” option, particularly when the system fails to boot normally.
Microsoft’s own release health documentation for Windows 11 24H2 and 25H2 references similar post-update startup issues tied to EFI System Partition (ESP) edge cases and suggests that newer cumulative updates, along with an ESP registry workaround, can address some freeze-related scenarios. However, KB5094126 itself appears to be implicated in fresh incidents.
BitLocker Recovery Loops on Local Accounts
A particularly disruptive class of issues involves devices unexpectedly booting directly to the BitLocker Recovery screen after KB5094126 is applied.
One corporate environment reports that multiple Windows 11 tablets used by a sales team, deliberately configured with local accounts and device encryption toggled off, began demanding BitLocker recovery keys immediately after installing the June 9, 2026 update.
Because these endpoints do not use Microsoft accounts and have BitLocker disabled in settings, there is no obvious path to a cloud-backed recovery key, leaving the organization effectively locked out of several machines.
Existing Microsoft guidance reaffirms that if a BitLocker-protected volume enters recovery mode and no recovery key is available in any of the standard backup locations (Microsoft account, Azure AD, AD DS, printed or file backup), there is no supported method to bypass recovery or extract a temporary clear key via WinRE or Command Prompt.
In such cases, the only remaining option is to wipe the drive and reinstall Windows, which has raised concerns among affected businesses about Microsoft’s accountability when a security update appears to trigger recovery on systems that were believed to have encryption disabled.
OneDrive Integration Broken in File Explorer
KB5094126 is also causing OneDrive integration problems, especially on domain-joined PCs managed by Group Policy.
One administrator notes that after installing the update, the OneDrive node in File Explorer remains visible but becomes non-functional: the folder appears empty and cannot be browsed, even though the OneDrive client itself still syncs files and remains accessible via the system tray “blue cloud” icon.
When the same device is moved into an organizational unit (OU) that blocks Group Policy and then rebooted, OneDrive reappears correctly at the top of File Explorer under the “cloud” section and behaves normally, suggesting a regression in how KB5094126 interacts with certain OneDrive or folder redirection GPOs.
| Issue category | Symptom / user impact | Affected scenario example |
|---|---|---|
| System freezes | PC installs KB5094126 and then freezes or becomes unresponsive post‑reboot | Home user reports Windows 11 freezing after cumulative update install. |
| BitLocker recovery loop | Device boots straight into BitLocker Recovery despite BitLocker previously disabled | Corporate tablets with local accounts locked at BitLocker recovery screen. |
| LAN connectivity loss | Internet works, but local network shares and LAN resources are unreachable | Windows 11 Pro 25H2 laptop loses LAN access when KB5094126 is present. |
| OneDrive File Explorer | OneDrive node shows in File Explorer but appears empty or cannot be browsed | Domain‑joined PCs lose OneDrive browsing under GPO after update. |
Community discussions on Windows forums and Reddit indicate that, so far, the most reliable workaround for the broken File Explorer integration is to uninstall KB5094126 and then configure Windows Update not to reinstall it, using advanced update controls or, in managed environments, deferral policies in WSUS or Intune.
Microsoft community moderators acknowledge that multiple users are reporting similar behavior and advise affected administrators to escalate cases through the Microsoft 365 Admin Center so they can be investigated with backend diagnostics and potentially addressed via a Known Issue Rollback (KIR) or a subsequent cumulative update.
Follow us on Google News, LinkedIn, and X to Get Instant Updates and Set GBH as a Preferred Source in Google.
