This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
A few months ago I had a problem with win10: a blue screen every second boot. I searched the web and found a fix, i.e. to disable the fast boot option in the Power Saving Options. Which I did, and it worked.
A few weeks ago I installed the Falls Creators Update (aka 1709), and now I get a strange behaviour. The Start Menu button (the window icon) is totally insensitive. When I click it, nothing happens. If I reboot (with Alt-F4, or with Ctrl-Alt-Del and Task Manager), all goes well, i.e. after reboot the Start Menu works regularly. However, at the next boot, the Start Menu gets insensitive once again.
As it happens every second boot, I have checked the "fast boot" option, thinking that maybe the falls Creators Update had turned it on again. No, it had not, I found it still disabled as it was before the update.
Honestly, I an not sure whether this problem has started occurring RIGHT AFTER the 1709 update, or a few days later. For sure, yet, it didn't happen BEFORE the 1709 update.
There is a detail that may help troubleshooting: in the sessions when Start menu is insensitive, when I reboot, the system shutdown always shows a message "Task Host Window stopping background tasks \Microsoft]Windows\Plug and Play\Device Install Reboot required".
A device install every second boot? Doesn't make sense...
Any clue?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I had the same issue. Here is what I did to solve (yes, SOLVE) the problem.
In Settings, Accounts, Sign In Options, there is a new function in the Privacy section named:
Use my sign-in info to automatically finish setting up my device after an update or restart.
OIt appears to be set to On after installing 1709.
Change it to Off, reboot, and you won't have the Start Menu issue again.
Hope this helps.
This can be a possible solution. My computer has now been restarted six times without any problems...
Regedit
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WpnUserService
Double click on the value (DWORD): "Start"
Change the "Data" to 4 then OK.
Reboot
I would like to change the scheduled task \Microsoft\Windows\Plug and Play\Device Install Reboot Required to wait one minute when starting triggered by a logon. But every time I try to change it, I get an error message "Task Scheduler service is unavailable. Task Scheduler will attempt to reconnect to it."
Is there some trick to being able to modify a system task in the Task Scheduler?
That workaround only works for a limited group of people anyway. The regedit workarounds setting a delay work for most, but still may cause issues with some apps. Setting the pc to require ctrl-alt-del and password entry when logging in seems to always work afaik and doesn’t cause complications, but can be a bit of a PITA. Replacing windowa will work, bit not practical for many. Hope for MS to fix. Take out frutration on cheap inanimate object, channel into creativity, or exercise. Other methods of taking out your frustration could be costly, unhealthy, or land you in jail.
This morning when I booted up I immediately checked the Start button and it was not responding.
I next checked the \Microsoft\Windows\Plug and Play\Device Install Reboot Required task and it was still running when it should have successfully completed. I ended the task (through the Task Scheduler) but that did not correct the issue.
I checked the event logs and there were two errors saying that ShellExperienceHost.exe had stopped responding and was terminated.
Package Microsoft.Windows.ShellExperienceHost_10.0.16299.15_neutral_neutral_cw5n1h2txyewy+App was terminated because it took too long to suspend.
The program ShellExperienceHost.exe version 10.0.16299.15 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. ...
I'm pretty sure now that the failures I previously found in the task history were because I rebooted while the task was still running.
