StartMenuExperienceHost.exe stopped working ...

DonT5 said:

I just opened the Start Menu as I had to reinstall an App and wanted to pin it to my taskbar and as soon as I did the **** StartMenuExperienceHost failed again so sorry to report that the latest Preview Cumulative Update KB5036969 did not fix the error we have been getting. @Meeker Morgan and @qbdp .

Hey Don,

Have you heard back from MS or gotten any info that they are aware of this issue that is plaguing I assume every one who got these latest updates?

22Green said:

Hey Don,

Have you heard back from MS or gotten any info that they are aware of this issue that is plaguing I assume every one who got these latest updates?

I have not heard a word from MS but I did get some new reply's with other members having the problem as well. I did get this :

In your discussions with other users, I noticed that you have previously submitted this question in the Feedback Center. If it's convenient, would you please share this link here so that we can vote for you.

We have also submitted this question through internal channels. If you can share this feedback link, we will submit your feedback content to the relevant team for investigation through internal channels.

Best Regards,

Mitchell | Microsoft Community Support Specialist

Regards,
Don

Still just riding it out. Thank you.

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

Same here. looks like MS is not going to address it - anyone get any feed back from them? I'll do a sys restore back till March I guess and then hide all updates till it gets fixed. Its annoying seeing all these red X's in reliability history.

22Green said:

Same here. looks like MS is not going to address it - anyone get any feed back from them? I'll do a sys restore back till March I guess and then hide all updates till it gets fixed. Its annoying seeing all these red X's in reliability history.

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.

Meeker Morgan said:

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.

I just finished installing the latest Patch Tuesday updates. I will let you know if these solved the problem which I will be surprised if it does.

Don

- - - Updated - - -

DonT5 said:

I just finished installing the latest Patch Tuesday updates. I will let you know if these solved the problem which I will be surprised if it does.

Don

Guess what? Just as I suspected it was not fixed. I am so sick of this c**p.

Don

- - - Updated - - -

I have posted a new FeedBack Hub post here https://aka.ms/AAqgy2h so please go there everybody and ask them the same question I asked them about why this has not been fixed.

Don

h4X0R said:

Had the same problem on win 10 22H2 19045.4291, which started happening a couple of days after the April updates.
Process in post #13 seems to have fixed it. - thanks

Attachment 408333

So that post fixed your issue complexity? Your post was a month ago and right now if you check Reliability History you have no errors? I must have missed your post because everyone else said it didn't work for them. I was curious to see if you are fixed up.

Thanks

22Green said:

So that post fixed your issue complexity? Your post was a month ago and right now if you check Reliability History you have no errors? I must have missed your post because everyone else said it didn't work for them. I was curious to see if you are fixed up.

Thanks

yes, it was fixed for me until the May updates came through yesterday.

I retried the process in #13 which unfortunately didn't work this time. However, I retried the process in #13 using the following command in the powershell step:

Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode （$_.installlocation + “\appxmetadata\appxbundlemanifest.xml”）}

So far it's working fine - no issues since yesterday.


Note: I routinely run diskcleaner, sfc /scannow and create macrium system backups before installing monthly windows updates. After I installed the May updates and went through the process in #13, sfc found and repaired corruption, so clearly the updates are messing something up.