Microsoft Recognizes Problems in Windows 11 KB5094126 Update

Microsoft has acknowledged awareness of various issues in the KB5094126 update (June 2026 Patch Tuesday), including a bug where the Recycle Bin fails to display correct file names and Office apps crash. Additionally, there are reports of Black Screen of Death (BSOD) and BitLocker recovery screen prompts, though these issues have not been officially acknowledged by Microsoft at this point.

Summary of KB5094126 Update

KB5094126 is a required update included in the June 2026 Patch Tuesday cycle and applies to PCs running Windows 11 25H2 or 24H2. This update installs automatically, even if Windows Updates are disabled. It upgrades the OS to Windows 11 Build 26200.8655 or 26100.8655. To check if this update is installed, go to Settings > System > About.

Issues Confirmed by Microsoft

Microsoft has verified two separate problems caused by KB5094126:

• Office Apps Crash: Third-party applications are unable to open Office programs like Word, PowerPoint, or Excel. This issue is due to a bug that impacts OLE automation, a feature that allows third-party apps to interact with Office apps. For instance, accounting or document management software integrated with Office apps may cause Word, Excel, or PowerPoint to crash when attempting to open files.
• Recycle Bin File Name Bug: The Recycle Bin interface incorrectly shows internal file names (e.g., $R4ABC12.docx) instead of the original file names (e.g., Report.docx). Although this does not lead to data loss, it can cause confusion when trying to restore or delete files.

Details About the OLE Automation Bug

The OLE automation disruption has significantly affected workflows in multiple industries:

• Organizations using applications such as CCH Engagement, Workpaper Manager, Dentrix, Softdent, and Zotero encounter crashes when these apps attempt to interact with Office products.
• Apps relying on OLE automation to open Word, Excel, or PowerPoint are unable to operate. However, manually opening Office files via File Explorer continues to work as expected.

Microsoft has acknowledged this issue and is working on a fix, but no immediate solution is available. Users are advised to exercise caution when utilizing affected third-party programs.

Explanation of the Recycle Bin Bug

Normally, when a file is deleted, it is moved to the Recycle Bin with a user-friendly name (e.g., dog.jpg). Internally, Windows assigns it a name like $Rxxxxx.ext, while metadata preserves details such as the original name and location. Due to the KB5094126 update, the Recycle Bin now displays the internal name instead of the original file name. This can lead users to accidentally delete or restore incorrect files.

Microsoft has committed to providing a workaround for this issue, with a fix expected by July 14, 2026. In the meantime, users are advised to carefully review file names before performing any actions in the Recycle Bin.

Unacknowledged Problems: BSOD and Boot Failures

Although Microsoft has not officially recognized reports of BSODs and boot failures linked to KB5094126, users and administrators have reported the following issues:

• Systems booting into recovery mode after installing the update.
• BSODs with error code 0xc0430001.
• BitLocker recovery screens, blank blue screens, and Secure Boot verification errors.

These issues appear to primarily impact HP business PCs, including models such as:

• HP EliteBook 840 G10
• HP ProBook 460 G11
• HP ZBook
• HP Engage One Pro 15.6 G2 AiO POS systems
• HP ProBook 650 G9
• HP EliteBook 840 G9
• HP EliteBook x360 830 G6

Based on testing by Windows Latest, the BSOD issue is linked to insufficient EFI storage. This partition, responsible for storing boot and firmware-related files, may lack sufficient space, causing update failures. Alternatively, Secure Boot may fail to trust the boot path, resulting in errors such as "operating system loader failed signature verification."

Suggested Solutions for BSOD Problems

If BSODs occur after installing KB5094126, the following steps are recommended:

1. Disable Secure Boot and attempt to reinstall the update.
2. Expand the EFI partition to ensure adequate storage space.
3. Re-enable Secure Boot after successfully applying the update.

Conclusion

Microsoft has recognized several significant issues in the KB5094126 update, with additional problems being reported by users. While some fixes are underway, users are advised to remain cautious and apply temporary workarounds where possible. Stay updated and review system settings to reduce any potential disruptions caused by this update.