Could be something nefarious, but my best guess is sloppiness and incompetence.

I did that already once. Even created the other account for the purpose.
Nope.

Nope again, after almost a day.

Still can't figure out what user action (if any) correlates with the failure.

OK so far today. We'll see.

I wonder what exactly it's doing, because the reliability history stuff are the only symptoms.
I have yet to catch the start menu doing anything obviously flakey.

Still doing it, and I'm up to date on updates.

Still just riding it out. Thank you.

FWIW, the DISM routine did fix some corrupted files for me, even if it didn't fix my original problem.

Edition Windows 10 Home
Version 22H2
Installed on ‎2021-‎01-‎01
OS build 19045.4355
Experience Windows Feature Experience Pack 1000.19056.1000.0

Still not fixed.

If I go a week without it happening I'll report and mark it solved,

Why bother? The only way I even know it's happening is by looking at the reliability monitor.
And whenever the fault occurs (once per session) the service starts right up again invisibly.
This is...

For now, just living with it.

FWIW, I'm back up to three versions of C++ (via automatic updating).

Can this be done without wiping user data, or will I need to restore afterwards?
Of course one backs up first just in case.

And when I try, ShellExperienceHost.exe stops.

I must have broken it somehow while trying to fix that other problem:...

Sorry. It happened again just now.
Though I think the C++ fix was still needed.

For now, just back to waiting for the next update.

Unconditional surrender? No thanks.

It was 3, cut it down to one (as previously described), and today's update brought it up to 2.

Still OK, but I'll give it a few days.

If this is really fixed now, I suspect the correct fix was the C++ thing all along, though the other attempted fixes don't seem to have hurt anything....

Read down the whole thread. Also, not certain it's fixed.

So far so good, but I said that before.
After a few days, I may nark it solved (I hope).

Even if this fix works, I still think MS broke something with that update.
Lack of regression testing is...

Uninstalled two versions (x86 and 64) of 2008 redistributable. Option to "Change" did not exist.

"Change" on this one.

https://i.imgur.com/LxAI86Q.jpeg

I'll report back later.

I just noticed this last night:

https://i.imgur.com/X7Vu3wO.jpeg

The process is running but with UAC virtualization disabled.
Should it be enabled, and if so how?

Just grasping at straws...

Happened to me again. I'm convinced that update broke something.
If it's really not just me there is some chance Microsoft will fix it, but not necessarily.
Meanwhile the system is robust enough...

So -- reg cleaners for specialized purposes but not routine maintenance.

You do what I do.