KB5072911: Multiple symptoms occur after provisioning a PC with a Windows 11, version 24H2 update

Summary

After provisioning a PC with a Windows 11, version 24H2 monthly cumulative update released on or after July 2025 (KB5062553), various apps such as StartMenuExperiencehost, Search, SystemSettings, Taskbar or Explorer might experience difficulties.   

This will occur for the following: 

• First time user logon after a cumulative update was applied.

• All user logons to a non-persistent OS installation such as a virtual desktop infrastructure (VDI) or equivalent as application packages must be installed each logon in such scenarios.

Common symptoms 

Some common symptoms that might occur, include but are not limited to the following: 

XAML components 
These issues typically occur after updates to built-in dependency packages hosting XAML components, such as the following: 

• MicrosoftWindows.Client.CBS_cw5n1h2txyewy

• Microsoft.UI.Xaml.CBS_8wekyb3d8bbwe

• MicrosoftWindows.Client.Core_cw5n1h2txyewy

Shell components  
These shell components may fail and report an on-screen error or silently fail to execute such as the following: 

• Explorer.exe

• shelhost.exe

• StartMenuExperienceHost

• Application crashes when initializing the XAML views

• Explorer running but no taskbar window.

• other XAML island views fail to initialize.

• ImmersiveShell

Other symptoms 
Other symptoms include but are not limited to the following: 

• Explorer crashes

• The Start menu fails to launch, often displaying a critical error message

• System Settings. Start > Settings > System silently fails to launch

• ShellHost.exe crashes

• Application crashes when initializing XAML views

• Explorer running but no taskbar window

• other XAML island views fail to initialize

Cause

The applications have dependency on XAML packages that are not registering in time after installing the update.

Resolution

We are working on a resolution and will provide more information when it is available.

Workarounds

Manual registration of the missing packages 

Register the missing packages in the user session and restart SiHost to allow Immersive Shell and related components to pick them up. To do this, run the following commands to register each of the missing packages:

Run this sample PowerShell script on non-persistent OS installations

For non-persistent environments, a logon script approach remains the best option. Create a batch file wrapper to execute synchronously before Explorer launches.

Note This approach ensures the script runs synchronously, effectively blocking explorer.exe from launching prematurely until the required packages are fully provisioned.