Explorer seems to suffer from updates that also aim to improve it :)

An old problem with Windows Explorer crashing when its GDI objects got too high, was fixed with a registry patch (mentioned in that old thread). Since that time, Explorer behaved.

Now with the latest 25H2 26200.8524 it started crashing again for a different reason.

Error 0xc000027b (presumably a problem with Microsoft Store but even though I went through the suggested fixes, I doubt this is the reason -- but too early to be certain since I did them last night).

The culprit in the 2-3 crashes I had since the latest Windows update, was Windows.UI.Xaml.dll in \System32.
This seems to be coming from GitHub - microsoft/microsoft-ui-xaml: WinUI: a modern UI framework with a rich set of controls and styles to build dynamic and high-performing Windows applications.

No user programs in the stack trace. Just this .Xaml, CoreMessaging and explorer!CTray starting the crash.
And all that with about 10 Windows Explorer opened folders.

The silly thing gets worse in handling its multiple processes.

Anything obvious comes to mind?

Thanks in advance.

It affects Explorer Patcher which crashes. Rolling back to 8457 fixed the issue. I put Windows Update on pause until later this month so the buggy update doesn't reinstall itself.

Have you tried uninstalling the Graphics Device Interface,[GDI ] and restoring the registry to its original state to see if operations have returned to normal?
Also check your DirectX for any problems,access it by typing ---dxdiag ---into the Search box.
A look through Reliability History may be helpful.Start typing ---reliability ---into the Search box.

NormanF said:

It affects Explorer Patcher which crashes. Rolling back to 8457 fixed the issue. I put Windows Update on pause until later this month so the buggy update doesn't reinstall itself.

Click to expand...

It's interesting that StartAllBack didn't interfere with the update, right?

I think it's "planet wide" but one of the most dreaded sentences you can hear is when it comes from a govt with the words "We are here to help you" !!!!!!!.

Microsoft seem to be one step forward and two steps backwards with a lot of their "Windows improvements". I don't think people mind so much with insider / test builds as these are to trial out new things -- Ms can't possibly try out stuff on every conceivable bit of hardware that Windows runs on -- but at least leave bog standard W11 alone and stable until the next official Retail release etc.

cheers
jimbo

Thank you all for the suggestions.

dxdiag:
no problems found (in all tabs)

Reliability:
No problems other than 3 Explorer crashes on May 30, 2 more on 31st, and 1 for June first. The future looks (un)promising :)

I didn't try uninstalling the graphics drivers. They have been working fine since their installation was way before the Windows update.
I'll restore the registry fix so it supports again the same maximun for GDI objects used by Explorer, but unlikely that it will make a difference.
The value I used is still the same after the Win update. If they decreased the GDI maximum by a lot and forgot to update the registry item I had changed, that could be a problem (in their programming).

Explorer Patcher:
It's not installed in the computer but going back an update and lose the latest improvements (so to speak), will probably fix the problem.

DISM and SFC claimed the system was in perfect health.

I could use an Explorer replacement until a fix is released by MS. So far, I never had any problems with those types of replacements so I'm optimistic.

Cheers.

Btw, can you also post this problem in the feedback hub for the windows dev to fix?

rzom said:

Btw, can you also post this problem in the feedback hub for the windows dev to fix?

Click to expand...

I don't mind but is that the GitHub area I mentioned above or some other place?

A short update to the situation (it's the same), and some new weirdness that I can resolve by rebooting or throwing away the Windows Explorer.

1) Explorer has crashed with the same error a couple more times (last one was yesterday).
There is some sort of warning that I forgot to mention and could point to the reason (wishful thinking here :) )
The mouse starts stuttering, keystrokes are slow to appear or they just never show up. The Explorer crashes a short time later.
Some delay because of my bluetooth mouse/keyboard Logitech combo?

2) Unexplained new weirdness (that might link to the original problem). No dumps are created though so I can't be sure.
Not many Explorer windows are open, lots of tabs on MsEdge and some graphics program working away or has just crashed for its own reasons.
Used RAM at the time is around 38% of the available 64GB. CPU usage is at 2-5% and GPU usage (if not used by graphics) is 1% or so.

At some point, the opened Explorer windows stopped responding (even their close button).
I could only close those windows by Alt-tabbing and closing some window in the process.
I was left with 4 Explorer windows shown in the taskbar that wouldn't open or shown using Alt-tab.
I managed to delete the explorer task through Task Manager after some time (TM wouldn't respond either), got my black (but empty) desktop, restarted the Explorer and was left with my still black and empty desktop. Not even a Windows Explorer link in the taskbar as I usually get.
After getting bored trying different expletives, I restarted Windows and all was well in the world (so to speak).

I have a very bad impression of MS development group since the late 80's and I'm afraid it still remains the same (and maybe worse)...

Regards to all.

kanenas said:

I don't mind but is that the GitHub area I mentioned above or some other place?

Click to expand...

No. Press ctrl + F and windows will open a feedback hub for you to submit your issue and gice logs to them fkr easier triage.