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
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
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

63 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2017-12-16T02:20:26+00:00

    Changing the Dword value to 4 disables the WpnUserService.

    More info: https://technet.microsoft.com/en-us/library/cc959920.aspx

    Although this seems to be working for me (4-5 days so far), not ruling it a fix until more time passes. Seen too many supposed fixes that worked temporarily only for the problem to return after days gone by.

    Also not comfortable with disabling the WPNUserService entirely, as some users reported possible issues with some software that depends on it (ie, Logitech Setpoint not working).

    Alternative to disabling the WPN service are these options:

    Under same reg key (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WpnUserService)...

    • create new DWORD "DelayedAutostart" and set it to 1
    • create new DWORD "AutoStartDelay" and set it for example to 300 (for 5 minutes start delay)

    Hi,

    Is the AutoStartDelay related to starting Windows or just delaying the service?

    Also, I wonder if instead of disabling the WPN service, can we set the service to be started Manually (use 3 instead of 4) so that software that depends on it can still start it later?

    Thanks!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-12-13T14:17:18+00:00

    Changing the Dword value to 4 disables the WpnUserService.

    More info: https://technet.microsoft.com/en-us/library/cc959920.aspx

    Although this seems to be working for me (4-5 days so far), not ruling it a fix until more time passes. Seen too many supposed fixes that worked temporarily only for the problem to return after days gone by.

    Also not comfortable with disabling the WPNUserService entirely, as some users reported possible issues with some software that depends on it (ie, Logitech Setpoint not working).

    Alternative to disabling the WPN service are these options:

    Under same reg key (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WpnUserService)...

    • create new DWORD "DelayedAutostart" and set it to 1
    • create new DWORD "AutoStartDelay" and set it for example to 300 (for 5 minutes start delay)

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2017-12-13T14:02:31+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

    This worked for me.  My Start Menu would not work after doing a 'Restart'  but would work after a 'Shut Down' and Power up after the upgrade to 1709.

    What changing this DWORD actuall does I'm curious to know but it has cured my Start Menu not working after 'Restart'.  What does it do?

    Anyway, many thanks.

    Was this answer helpful?

    0 comments