Microsoft has shipped an emergency fix for a crippling bug in Windows 11 version 24H2 and preview builds of 25H2 that left newly provisioned enterprise machines with a broken shell—blank Start menus, vanishing taskbars, dead Settings panels, and an unresponsive File Explorer. The KB5095093 update, released out-of-band on Thursday, specifically targets organizations that use Windows Autopilot, Windows Deployment Services, or custom provisioning packages to set up new PCs. For affected IT admins, the update is a relief after weeks of escalating reports of “black screen with a cursor” login loops and unusable desktops on freshly imaged devices.

What Actually Changed

The root cause traced back to a logic error in the XAML component responsible for rendering modern shell elements. During the provisioning phase, a race condition could corrupt the tile database and state files that feed the Start menu, Search, and the taskbar, effectively causing all XAML-hosted interfaces to fail. The symptom set was broad: clicking Start would flash and vanish, the Settings app refused to launch, and even the notification center became unresponsive. For users locked into a broken profile, the only workaround was to create a new local account or, in some cases, reimage the device from scratch.

KB5095093 delivers a two-part remedy. First, it hardens the provisioning engine so that the race condition can no longer occur during the critical first-boot sequence. Second, it includes a remediation script that silently runs during update installation, scanning for and repairing corrupted tile data and registry keys on already-provisioned machines. Microsoft confirmed in its advisory that the fix does not roll back any other system changes and requires a reboot.

Crucially, the update is not being pushed to consumer devices via Windows Update’s automatic channel—it is classified as a “targeted” release, meaning it appears only on systems that have previously installed a provisioning-related update (KB5045523 or later) or those manually checked by an admin seeking the fix. This surgical approach minimizes impact on unaffected users while ensuring the patch reaches exactly the machines that need it.

What It Means for You

For Home Users and Small Businesses

If you bought a Windows 11 PC off the shelf at a retailer and set it up with a Microsoft account, you are almost certainly not affected. The bug exclusively impacts machines configured via enterprise provisioning tools, which are rarely used in consumer scenarios. However, if you built your own PC and used a work or school account to sign in during setup, and your organization’s IT policy pushes provisioning packages, you might see the update offered. In that case, installing KB5095093 is safe and recommended—it will not alter any personal files or applications.

For Enterprise IT Administrators

This update is a priority install for any environment that provisions Windows 11 24H2 devices or tests 25H2 Insider Preview builds. The fallout from a broken shell on a newly deployed laptop or virtual desktop can stall rollouts, lock help desk queues, and poison user trust. Microsoft’s advisory (not yet published on the update history page at time of writing, but confirmed via the admin center message center) warns that devices provisioned between January 15 and February 3, 2025, are most likely to exhibit the corruption. Admins should:
- Immediately approve KB5095093 in WSUS or Microsoft Endpoint Manager.
- Add it to any golden images or deployment task sequences.
- Run a compliance report on recently provisioned 24H2 devices to identify those missing the patch.
- For machines already stuck in a broken-shell state, boot into the recovery environment and use System Restore to a point before the provisioning attempt, then apply KB5095093 before retrying the provisioning process.

Microsoft also provided a manual repair method via a command-line tool bundled with the update. Running starttierepair.exe /scan from an elevated prompt in Safe Mode can rebuild the tile database without a full reimage, though the company recommends applying the update as the primary solution.

For Developers and Insiders

Insider builds in the Dev and Beta channels that are labeled 25H2 are also fixed. Developers building provisioning packages or custom deployment solutions for Windows 11 should note that the race condition existed in the ProvTool.exe component and was only reproducible under specific timing conditions—typically on systems with slower SSD controllers or virtual machines with limited vCPUs. The fix alters the sequencing of registry writes during the provisioning phase, which may affect the timing of scripts that rely on immediate shell availability post-provisioning. Testing against a KB5095093-patched image is advised before shipping new tooling.

How We Got Here

The bug first surfaced in late January after organizations began transitioning from Windows 11 23H2 to 24H2 for their device fleets. Several IT admins on Microsoft’s Tech Community forums reported that “freshly enrolled Autopilot devices” would boot to a black screen with only the mouse cursor visible, while the Ctrl+Alt+Del security screen remained accessible. Task Manager could be launched, revealing that Explorer.exe was not loaded, and attempts to manually start it yielded a quick flash and crash.

By early February, Microsoft acknowledged the problem via a support article (unpublished at time of press but referenced in partner communications) and attributed it to “a timing issue in the provisioning framework that may corrupt XAML-dependent applications.” The company initially suggested a workaround: after the first failed boot, an admin could press Shift+F10 to open a command prompt, then run dism /online /cleanup-image /restorehealth followed by an offline re-registration of the Start menu with PowerShell commands. This clumsy approach often failed, and organizations with hundreds of affected devices demanded a real fix.

Enter KB5095093, a rare out-of-band release that falls outside the monthly Patch Tuesday cadence. Historically, shell-breaking bugs of this severity (such as the 2023 Taskbar vanishing act in Windows 11 preview builds) prompted similar rapid responses. The update’s development timeline, as pieced together from build tags in the servicing stack, suggests Microsoft had an internal fix ready within 10 days of the first confirmed reports, then spent an additional two weeks validating the remediation across diverse hardware and VM configurations.

What to Do Now

  1. Check for the update. On a potentially affected device, open Settings → Windows Update → Check for updates. If KB5095093 appears, install it immediately. For managed fleets, sync your update rings or manually import the patch from the Microsoft Update Catalog.
  2. Perform a post-install validation. After reboot, confirm the Start menu, Search, Settings, and taskbar respond normally. Open Event Viewer and look for events from source “Microsoft-Windows-TWinUI/Operational” with event ID 1003—this indicates a successful component repair.
  3. For unrecoverable devices. If a machine is stuck in a login loop and you cannot access Safe Mode, create a bootable Windows 11 installation media and use the “Repair your computer” option. Navigate to Troubleshoot → Advanced options → Command Prompt, then run the repair sequence: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows followed by the DISM command above. Then install KB5095093 via the command line: dism /image:C:\ /add-package /packagepath:D:\updates\windows11.0-kb5095093-x64.msu (adjust paths as needed).
  4. Update deployment images. If you maintain custom WIMs or VHDs, re-capture them after applying the update. For Autopilot deployments, ensure that your Enrollment Status Page settings do not force the user to wait for the shell to fully load before completing—this exacerbates the race condition even with the patch.

For home users who encounter the bug despite not using provisioning (extremely rare; only possible if a third-party “bloatware remover” corrupted the tile store), the same repair steps above apply. However, the simplest path is to create a new local administrator account via Safe Mode, sign in, and then delete the broken profile.

Outlook

Microsoft’s prompt handling of this bug—though painful for the admins caught in its wake—signals a maturing response pipeline for OS-level regressions that directly harm productivity. The out-of-band update model, once reserved for zero-day security threats, is now used for reliability issues with broad enterprise impact. That’s a net positive for organizations that can’t wait four weeks for the next Patch Tuesday.

Looking ahead, the incident underscores the fragility of Windows’ hybrid shell architecture. As more legacy components migrate to modern XAML frameworks, the surface area for such start-up race conditions grows. Insiders note that the 25H2 preview builds include structural changes to the provisioning subsystem that should prevent similar corruption vectors, but until those changes reach production, IT pros should keep a close eye on release notes and budget for extra testing cycles when adopting new feature updates. For now, KB5095093 puts out the immediate fire—and the Start menu is safely back where it belongs.