Recent Windows 11 updates cause Start menu and Explorer to crash in business environments By Beatriz
3 min read
 |
Microsoft has confirmed serious flaws in essential components of Windows 11, such as the Iniciar menu and the Explorador of Arquivos, after installing recent cumulative updates. The problem mainly affects enterprise or managed environments, with systems in versions 24H2 or 25H2 that have received patches starting in July 2025. The company identified the cause in XAML packages that do not register in time, leading to crashes or loading failures.
Symptoms include black screens at startup, menu Iniciar not opening, and missing taskbar. Aplicativos XAML dependents, such as Busca of Windows and Configurações of Sistema, may also stop working. The company is working on a permanent solution, but there is no set date for launch.
These incidents highlight challenges in system provisioning, especially in persistent or non-persistent installations such as virtual desktop infrastructures.
- July 2025 cumulative updates (KB5062553) started reporting.
- Affected versions: Windows 11 24H2 and 25H2.
- Main impact: Ambientes with provisioning before first user login.
Technical cause of failures
The failure occurs when XAML dependency packages do not provision themselves correctly after installing updates. Isso happens in provisioning scenarios, where the system is configured without immediate user login.
Microsoft details that late registration affects modern XAML-based apps. In internal tests, the company reproduced the error in virtual setups, confirming isolation for managed devices.
Administrators report that the problem has persisted since July Patch Tuesday, with spikes after October (KB5066835).
Tested: Windows 11’s ‘faster’ File Explorer (preloaded) is still slower than Windows 10.
—Windows Latest (@WindowsLatest)November 28, 2025
On a 4GB RAM test machine, File Explorer used ~32.4MB of RAM without preloading. After turning on preloading, Windows quietly adds ~35MB more. So Explorer now sits at ~67.4MB in memory…pic.twitter.com/pN3tJor7uf
With Dark Mode, you get File Explorer flash bang! 💥
Symptoms observed in users
Affected users experience black screen when loading Explorador from Arquivos. The Iniciar menu fails to be clicked, and the taskbar disappears from the desktop.
Other apps, such as menu host Iniciar and Busca, display initialization errors. In extreme cases, the system restarts crash loops during boot.
Reports indicate that the error is rare on personal PCs, but common on corporate fleets with automated updates.
Microsoft estimates that less than 5% of provisioned devices show symptoms, based on telemetry data.
Workarounds available for administrators
Administrators can apply a PowerShell script to delay the launch of Explorador until full provisioning. The code checks the XAML package registry before proceeding.
In virtualized environments, edits to the Windows registry prevent premature booting. Microsoft provides the official script on its support portal.
These temporary measures mitigate the impact, but require staging testing before deploying to production.
Steps include:
- Download the provisioning script.
- Run via Group Policy on domains.
- Monitor event logs for confirmation.
Impacted versions and history
The bug appeared with the update KB5062553, in July 2025. Posteriormente, KB5065789 and KB5066835 worsened the cases in 24H2.
Version 25H2, released in the fall, inherited the code base, extending the problem to new deployments. Microsoft updated bulletin KB5072911 in December to include this variant.
Since then, monthly patches have maintained the vulnerability, with reports growing in November. The company prioritized the issue in its fix queue.
Recommended preventive measures
To avoid the error, wait for all users to log in before installing updates on non-persistent setups. In VDI, configure custom boot sequences.
Tests in laboratories simulate provisioning to detect failures early. Microsoft suggests pausing automatic updates in test groups.
Organizations should review update policies to include post-installation XAML checks.
Reactions from the technical community
IT forums discuss the impact on enterprise deployments, with administrators sharing custom scripts. Alguns choose to revert to 23H2 temporarily.
Windows experts warn of delays in the adoption of 24H2, citing stability as a factor. Relatos on social media highlights frustrations with recurring crashes.
Microsoft monitors feedback to speed resolution, promising weekly updates in the newsletter.
Future correction prospects
The company plans a hotfix for January 2026, integrating automatic XAML registration. Testes beta is already circulating on insider channels.
Meanwhile, out-of-band updates address isolated symptoms such as installation loops. Usuários household items remain protected by usage patterns.
The incident reinforces the need for robustness in cumulative updates, especially for hybrid ecosystems.
