WUI.exe is crashing after latest Windows 11 updates are installed

Hi Tony DiDonato,

Thanks for the command you shared. It explains the reason why your end users are experiencing this desktop initialization failure. The cmdlet you executed belongs to the third-party PSWindowsUpdate module rather than a native Microsoft deployment tool. While this community module is widely used, applying the forced automatic reboot switch during the installation of a major Cumulative Update like KB5079473 directly interrupts the Component-Based Servicing stack.

When the endpoint is forced to restart before Windows finishes staging the new Appx packages in the background, the system attempts to recover and resume this provisioning during the next user login. This aggressive interruption causes the AppReadiness service, located in the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AppReadiness, to hang indefinitely. Because this service is stalled, the explorer.exe shell is blocked from loading, resulting in the black screen with the hardware cursor. To prevent this from happening across your network, you must remove the forced reboot parameter and allow the native Windows Update Orchestrator to handle the restart cycle gracefully. Moving forward, transitioning your patching strategy to officially supported enterprise platforms like Windows Server Update Services or Microsoft Intune will ensure the update staging phase completes fully before any endpoint reboots are authorized.

Hope this helps :)

VP

Install-WindowsUpdate -KBArticleID KB5079473 -AcceptAll -AutoReboot -Verbose

Hi Tony DiDonato,

How is your issue going? Has it been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)

VP

Hi Tony DiDonato,

Your initial assessment regarding a crashing process is on the right track, but the specific component failing is the primary Windows shell rather than a standalone executable called WUI.exe. When users encounter a blank screen with a responsive mouse cursor immediately following a Windows Update, it indicates the system successfully booted and authenticated, but the operating system failed to launch the explorer.exe process responsible for drawing the taskbar and desktop environment. You can bypass this state immediately by having the user press Control, Alt, and Delete to open Task Manager, selecting the option to run a new task, and typing explorer.exe to manually force the graphical interface online.

To ensure the update did not corrupt the default shell configuration, you should inspect the local registry on an affected machine. Navigate to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon registry path and verify that the string value named Shell is set exactly to explorer.exe. If the registry value is intact, this behavior is most frequently caused by the App Readiness service hanging while attempting to process new application packages during the initial post-update login. You can resolve this network-wide by deploying a script or Group Policy preference to temporarily set the AppReadiness service startup type to Disabled, restarting the affected endpoints, and then reverting the service to its default Manual state once the profiles load successfully.

Hope this answer brought you some useful information. If it did, please hit "accept answer". Should you have any questions, feel free to leave a comment.

VP

The described symptom (blank/black screen with mouse cursor after reboot, GUI never loading) matches a known class of issues where shell/XAML components fail to start after Windows 11 updates, especially in enterprise or managed environments.

Based on the context, the most relevant documented cause is missing or not-yet-registered XAML dependency packages after cumulative updates on Windows 11 24H2/25H2. When these packages fail to register in time, XAML-dependent shell components such as Explorer, Start menu, and other shell hosts can fail to start, resulting in:

• Black screen after logon
• No taskbar or Start menu
• Explorer.exe not starting or crashing immediately

In such cases, the underlying cause is not specifically “WUI.exe” itself, but that the shell and XAML-dependent components cannot initialize because their dependency packages are not properly registered after the update.

Key points from the documented issue:

• Affects Windows 11, version 24H2 and 25H2, primarily in enterprise/managed or non-persistent environments.
• Occurs when monthly cumulative updates (released on or after July 2025) are installed before:
  • First user logon on a persisted OS, or
  • Every user logon on non-persistent/VDI images.
• Impacted components include:
  • Explorer.exe (black screen, no Start menu, no taskbar)
  • StartMenuExperienceHost
  • shellhost.exe
  • Other XAML-dependent apps (Settings, UAC UI, etc.)
• Cause: XAML packages such as MicrosoftWindows.Client.CBS_cw5n1h2txyewy, Microsoft.UI.Xaml.CBS_8wekyb3d8bbwe, and MicrosoftWindows.Client.Core_cw5n1h2txyewy are not registering in time after updates.

For affected enterprise devices, this is a known issue under investigation, and the documented guidance is that a formal resolution is in progress and will be published via the Windows release health/support channel. For now, IT admins should:

• Treat the black-screen-with-cursor condition after updates as a shell/XAML registration problem rather than a generic display driver issue when it appears in these specific Windows 11 24H2/25H2 enterprise scenarios.
• Monitor the official KB for updated remediation steps or permanent fixes as they become available.

If devices are instead showing a black screen with cursor without stop codes but outside the specific 24H2/25H2/XAML scenario, the generic blank-screen troubleshooting guidance applies (checking display mode, graphics reset, Explorer restart via Ctrl+Alt+Del, etc.), but the enterprise/XAML dependency issue is the closest documented match to the described behavior in a managed network after updates.

References:

• KB5072911: Explorer, the Start menu, and other XAML-dependent apps might not start or close unexpectedly on some enterprise devices
• Troubleshooting blank screens in Windows