Microsoft Acknowledges Windows 11 UI Issues Affecting Enterprise Systems
In recent developments, Microsoft has publicly recognized that certain graphical elements of Windows 11, including essential features like the Explorer, Start Menu, and Taskbar, are experiencing malfunctions on select enterprise and office systems. This acknowledgment comes amidst rising concerns among IT administrators managing Windows 11 environments.
Details of the Issue
According to a support article aimed at IT and system administrators, the root of the problem lies within XAML—an essential markup language for developing Windows applications. Microsoft further elaborated on this situation today, emphasizing that the issues surfaced following the release of the July 2025 Patch Tuesday update (KB5062553), particularly impacting provisioned Windows 11 24H2 PCs.
Potential for Broader Impact
In our previous analysis, we hypothesized that the forthcoming version 25H2 might also be affected due to shared codebases and servicing branches with the currently impacted 24H2. Consequently, the latest Windows 11 update, KB5070311, may also experience similar issues.
Impact on Home Users
Fortunately, Microsoft reassured users that these issues are less likely to affect personal home PCs. The company clarified that problems with XAML-dependent applications such as the Explorer, Start menu, Taskbar, and Windows Search mainly pose challenges in managed environments, thus sparing individual systems.
Identified Bugs and Symptoms
In an effort to clarify the impact of these issues, Microsoft has released an updated table summarizing the specific bugs and their associated symptoms:
| Binary | Enterprise User Experience or Failure Signature |
|---|---|
| Explorer.exe |
|
| StartMenuExperienceHost |
|
| shellhost.exe |
|
| XAML-dependent apps |
|
Workarounds and Fixes
To mitigate these issues, Microsoft suggests a straightforward workaround: restarting the Shell Infrastructure host (SIHost.exe) service can help restore missing Immersive Shell packages. Administrators can implement this fix using 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
Additionally, a PowerShell login script is available to prevent Explorer from launching prematurely before the necessary packages are fully provisioned. The necessary batch script is as follows:
@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”
For further information, the full support article detailing these bugs and potential resolutions can be found here under KB5072911 on Microsoft’s official site.
Leave a Reply