Windows 11 KB5072911 for 24H2 and 25H2
Microsoft just published KB5072911 for Windows 11 24H2 and 25H2 versions. This article discusses an issue that might cause Explorer, the Start menu, and other XAML-dependent apps on some enterprise devices to either refuse to start or close unexpectedly.
While most users will probably see no issue at all, some IT pros managing specific environments might need to pay attention. Large enterprises and virtual desktop setups (VDI) are examples of environments where the system is subject to strict control.
So what's going on? Some users have reported problems getting certain core Windows apps running properly right after installing this latest cumulative update. Apps built using XAML can sometimes refuse to start or just crash randomly as soon as you log in.
This problem doesn't sound like something happening everywhere, though. Organizations with centrally managed devices appear to be the primary target of this issue. For regular home users logging into their own laptops, this update likely won't cause a ripple unless they're running very specific versions and have other weird stuff going on.
Reports suggest the problem often pops up in two main situations: straight after installing Windows 11 for the first time ever (especially following any July updates) or when users log into non-persistent environments like VDI, where packages get reset between sessions. In these cases, Explorer and other XAML apps might struggle to launch.
Beyond just not starting smoothly, some have encountered errors related to shell components, parts of Windows essential for the desktop experience. Things can range from a frustrating black screen upon login (meaning you're locked out) to failures opening the Start menu or Explorer itself, right up to weird issues with the taskbar, like it appearing but acting buggy.
It seems these glitches are linked to some package registration hiccups that occur during update installs. Basically, certain XAML libraries might not be correctly set up after the patch, causing dependent apps to misbehave from the get-go.
Microsoft is clearly aware and working on a solution. But for those affected environments now, there's one potential workaround being discussed: trying to manually register the specific XAML packages within each user session before restarting SiHost.
If your organization is seeing this stuff happen, checking out their official KB5072911 support article below might be worth it:
KB5072911: Explorer, the Start menu, and other XAML-dependent apps might not start or close unexpectedly on some enterprise devices
