Microsoft has published a support document that says that Windows 11 updates might cause several system apps to stop working. These issues seem to affect enterprise PCs.
This is what the support page says,
"After provisioning a PC with a Windows 11, version 24H2 or a Windows 11, version 25H2 monthly cumulative update released on or after July 2025 (such as KB5062553 or KB5065789), XAML-dependent modern apps such as Explorer, the Start menu, SystemSettings, Taskbar and Windows Search might experience difficulties"
It mentions some scenarios where Explorer may crash on start, Windows may log on to a black screen. The Taskbar may fail to appear/render/display on the desktop. The Start Menu may fail to open, and display a critical error message. ShellHost.exe could crash. XAML-dependent apps like Consent.exe, which is used for the User Account Control UI, may crash or fail to start. The System Settings page, i.e. Start>Settings>System may fail to open. Apps may crash when initializing XAML views.
Yesterday, Martin wrote about a bug in File Explorer's dark mode that could result in a flash bang. Seriously, what's left to break at this point?
Microsoft says these issues are very unlikely to occur on personal computers, and that they affect a "limited number of enterprise or managed environments". It explained that the affected apps have a dependency on XAML packages, and that these are not registering in time after installing Windows updates.
While it is yet to resolve the problem, the company is recommending some workarounds.
IT administrators managing enterprise or virtualized environments can use the following commands in PowerShell to register the missing packages in the user session, and restart SiHost to allow Immersive Shell and related components to reflect the changes.
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
Microsoft is suggesting users on non-persistent environments to use a logon script, and run it from a batch file before Explorer starts.
@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"
All these issues on Enterprise PCs could make work life miserable. How do so many issues fly under the radar before they are shipped? What exactly is the point of the Windows Insider Program, if testers don't check for serious errors? And why haven't these issues been fixed for months?
As Windows Central's Zac Bowden rightly says, Microsoft has become sloppy when it comes to Windows 11 updates.
Thank you for being a Ghacks reader. The post Microsoft says Windows 11 updates could break the Taskbar, Start Menu, Explorer and more on Enterprise PCs appeared first on gHacks Technology News.
]]>☞ El artículo completo original de Ashwin lo puedes ver aquí