Microsoft finally fixes bug that broke all major Windows 11 core UI components on some PCs

The bug-fix for a problem that broke XAML Windows 11 shell components should roll out soon to all PCs in the upcoming Patch Tuesday update.

Last month Microsoft rolled out a new OOBE (out-of-box experience) update for Windows 11 25H2 and 24H2 PCs under KB5095189.

The OOBE is the initial OS setup that happens immediately after Windows completes its installation process. This was pushed out alongside new setup and recovery updates, KB5102558 and KB5095615, that accompanied the C-release preview update for the month of June under KB5095093.

It was a big release for sure with a long list of changes and improvements including some major bug fixes. For example the company fixed a storage-hogging bug that was gobbling up several gigabytes of space due to an issue with its Capability Access Manager process, a default Windows service.

Alongside that the company has also announced a fix for another big problem that was affecting certain systems wherein almost all the Shell components were broken. Therefore it essentially affected the Start menu, Search bar, Settings, Taskbar, and File Explorer, which basically means every core UI element. The problem was primarily on provisioned PCs due to compatibility conflicts with XAML. The company provided an updated workaround for it earlier this year in January.

Interestingly, Microsoft had acknowledged that the bug was present since July 2025, and finally, after almost exactly one year, the company has at long last fixed the issue with the latest C-release and as such, the fix should roll out with the upcoming Patch Tuesday to all users. Microsoft writes:

This is[*sic] issue is addressed starting with Windows updates released June 23, 2026 (KB5095093). This resolution is gradually rolling out and will be fully available in the following month in a monthly Windows update. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.

In the meantime the company has recommended that users opt for the workarounds (linked above) that were previously provided till the fix rolls out to them. You can check out the official support article here under KB5072911 on Microsoft's website.

Source

Hope you enjoyed this news post. Feedback welcome.

Posted Monday 6 July 2026 at 7:29 am AEST (my time).

News posts: 2023 5,800+ | 2024 5,700+ | 2025 5,700+ | 2026 (to end of June) 2,475

RIP Matrix