New
#61
Action center will not open.
And when I try, ShellExperienceHost.exe stops.
I must have broken it somehow while trying to fix that other problem:
StartMenuExperienceHost.exe stopped working ...
Help!
StartMenuExperienceHost.exe stopped working ...
-
-
New #62
I just reinstalled with the April iso and noticed that StartMenuExperienceHost.exe has a different date stamp of November 28, 2023, and we had April 9, 2024.
-
New #63
I have now used the startmenu and even right-clicked on the startbutton many times, still no errors logged. I would advise all (except OP) who still get them to log in as an admin and do the actions detailed in post #13, several times to be sure. And when you run the commands be sure to always be online, the powershell script probably downloads a new copy of the file from Microsoft servers, it can't restore it from your local repositories like the DISM commands.
My file was last modified on 10th january 2024, and the signature's time stamp is 28th november 2023.
-
New #64
-
-
New #66
A clean install is gonna bring it right back down through updates. Over in answers.microsoft these "techs" are telling people to reinstall Windows. That is not the solution.
I hope MS is aware of this bug. They should be able to correct it. Who feels like reinstalling Windows lol unless you have a test rig and can try and trouble shoot it. That makes sense.
-
New #67
For now, just living with it.
FWIW, I'm back up to three versions of C++ (via automatic updating).
-
New #68
Someone else else where is complaining there's no solution but it is obvious there are 2 solutions here, one done by i486 and my case clean install.
My case did worked and even after updated to the latest 19045.4291 over a week ago, but then again who knows what will happen next month.
Who ever complaining there, it seems, are not looking for a solution but demanding a fix from Microsoft and have no intention to even to stop the error for now.
-
-
New #69
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 the same thing that happens when I used the Task Manager to end it manually.
Win 10 is that robust, I'll give MS that.
So at this point I'll shrug and wait for a fix.
Meanwhile I did clean up some corrupted files.
-
New #70
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,
DonLast edited by DonT5; 6 Days Ago at 18:03.
Quote
Related Discussions
