"The problem, which "primarily affects a limited number of enterprise or managed environments," occurs on PCs running Windows 11 24H2 or 25H2 with a monthly cumulative update released from July 2025. XAML-dependent modern apps such as the Start menu, Explorer, Windows Search, and the taskbar might abruptly crash or fail to load. The cause, according to Microsoft, is a failure to register certain XAML packages in a timely manner after an update installation. The bad news is that there is no immediate fix, and the workaround involves fiddling with the Windows registry for virtualized environments or a PowerShell script to prevent Explorer launching before the required packages are provisioned."
"Affected users might see a black screen or experience a crash on startup when Explorer loads. The Start menu might fail to open, and the taskbar might not appear on the desktop. Any app that depends on XAML could also crash or fail to start. Microsoft said: "We are working on a resolution and will update this article as more information becomes available." The Copilot company also noted that the issues were "very unlikely to occur on personal devices used by individuals.""
Microsoft admitted that monthly cumulative updates released from July 2025 can prevent timely registration of certain XAML packages, causing crashes or failures in XAML-dependent modern apps. Affected components include the Start menu, Explorer, Windows Search, and the taskbar on Windows 11 24H2 and 25H2 installations. The issue primarily affects enterprise or managed environments, and can occur when updates install before first user logon on persistent installs or before all users log on in non-persistent environments like VDI. No immediate fix is available; workarounds require registry edits for virtualized environments or a PowerShell script to delay Explorer until packages are provisioned. Microsoft is working on a resolution.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]