An update intended to strengthen Windows 11 security has turned into a nightmare for thousands of users. Starting in June, patch KB5094126 caused black screens and prevented some PCs from restarting normally. These bugs primarily affected a few specific models, notably from HP and Dell.
Microsoft still recommends installing these patches, but this time the impact on stability is raising concerns. Let’s take a closer look at this widespread crash and the possible solutions to get out of this predicament.
Windows 11: Black screens after the June update, causes and symptoms
The KB5094126 update, released during last June’s Patch Tuesday, patches nearly 200 vulnerabilities, including several critical ones. However, it is precisely this update that is causing some PCs to freeze on a black screen at startup. Even worse, an infinite loop on the BitLocker recovery screen is occurring.
HP business laptops—such as the EliteBook 840 G10 and ProBook 460 G11—as well as Dell Precision laptops, are the most affected. An error message 0xc0430001 appears before the screen remains stubbornly black.
The problem lies with the Secure Boot management. Microsoft modifies the certificates and files of the EFI boot, but on EFI partitions that are too small (100 MB), the space becomes insufficient for these additional files.
How to bypass the startup block on Windows 11
The technical support team recommends a somewhat obscure but effective workaround: temporarily disabling Secure Boot in the PC’s BIOS. This frees up the necessary space to complete the update.
Once the update is installed, Secure Boot can be re-enabled. This procedure is primarily intended for advanced users, as it involves sensitive settings.
For others, uninstalling the patch via Settings > Windows Update > Update History remains the simplest solution, even if it leaves some security holes.
Secondary impacts: disruptions in OneDrive, Word, and folder customization
This patch doesn’t just sabotage startup. It also breaks the integration of cloud services like OneDrive, Dropbox, and iCloud Drive in Windows Explorer. Shortcuts remain frozen, especially for local accounts without User Account Control (UAC).
Business applications that control Word via COM (Dentrix, CCH ProSystem fx, etc.) are experiencing issues. Microsoft has also tightened its handling of the desktop.ini file, which removes icon customizations that do not originate from sources deemed trustworthy.
Practical solutions and resources to avoid trouble
While awaiting an official fix, several options are available to victims:
- Temporarily disable Secure Boot to force the update
- Uninstall update KB5094126 to restore stability
- Check cloud settings and UAC configuration
- Follow the specific advice of the PC manufacturer, especially HP or Dell.
- Consult detailed guides like those presented on David Computer scientist Or UBackUp.
Insisting on installing this update without taking precautions can render a machine unusable, causing considerable frustration for users. It is essential to proceed step by step.
Microsoft on alert: what communication strategy will be in place for June’s Patch Tuesday?
Contrary to usual practice, Microsoft had anticipated this issue and published clear recommendations beforehand. This did not prevent the scale of the crisis.
The problem appears to stem from modified EFI files, which conflict with already full partitions. HP also stores its own tools in this sensitive area, further reducing the available space.
Microsoft is working on a fix, but the wait could be long. Until then, vigilance is key to avoid encountering an incomprehensible black screen.
When transparency becomes necessary to limit the impacts
This case illustrates how confusing the closed and opaque nature of Windows systems can be. Digital sovereignty requires greater control and visibility over urgent updates.
It is worth remembering that some free and open source systems offer more granular update management, without taking unexpected risks.
Dialogue with the community is vital, because every bug resolved behind closed doors ends up costing users dearly. Fortunately, alternatives exist, and we shouldn’t hesitate to explore them.
Which PC models are most affected by this bug?
HP EliteBook 840 G10, ProBook 460 G11, ZBook, Engage One Pro PCs and Dell Precision PCs most frequently encounter this black screen problem after the update.
What are the symptoms of a black screen caused by the update?
A frozen screen with error code 0xc0430001 or an indefinite loop on the BitLocker recovery screen at startup.
How to bypass the Secure Boot problem?
Secure Boot must be temporarily disabled in the BIOS, the update applied, and then re-enabled to avoid the system crash.
Can the update be uninstalled if the problem occurs?
Yes, uninstalling update KB5094126 via Settings > Windows Update > Update History restores stability but removes security patches.
Source: www.lesnumeriques.com