Microsoft Acknowledges UI Issues In Windows 11 25H2 and 24H2 After Latest Update

Microsoft has confirmed user interface glitches in Windows 11 versions 24H2 and 25H2 following monthly cumulative updates released on or after July 2025, such as KB5062553 and KB5065789.

These problems disrupt XAML-dependent modern apps, including File Explorer, the Start menu, System Settings, Taskbar, and Windows Search.

The issues surface primarily in enterprise or managed environments, like virtual desktop infrastructure (VDI) setups, and rarely affect personal consumer devices.

The glitches occur when updates are installed before the first user logon on a persisted OS or during any logon on a non-persistent system, where app packages must reprovision each session.

XAML components fail to register promptly, leading to core shell elements breaking.

Affected users report black screens on Explorer.exe startup, unopenable Start menus with critical errors from StartMenuExperienceHost.exe, Taskbar rendering failures, and shellhost.exe crashes.

Impact On Enterprise Shell and XAML Apps

In enterprise scenarios, specific packages like Microsoft Windows.Client.CBS_cw5n1h2txyewy, Microsoft.UI.Xaml.CBS_8wekyb3d8bbwe, and Microsoft Windows.Client.Core_cw5n1h2txyewy underpins these failures.

Explorer.exe often leads to black screens or crashes, halting desktop rendering. The Start menu displays error dialogs, while Taskbar elements vanish entirely.

XAML-dependent apps compound the chaos: Consent.exe (User Account Control UI) crashes on initialization, System Settings silently fails to launch, and other XAML island views like those in third-party apps refuse to load.

IT teams in VDI environments, such as Azure Virtual Desktop, face repeated disruptions across sessions, as packages do not persist between logons.

Microsoft notes these stem from timing mismatches in XAML package registration post-update.

Workarounds and Path To Resolution

IT administrators can manually register the missing packages via PowerShell in the user session, then restart SiHost.exe to refresh Immersive Shell components. Commands include:

Add-AppxPackage -Register -Path 'C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\appxmanifest.xml' -DisableDevelopmentMode

Repeat for the UI.Xaml.CBS and Client.Core paths.

For non-persistent VDI, deploy a logon batch script wrapper that executes these synchronously before Explorer launches, using powershell.exe -ExecutionPolicy Bypass to bypass restrictions.

Microsoft is developing a permanent fix and promises updates via the support articles: KB5062553 and KB5065789.

Enterprise managers should monitor these for patches, test in staging environments, and apply workarounds to minimize downtime.

This incident underscores the risks of update sequencing in virtualized deployments.