Win 10: start menu not working every other boot, after 1709 update

Anonymous
2017-11-04T13:44:10+00:00

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?

Windows for home | Windows 10 | Performance and system failures

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.

0 comments No comments
Answer accepted by question author
Anonymous
2017-11-27T02:10:06+00:00

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.

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2017-12-08T14:16:36+00:00

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

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

63 additional answers

Sort by: Most helpful
  1. Anonymous
    2017-12-07T10:36:50+00:00

    Hi,

    We'd like to know if you're still experiencing the issue. If you are, please let us know so we can help.

    We'll be waiting for your response.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-12-05T02:09:15+00:00

    Odd. What specific message is shown and what limitations do you see now? Any different from when you tried the above? Did the Privacy setting revert back (I have seen in other posts that new updates can screw with it).

    No specific message is shown, the Start Menu just fails to open.  I tried the above and it seemed to work for a few days, then I got two failures again in these 3 or 4 days.  The Privacy setting has not reverted back.

    I have to added that I use auto sign-in (this is a home PC) so I don't have to enter my outlook password.  If I need to temporarily fix the issue, I have to sign out then sign back in (this time needs a password).

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-12-05T02:02:11+00:00

    Odd. What specific message is shown and what limitations do you see now? Any different from when you tried the above? Did the Privacy setting revert back (I have seen in other posts that new updates can screw with it).

    Was this answer helpful?

    0 comments No comments