Windows 11 KB5094126 has emerged as the most significant update of the year, introducing a plethora of new features, including the much-anticipated Low Latency Profile. However, reports from Windows Latest indicate that the June 2026 Update is not without its challenges, particularly for users of certain HP devices, where boot failures—manifesting as BSODs (Blue Screen of Death) or BitLocker Recovery prompts—have been reported. Additionally, issues with cloud synchronization in File Explorer have surfaced.
Released on June 9, 2026, as part of Microsoft’s Patch Tuesday cycle, KB5094126 (Build 26200.8655) installs automatically unless users have opted to defer the update. This update addresses up to 200 security vulnerabilities, including 33 classified as critical and five zero-day bugs.
Despite its importance, the rollout of KB5094126 has not been seamless for all users. One administrator managing a fleet of HP devices reported that following the deployment of the June update, numerous PCs encountered boot issues, primarily due to the BitLocker recovery screen or the dreaded Black Screen of Death. The HP EliteBook 840 G10, a model favored by enterprise customers, appears to be particularly susceptible to these problems. However, the complications extend beyond just one model, affecting a range of devices including:
- HP EliteBook 840 G10
- HP ProBook 460 G11 / HP 460 G11
- HP Engage One Pro 15.6 G2 AiO POS
- HP ZBook
- Dell Precision
- Dell Precision 7530
It is important to note that not all users with these devices are experiencing issues, suggesting that the problems may stem from a compatibility conflict between the update and specific BIOS configurations or EFI/System partition settings.
Why is the June 2026 update causing boot failure on some PCs?
According to insights from Windows Latest, the KB5094126 update interacts with Secure Boot-related files, certificates, Boot Manager, or EFI contents. On affected devices, particularly those with older images featuring a 100MB EFI partition instead of the newer 500MB to 1GB partitions, Windows struggles to write the necessary files. This results in boot failures.
For those affected, checking the Event Viewer may reveal numerous TPM-WMI errors, including messages indicating that the secure boot update failed due to insufficient disk space. HP devices are particularly vulnerable because they often store BIOS or firmware recovery files within the EFI partition, which can occupy significant space. Thus, the root of the issue may lie not with the SSD or the Windows installation itself, but rather with the size or condition of the EFI partition.
When attempting to install KB5094126, if the update fails, Secure Boot can prevent Windows from loading, leading to a BSOD with error 0xc0430001. Users with BitLocker enabled may find themselves directed to recovery mode, where they must enter their recovery key.
What to do if your PC is not booting after the Windows 11 June 2026 Update?
For those experiencing a recovery loop or boot failure, a temporary workaround involves disabling Secure Boot. Here’s a step-by-step guide:
- Ensure you have backed up your BitLocker recovery keys or use a Microsoft account, which automatically stores your keys.
- Access BIOS by pressing the Esc key before the OEM logo appears. If this does not work, consult your manufacturer.
- In BIOS, locate the Secure Boot option and disable it. You may be prompted to enter your BitLocker key, which can be found in your Microsoft account.
- Exit BIOS and attempt to boot into Windows. Once in, install the cumulative update.
- Reboot to allow the update to apply successfully.
- Return to BIOS and re-enable Secure Boot.
Additionally, it is advisable to ensure that your BIOS/UEFI is up to date. If the workaround does not resolve the issue, Secure Boot may need to remain disabled until Microsoft or HP provides further guidance. Once Windows is operational, checking for adequate free space in the EFI partition is recommended, as insufficient space may continue to cause problems.
Interestingly, reports of BSODs following the June 2026 update are not limited to Windows Latest’s readership; similar issues have been noted on platforms like Reddit and Microsoft’s Feedback Hub. Given Microsoft’s recent responsiveness to user feedback, an acknowledgment of these issues may be forthcoming.
Windows 11 KB5094126 is breaking File Explorer integration for OneDrive
Another notable issue following the installation of KB5094126 is the disruption of OneDrive integration within File Explorer. Users have reported an inability to access OneDrive from the left pane, tray icon, or existing shortcuts. While the extent of the impact remains unclear, some users have found that uninstalling the update resolves the issue.
Further investigation suggests that the problem may not be confined to OneDrive, as similar issues have been observed with Dropbox and iCloud Drive, although not as widespread as the OneDrive situation.
Is it impossible to access cloud files or folders in File Explorer after the June update?
Not necessarily. Users can still access cloud folders by navigating directly to C:Usersusername, but attempts to open them via File Explorer’s sidebar or system tray may fail. While some users have encountered this problem, others, including those on Windows 11 25H2, have reported no issues. The OneDrive version in use may also play a role, with a newer version currently rolling out, though there is no definitive evidence that updating OneDrive resolves the issue.
Windows Latest has determined that KB5094126 appears to disrupt Explorer’s cloud storage shell integration, particularly on systems with UAC disabled and local admin accounts. Switching to a Microsoft account and enabling UAC may restore normal access to cloud files. Alternatively, users can opt to remove the update and await a fix from Microsoft.
KB5094126 is also breaking Word integration in some business apps
Another confirmed issue involves the June update disrupting Microsoft Word integration within various line-of-business applications, such as dental and accounting software. While Word itself continues to function normally, applications that rely on Word automation for document handling are experiencing failures.
Identified applications affected by this issue include:
- Dentrix
- Softdent
- CCH ProSystem fx Engagement
- CCH ProSystem fx Workpaper Manager
- Older Eaglesoft / SmartDoc
- Neurology software using Word for reports
The exact cause of these disruptions remains unclear, but it appears that a change in how Windows interacts with Office automation may be at fault. Users encountering this issue should consider uninstalling the update via Windows Update > Update History > Uninstall updates, selecting KB5094126, and rebooting to complete the process.
Microsoft quietly changes how desktop.ini works, breaking custom folder icons
In a less publicized alteration, the KB5094126 update has modified the behavior of desktop.ini files, impacting custom folder icons for some users. This file, typically hidden, is utilized by advanced users or third-party applications to customize folder appearances. Following the June update, Windows has become stricter in verifying the authenticity of these files, leading to potential failures in folder customizations.
While this change does not restrict access to folders or files, it does affect how they are displayed in File Explorer for users who have relied on desktop.ini for customization. To restore functionality, users can add the desktop.ini file to Trusted Sites by executing specific commands in PowerShell:
Unblock-File "C:YourFolderPathdesktop.ini"
This command unlocks a single desktop.ini file, while the following command can unlock all desktop.ini files within a folder:
Get-ChildItem "C:YourFolderPath" -Recurse -Filter desktop.ini -Force | Unblock-File
It remains uncertain whether Microsoft will address this behavior in future updates, but it mirrors previous changes observed with the Preview pane in File Explorer.
