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
Sorry, I missed the fact that you were the thread starter and had the right to mark as 'resolved'. I often see MS employees as marking threads here as resolved and assumed as such.
There are 2 threads on this issue (maybe more), the larger one not marked as resolved yet:
What do you mean "it works"?
That the problem did never occur again since I applied the fix.
How many days have passed before you reached this conclusion?
Five, in which the computer has been restarted at least 20 times, without this issue ever occurring again, whereas it occurred regularly every second boot before I applied the fix.
Many of the supposed 'fixes' for this problem seem to work initially but problem returns, sometimes soon afterwards, sometimes days later.
When a 'fix' makes a systematic fault disappear for an observation time much longer than the recurring period of the fault, I observe that the behaviour of the system has positively changed and I call the fix a fix, not a 'fix'. Then, there are two possibilities:
I and a several others have already tried this fix with the sign-in options WEEKS AGO and it has not fixed it by any means.
I'm so sorry for you.
A fix would have to apply to ALL people who have tried it, not just those for whom it seems to work temporarily.
A fix is a fix when it fixes. This thread was opened by myself. I wrote about my problem, and if my problem gets solved, I write that it is solved. You're free to open a thread about your own problem, which may look very similar but require a different handling in your case. I assume that there are enough differently configured computers in the world to allow for some fixes to be effective for some cases and not for others. If you were a doctor, you wouldn't cure all people that sneeze using the same medicine, would you?
Also, all is "temporary". Nobody cares about a fix on Windows 95 today. Windows updates introduce bugs that immediately complicate people's lives and getting help soon is very important. Marking soon as effective a fix that worked for me may help other people (for which it may be effective too) to find this fix soon. Yet, as you see, I did test it for a reasonable time span.
And finally: according to your statement, who would be entitled to mark a problem as "solved", exactly? And when?
Whomever marked this as answered jumped the gun or does not seem to know much about the issue. This supposed fix is weeks old and it does not work for me and many others.
I did. Sorry, I'm almost sure the question I answered was "did this resolve your issue?", not "did this resolve amuzeini's and the rest of the world's issue?" I will read more carefully next time.
I can now confirm that it works. Kudos!
What do you mean "it works"? How many days have passed before you reached this conclusion? Many of the supposed 'fixes' for this problem seem to work initially but problem returns, sometimes soon afterwards, sometimes days later.
I and a several others have already tried this fix with the sign-in options WEEKS AGO and it has not fixed it by any means. A fix would have to apply to ALL people who have tried it, not just those for whom it seems to work temporarily.
Whomever marked this as answered jumped the gun or does not seem to know much about the issue. This supposed fix is weeks old and it does not work for me and many others.
