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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-01-23T21:43:35+00:00

    Yes, the "Plug and Play\Device Install Reboot Required" always accompanies the start menu issue when needing to reboot. I've gone back to 1703 and the task is there in task scheduler as well, but I do not have logging enabled. It seems to start every time windows starts and is in a 'ready' state after that (in case something triggers it).

    Havent been on 1709 for about a month, but when I was on it the start menu issue was basically resolved for me (had not appeared in over a week). I gave up on 1709 due to other issues, ie, slowdowns when exploring my PC drives or directories. As well as inability to send/receive files over wifi with android phones/tabs (due to SMB v2 on 1709 which is buggy). I have no interest to return to 1709 after this.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-23T21:18:25+00:00

    I have experieced this problem just a few times. Here is what I've found.

    "\Microsoft\Windows\Plug and Play\Device Install Reboot Required" is a scheduled task and can be viewed the the Task Scheduler.

    It has two triggers.

    <Triggers>

    <WnfStateChangeTrigger>

    <StateName>7508BCA33D009602</StateName>

    </WnfStateChangeTrigger>

    <LogonTrigger />

    </Triggers>

    The Custom Trigger appears to be a state change from the Windows Notification Facility, which could happen with certain USB device actions.

    The second trigger is to run on every log in.

    The custom action is to invoke \Windows\System32\pnpui.dll, which I suspect is to notify the user about whether a restart is required to finish the action.

    <Actions Context="Users">

    <ComHandler>

    <ClassId>{48794782-6A1F-47B9-BD52-1D5F95D49C1B}</ClassId>

    </ComHandler>

    </Actions>

    I keep a history for scheduled tasks and I have found a case where the task failed with these two errors:

    Task Scheduler failed to complete task "\Microsoft\Windows\Plug and Play\Device Install Reboot Required" , instance "{7ab2254f-cc5f-40b2-8c43-e15dd629b6e3}" , action "Device Installation Reboot Dialog Task" . Additional Data: Error Value: 2147942404.

    Task Scheduler failed to start instance "{7ab2254f-cc5f-40b2-8c43-e15dd629b6e3}" of "\Microsoft\Windows\Plug and Play\Device Install Reboot Required"  task for user "" . Additional Data: Error Value: 2147942404.

    When all is OK, instead of these messages we see Action Completed and Task Completed messages. The time between Action Started and Action Completed may just be a few seconds. I suspect the failure I am seeing is because the action has not completed (is hung) and then I reboot, causing the failures to be logged. Whether the hang is in the pnpui.dll I do not know, but I suspect so.

    I have not found any obvious telltale events at the same time. Should it happen again, I will look  again before rebooting.

    I would interested to know what would happen if someone just disabled the trigger on Log On so see if that would eliminate the problem or cause further trouble.

    I have found rebooting gets by system back to normal. But there are a few things I would like to know:

    1. Is this scheduled task new in 1709?
    2. Why is the task triggered by every log on? I'm wondering what would happen if I just disabled that trigger?
    3. Every time this problem is seen, will we see such errors in the Task History?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-20T07:24:54+00:00

    Same here...I was wonder what the £$%^"£$ M$ has done this time. :-( Time  to buy a Mac! :-P

    Was this answer helpful?

    0 comments