Microsoft Confirms Windows 11 25H2 UI Features Broken also Along With 24H2 Following Update
## Technology Update: Windows 11 User Interface Issue
Technology Update: Windows 11 User Interface Issue
Microsoft has identified a significant issue affecting Windows 11 versions 24H2 and 25H2, where critical user interface components fail following the installation of cumulative updates released on or after July 2025.
The issue impacts XAML-dependent modern applications, including File Explorer, the Start menu, System Settings, Taskbar, and Windows Search. Affected users may encounter symptoms ranging from application launch failures to complete desktop rendering failures.
Overview of the Windows 11 UI Breakdown Issue
This issue primarily affects enterprise and managed environments and is unlikely to occur on personal devices. It arises in specific provisioning scenarios, particularly when Windows updates are installed before the first user logon to a persisted operating system installation. Non-persistent environments such as virtual desktop infrastructure (VDI) deployments are especially vulnerable due to timing-related registration failures.
The issue impacts XAML-dependent modern applications, including File Explorer, the Start menu, System Settings, Taskbar, and Windows Search.
In affected environments, users may experience critical failures such as Explorer.exe crashes resulting in black screens, Start menu failures with error messages, and System Settings and other XAML-dependent applications crashing at startup. The root cause is the failure of XAML dependency packages to register in time after a Windows update is installed. Affected packages include Microsoft Windows.Client.CBS, Microsoft.UI.Xaml.CBS, and Microsoft Windows.Client.Core.
While Microsoft is working on a permanent resolution, IT administrators can implement manual workarounds. For persistent installations, administrators should register missing packages using PowerShell's Add-AppxPackage command and restart SiHost. For non-persistent VDI environments, Microsoft recommends a logon script approach using a batch file wrapper to ensure the registration script runs synchronously, blocking Explorer from launching until packages are fully provisioned.
Microsoft is actively developing a resolution and will provide updates as more information becomes available.
Based on reporting by GBHackers.
