StartMenuExperienceHost.exe stopped working ...

OK so far today. We'll see.

Took an hour and 19 minutes after windows 10 sign-in for the error to happen today. I have been getting it several times a day, same error details. Have been troubleshooting it since April 10th. This is a work computer, windows 10 home, 2016 HP desktop (not in my profile). I have pretty much exhausted possible remedies. The system is working extremely well other than this issue. Had a bunch of windows updates installed yesterday.

OS Build 19045.4412
Experience 1000.19056.1000.0

ok thanks for that info. !

I just found this link after some Google searching and it also has that same command, so maybe it will work. There is another thread jst like this over in MS answer forums. I posted there to see if anyone tried it.

[How To] Re-register Start Menu In Windows 10

- - - Updated - - -

h4X0R said:

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.
Attachment 410043

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.

ok thanks for that info. !

I just found this link after some Google searching and it also has that same command, so maybe it will work. There is another thread jst like this over in MS answer forums. I posted there to see if anyone tried it.

[How To] Re-register Start Menu In Windows 10

PS Same here I'm running disk cleaner and SFC and check Reliability History a couple times a week. Theres probably millions of PC's with the issue but the average user is not checking RH at all.

- - - Updated - - -

I only ran the command which I would assume would be the only thing you need but after rebooting it did not work.

Should I do the first few steps in post #13 first? I don't how that would be related to the command being run in Power Shell that 100% targets the Start menu.

that's right, I did :

Code:

-- Command Prompt (admin)

dism.exe /online /cleanup-image /scanhealth
dism.exe /online /cleanup-image /restorehealth
dism.exe /online /cleanup-image /startcomponentcleanup
sfc /scannow

--- restart
--- 
--- Powershell (admin)

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

seems to have fixed it for me after the May updates. remember to restart after running the commands in cmd and again after powershell. did your sfc scan find any corruption?

h4X0R said:

that's right, I did :

Code:

-- Command Prompt (admin)

dism.exe /online /cleanup-image /scanhealth
dism.exe /online /cleanup-image /restorehealth
dism.exe /online /cleanup-image /startcomponentcleanup
sfc /scannow

--- restart
--- 
--- Powershell (admin)

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

seems to have fixed it for me after the May updates. remember to restart after running the commands in cmd and again after powershell. did your sfc scan find any corruption?

Hello h4X0R,
Hello this is Don and I just ran everything including the DISM Command Lines and ran SFC. SFC did find errors but they were corrected and verified that by running it again. I restarted my computer and then entered the command

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

into Powershell Admin then restarted my computer and now I will check later on tonight and see if it works.

Don

- - - Updated - - -

h4X0R said:

that's right, I did :

Code:

-- Command Prompt (admin)

dism.exe /online /cleanup-image /scanhealth
dism.exe /online /cleanup-image /restorehealth
dism.exe /online /cleanup-image /startcomponentcleanup
sfc /scannow

--- restart
--- 
--- Powershell (admin)

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

seems to have fixed it for me after the May updates. remember to restart after running the commands in cmd and again after powershell. did your sfc scan find any corruption?

This procedure did not work.

Nope again, after almost a day.

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

ahhh bummer I'm not even gonna bother trying it now, and as mentioned MS has to fix this.

Now its a waiting game...

DonT5 said:

Hello h4X0R,
Hello this is Don and I just ran everything including the DISM Command Lines and ran SFC. SFC did find errors but they were corrected and verified that by running it again. I restarted my computer and then entered the command

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

into Powershell Admin then restarted my computer and now I will check later on tonight and see if it works.

Don

- - - Updated - - -




This procedure did not work.

maybe try one more thing:

reboot
login to a different user account
retry the commands you detailed above in your post
reboot and login to your usual account

i

h4X0R said:

maybe try one more thing:

reboot
login to a different user account
retry the commands you detailed above in your post
reboot and login to your usual account

i

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