Microsoft has finally acknowledged that Windows has issues, and in a new support article , it admitted that there are issues with almost every major core feature of Windows 11.
The issues are related to XAML and this affects all Shell components, such as the Start menu, taskbar, Explorer, and Windows Settings.
Although Microsoft only (officially) acknowledged the issue in November 2025, it has been around since Patch Tuesday July 2025 (KB5062553), which is four months ago. Also, because Windows 11 25H2 shares the same codebase as version 24H2, the latest Windows 11 feature update is also affected.
In the support article, Microsoft states:
“After a computer is given a Windows 11 Monthly Cumulative Update, version 24H2 released in July 2025 or later (KB5062553), various applications such as StartMenuExperiencehost, Search, SystemSettings, Taskbar, or Explorer may experience difficulties.
The company also says that Windows XAML component and package updates for MicrosoftWindows.Client.CBS_cw5n1h2txyewy , Microsoft.UI.Xaml.CBS_8wekyb3d8bbwe , and MicrosoftWindows.Client.Core_cw5n1h2txyewy are causing some of the issues.
The company reports that the following Shell components and related services may fail and report an error on the screen or fail without executing:
- 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
Microsoft says it is preparing a fix, and is currently providing some solutions to address the problems.
First, the company says that restarting the Shell Infrastructure Host service (SIHost.exe) will help restore missing Immersive Shell packages.
This can be done with the following commands:
Add-AppxPackage -Register -Path 'C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\appxmanifest.xml' -DisableDevelopmentMode
Add-AppxPackage -Register -Path 'C:\Windows\SystemApps\Microsoft.UI.Xaml.CBS_8wekyb3d8bbwe\appxmanifest.xml' -DisableDevelopmentMode
Add-AppxPackage -Register -Path 'C:\Windows\SystemApps\MicrosoftWindows.Client.Core_cw5n1h2txyewy\appxmanifest.xml' -DisableDevelopmentMode
As a second solution, the company shared a PowerShell logon script that essentially prevents Explorer from starting prematurely until the required packages are fully operational.
The PowerShell logon script:
@ Echo off
REM Register MicrosoftWindows.Client.CBS
powershell.exe -ExecutionPolicy Bypass -Command “Add-AppxPackage -Register -Path 'C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\appxmanifest.xml' -DisableDevelopmentMode”
REM Register Microsoft.UI.Xaml.CBS
powershell.exe -ExecutionPolicy Bypass -Command “Add-AppxPackage -Register -Path 'C:\Windows\SystemApps\Microsoft.UI.Xaml.CBS_8wekyb3d8bbwe\appxmanifest.xml' -DisableDevelopmentMode”
REM Register MicrosoftWindows.Client.Core
powershell.exe -ExecutionPolicy Bypass -Command “Add-AppxPackage -Register -Path 'C:\Windows\SystemApps\MicrosoftWindows.Client.Core_cw5n1h2txyewy\appxmanifest.xml' -DisableDevelopmentMode”
You can find the support article here (KB5072911).





0 reviews
iGuRu.gr