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
Run the Start menu troubleshooter:
If that does not work, try the following:
Press Windows key + X
Click Task Manager
Click File > New Task (Run)
Type: CMD
Hold down Shift, click OK
Type in at the prompt OR Copy and Paste these one at a time : (Hit enter after each)
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth
Also run the System File Checker utility:
Press Windows key + X
Click Task Manager
Click File > New Task (Run)
Type: CMD
Hold down Shift, click OK
At the Command Prompt, type: sfc/scannow
This will check for any integrity violations
Restart your system
If that does not work, uninstall your display driver.
Boot to the Windows 10 desktop
Press Windows key + X
Click Device Manager
Expand Display adapters
Right click the current display adapter
Click Uninstall
Exit Device Manager
Restart
Windows 10 will automatically reinstall it.
If the above don't work, you have one of two options:
Option 1: perform a repair upgrade to see it repairs the Start menu:
http://answers.microsoft.com/en-us/insider/wiki...
Option 2: Rollback to your previous version of Windows 10:
I'm not surprised you are having trouble with Windows 10 Fall Creators Update.
There seems to be some early adopter issues at this time with Windows 10 1709, if you can, I recommend you downgrade to your previous version until the Fall Creators Update matures with future cumulative updates.
Open Start > Settings > Update & security > Recovery > under Go back to my previous version of Windows 10, click Get started.
Hello,
To fix Start Menu, try to re-register it:
https://www.kapilarya.com/re-register-start-men...
Let us know if this helps!
To begin with: thank you for your help.
I have tried all remedies but rolling back.
Start menu Troubleshooter said that the database of tiles (charms? frames? the message in Italian was "il database dei riquadri è corrotto", I don't know the original english word for "riquadri') was corrupt, but it was unable to repair it.
DISM did not find anything wrong (yet I executed all three commands). By the way: when Start menu doesn't work, Win+X doesn't work either, and when I type CMD, clicking OK with or without shift pressed does the same thing. I don't know what shift was meant for, I suppose it was meant to make the prompt elevated, but it didn't.
SFC /SCANNOW didn't find anything to repair.
Uninstallation and reinstallation of the display driver only had the effect to shuffle all the icons on my dual desktop (sigh).
I don't want to roll back to the previous version, both because it took hours for the new version to install and I don't have hours to spend to roll back, and because I have enough experience with software to know that the rollback features of complex upgrades are most often more buggy than the upgrade themselves, and since this upgrade seems to be ridiculously bugged, I just do not trust its rollback function.
Just one question. I belong to the generation that tried to diagnose the cause before suggesting the remedy (and rarely our remedies were "reboot"), so I'm puzzled why no attention is being paid to the Driver Install Reboot Required message. Is there a way to see WHAT driver is being installed and claims for a reboot? There's a 100% coincidence between receiving that message and having the Start Menu not working, so it seems to me very likely that there is a connection between the two facts, so this might be a clue to understand what's wrong. Is it really so impossible to DIAGNOSE a trouble of Windows nowadays?
Once again: thak you for your help anyway.
