Windows 11 KB5094126 Breaks Office Apps, Sends HP PCs into BitLocker Loops

June's Patch Tuesday fix for Windows 11 came with a steep hidden cost: while KB5094126 seals 208 security holes, it has also broken Office app launches, sent some HP business PCs into BitLocker recovery loops, and left the Recycle Bin showing cryptic internal identifiers instead of actual file names.

The mandatory cumulative update — which applies to Windows 11 versions 24H2 and 25H2 — was released on June 9, 2026. Microsoft has confirmed several of the bugs, though others remain in the "widely reported but unacknowledged" category weeks after the rollout.

What's breaking and how badly

The most disruptive issue affects anyone who uses Microsoft Office through third-party software. The update accidentally damaged OLE automation — the internal mechanism Windows uses to let one application talk to another. Accounting software, medical practice management tools, and countless enterprise apps rely on OLE to open, read, or write Office documents without the user manually launching Word or Excel. Those integrations are now broken for many users.

More alarming for IT departments: a subset of HP business machines have been getting stuck in BitLocker recovery loops or showing a black screen at boot after the update installs. The root cause appears to be insufficient EFI partition space — the update installs new Secure Boot certificates that some older partition layouts simply cannot accommodate.

Microsoft's acknowledged Recycle Bin bug is less catastrophic but still confusing: when Windows prompts you to permanently delete a file, it now shows the internal identifier (something like $R4ABC12) instead of the actual filename. Files restore correctly and the Recycle Bin itself displays normally — but if you're not sure what you're deleting, that prompt is now unhelpful. Microsoft says a fix won't arrive until July 14, 2026.

Additional reports — not yet officially acknowledged — include OneDrive becoming unresponsive from File Explorer's sidebar, systems freezing within minutes of startup, and LAN connectivity dropping while internet access stays up. A smaller but notable issue: the update modified desktop.ini files on some machines, scrambling custom folder icons and views.

The mandatory update problem

What makes this particularly frustrating is that KB5094126 is mandatory — it will eventually install even if updates have been paused. Users who have already been hit can't easily uninstall a cumulative update without risking exposure to the 208 vulnerabilities it patches. That's a genuine no-win situation: apply the update and face boot failures, or skip it and remain unpatched.

Microsoft's recommended workaround for the HP boot issue involves expanding the EFI partition before the update, which requires enterprise deployment tooling that most home users don't have. For Office OLE issues, there is currently no published workaround.

What to do right now

If you're an IT administrator managing a fleet of HP business machines, hold the update at the group policy level until Microsoft issues further guidance. For Office integration failures, check whether your accounting or medical software vendor has posted a hotfix — some have already pushed compatibility patches on their end. Home users on consumer HP hardware appear largely unaffected by the boot issues so far.

The update does bring genuine improvements alongside the chaos: a new "Low Latency Profile" that reduces system jitter for gaming and audio workloads, and the 208 security patches remain important. The question is whether Microsoft can push a corrective rollup before July 14 — the currently promised date for just the Recycle Bin fix.