StartMenuExperienceHost.exe stopped working ...

DonT5 said:

I agree with @Meeker Morgan's why bother. Why should I have to do a clean install to fix a problem MS created. I and others have submitted a bug reports in the Feedback Hub whatever good that will do under the same Title as this. We should not have to reinstall Windows to get this fixed and whose to say that it will not come back once you do later on. I have pinned all the Apps that I constantly use to my Task Bar to avoid opening the Start Menu with the exception of restart or shutdown and I have removed all Apps that I had pinned to the Start Menu and I have not seen any errors since I did that. I remember that one of the recent updates said it could effect some apps and it looks as if it did.....the StartMenuExperienceHost App. I bet there are more users that are having this problem but have not noticed it because you can open the Start and you see no problems unless you look in the Event Viewer or the Reliability History. I do not know about you but I am tired of their updates screwing up more than they fix. I went to File Explorer then Windows then System Apps and scrolled down to Microsoft.Windows.StartMenuExperienceHost and I saw that the file was modified on 4/9/2024 at 2:22 PM which was the same date and time I installed the April Patch Tuesday updates KB5037036, KB5037036, and KB5034441 which still to this day has no fix and continues to fail in installation. Now if one of these update did not effect the StartMenuExperienceHost then it was one of these updates Cumulative Update Previews KB5035941, KB5036580 that were installed on 3/27/2024. The StartMenuExperienceHost was not failing before any of these updates were installed. I have tried everything to fix this but I am not going to do a clean install to fix a MS problem. Like @Meeker Morgan said "So at this point I'll shrug and wait for a fix."

Respectfully,
Don

Which build are you running now, 19045.4291 (april cumulative) or 19045.4355 (latest preview update)?

Did you really install KB5036892 - the april cumulative update? You wrote 'KB5037036' twice, so I'm just making sure. If you did, then I find it strange that your file was modified on that day and remains with that same modification date. Have you done the same tasks detailed in post #13? Because I did, and my file shows as having been modified in january, despite the fact that I'm running an up-to-date build of 19045.4291. What I didn't do was install any of march's updates. This might be significant, maybe Microsoft introduced some change in them, but didn't include the same change in aprils updates. This goes against the whole idea of cumulative updates, but mistakes happen. But the deal is that I too got these errors until I ran those aforementioned commands, just as instructed. And as I said, then there's the file's modification date that differs from yours. The cause of this error is obviously more complicated than it seems.