New
#21
If post #13 or an in-place upgrade repair install doesn't help, see:
StartMenuExperienceHost.exe Missing or Crash Windows 11/10
for ideas.
If post #13 or an in-place upgrade repair install doesn't help, see:
StartMenuExperienceHost.exe Missing or Crash Windows 11/10
for ideas.
Hello, everybody.
Non of the above works.
I am 99% certain as I have been trying to fix this since the update preview 19045.4239 around 2 weeks ago, the only way to stop the error is to roll back to 19045.4170.
The only thing I have not tried is a full reinstall.
I appreciate a good hint or two from more enlightened users.
Thank you for your reply.
Kindly specifically confirm you tried Step 4 in the link I posted above.
Note that in this thread:
Start menu experience host issue
- what appears to be the same thing was recommended, and the thread is marked solved, albeit without any acknowledgement.
Hello, dalchina.
Yes, I have changed the permission there (Step 4), but no joy.
Just checked and the permission as instructed there.
The errors happen a few times every hour but it looks like if I don't touch Start Menu then may not happen for a few hours.
shadowblade's case seems to be the exact one I am experiencing but unfortunately no solution for me yet.
I just did in place upgrade and the error came back with March updated ISO. The problem reapears in March ISO. Аnd then the new updates appeared and again also errors. I don't think a clean install will work either.
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 that the crashing program starts right up again.
Hanging loose for now.
Same issue here. I just found the thread by Googling some stuff. I'm just gonna wait for MS to fix it. It was their update that broke it for who knows how many users.
I just happen to check Reliability History once a week and found it as others did. No one would know they had the issue w/o checking for problems.
MS has to fix it in my opinion.
There seems to be some randomness to this. I just used the startmenu to access the update settings, gave it a good 15-20 minutes before I shut down, no errors. There was another log entry for an action I did around the same time as using the startmenu that was logged, so it can't be because I didn't give the reliability monitor time to react. Yesterday it seemed like there was always a 10 minute delay between the action and the logged error. The taskbar also calls the shell experience host if I'm not mistaken, so using the system settings in the tray (the ones that open settings especially) or right-clicking on the pinned items or the start button also do so, and if there's an anomaly in the process those actions should trigger the bug. The errors seem to have ceased after I ran the powershell script from an admin account, for now. I'm sure they will come back, like they have for others.
Edit: Nevermind that, the taskbar items don't call up the shell experience host. Only clicking on the start button does this, or loading the menu some other way. Accessing settings without going through start menu might also.
Last edited by i486; 14 Apr 2024 at 06:37.
I just noticed this last night:
The process is running but with UAC virtualization disabled.
Should it be enabled, and if so how?
Just grasping at straws here.
Considering your first screenshot:
If you search for ucrtbase.dll Exception code: 0xc0000409 you will find a good many results..
That comes from a VC++ runtime.
This suggests repairing/reinstalling the VC++ runtime. Problem would be you probably have several installed.
What Is Ucrtbase.dll & How to Fix the Related Errors? [Answered] - MiniTool Partition Wizard