Some people suggests that ShellExperienceHost.exe is making Start Menu unresponsive if it suspends... now, it's supposed it SHOULD suspend and be running only if you click on the start menu, but seems that probably this process is not "waking up" properly if you try to acess the Start Menu...
have anyone tried to monitor that to confirm if the bug comes from there? I could help, but I?m on CU, and no plans to upgrade until graphics stuff and start menu work again XD.
Crikey,...I 've just had the 'Start' menu not working,..totally unresponsive. Same for Cortana as well. I updated (Clean Install) to FCU last week and have the latest Cumulative update. It's been working flawlessly for the past seven days. This morning though, I encountered the unresponsive problems described in this thread when I powered up the PC.
I restarted the PC and thankfully it's all back to normal but this is worrying. I Googled this and it seems a lot of people out there are having this problem.
How can this be a random event in my case after seven days of working flawlessly?
Happened again this morning. Seems to happen every time I start the PC from a Cold Boot. The Start menu, Cortana is unresponsive. Only a forced Restart makes everything work again. I'm on FCU (1709) with latest Cumulative Update.
This is what I see in in Reliability History.
Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:
C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Problem signature
Problem Event Name: MoAppHang
Package Full Name: Microsoft.Windows.ShellExperienceHost_10.0.16299.15_neutral_neutral_cw5n1h2txyewy
Application Name: praid:App
Application Version: 10.0.16299.15
Application Timestamp: 59cda974
Hang Signature: ab9b
Hang Type: 2097152
OS Version: 10.0.16299.2.0.0.768.101
Locale ID: 2057
Additional Hang Signature 1: ab9b89468e42e86e068aa614329a60d9
Additional Hang Signature 2: 867a
Additional Hang Signature 3: 867abc74960808a8cd9bd52b020fc8f3
Additional Hang Signature 4: ab9b
Additional Hang Signature 5: ab9b89468e42e86e068aa614329a60d9
Additional Hang Signature 6: 867a
Additional Hang Signature 7: 867abc74960808a8cd9bd52b020fc8f3
.
Extra information about the problem
Bucket ID: 43a00c1b815b0614b2b86bc70e701302 (133556577791)
This is happening to me but it started a couple of days ago, start button doesn’t open anything as well as the action centre button, I restored from Macrium to last Friday, all worked when I went to sleep (I left the laptop turned on) but this morning problem returned, I’m now restoring back to the 1st Nov but something tells me that will be the same if others are experiencing this problem.
The only way I managed to get around this problem of ShellExperienceHost crashing for several days now is to perform a proper shutdown
with >shutdown /s /f . Seems the new type of shutdown introduced with FCU brings a lot of new issues including problems with Plug and Play Device recognition.
Here is the workaround. It works.
Go to Settings -> Accounts -> Sign In Options and turn off "Use my sign-in info to automatically finish setting up my device after an update or a restart". This appears to prevent the windows start menu hang from happening.
Use sign-in info to auto finish after Update or Restart in Windows 10 User Accounts Tutorials
Last edited by Brink; 06 Nov 2017 at 18:06. Reason: added tutorial link for more info
Hi Geneo.
Here is the workaround. It works.
Go to Settings -> Accounts -> Sign In Options and turn off "Use my sign-in info to automatically finish setting up my device after an update or a restart". This appears to prevent the windows start menu hang from happening.
It certainly does seem to work. I did already try this after reading your comment in another thread this morning about the Start menu issues. It seemed to work for me when I did a reboot from a cold start. Hopefully,..this will fix the issues but only time will tell for me as the problem arises after I shut down the PC of a night and restart in the morning.
Last edited by Brink; 06 Nov 2017 at 18:07. Reason: added tutorial link for more info
Automatically finish setting up PC after update or restart
- Speed up the Windows sign-in process by following these steps to automatically sign in and set up your PC after an update or restart. We'll then lock your device to help keep your account and personal info safe. Do one of the following, depending on which version of Windows 10 you have installed:
- For Windows 10 (Version 1709), select the Start button, select Settings > Accounts > Sign-in options, then make sure Use my sign in info to automatically finish setting up my device after an update or restart is turned on.
- For previous versions of Windows 10, select the Start button, select Settings > Update & security > Window Update > Advanced options, then select the check box next to Use my sign in info to automatically finish setting up my device after an update.
- Note: This option isn’t available if your device is joined to a domain, or if work or email policies are applied to your device by your organization.
Properties
Article ID: 4027599 - Last Review: Oct 17, 2017 - Revision: 5
Applies to Windows 10
This is the information Microsoft provide about this function. For FCU 1709 with Taskbar & Start menu problems >
uncheck this setting and restart your PC.
Last edited by Brink; 06 Nov 2017 at 18:08. Reason: added tutorial link for more info
Go to Settings -> Accounts -> Sign In Options and turn off "Use my sign-in info to automatically finish setting up my device after an update or a restart". This appears to prevent the windows start menu hang from happening.
Last edited by Brink; 06 Nov 2017 at 18:07. Reason: added tutorial link for more info
Quote