W10 Enterprise won't automatically restart and finish installing pending updates outside of active hours.

oQcS3JJ2xdjHwF67 21 Reputation points
2022-02-15T18:33:03.77+00:00

W10 won't automatically restart and install pending updates (feature, cumulative, or otherwise) outside of active hours.

I have two machines isolated in my lab not restarting where Windows update is "pending restart."

One running 20H2 trying to finish a cumulative update: "Restart required: Your device will restart outside of active hours set by your organization."

This promised restart failed to happen over the weekend. No one was using it.

One running 20H2 trying to finish a 21H1 feature update: "Restart required: This update is ready to install! We need your help deciding when to restart so we can finish up."

Not sure why it "needs" the user's input.

I disabled OU inheritance. Consequently, there are just two active GPOs:

1) Set active hours from 8am-10pm

2) Win update target 21H1

  • I don't see any restart attempts in the Windows update logs.
  • Power management is set to "balanced" on one and "high performance" on the other.
    "put computer to sleep" isn't higher than two hours on either machine.
Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,697 questions
Windows
Windows
A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
4,795 questions
Windows 10 Setup
Windows 10 Setup
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Setup: The procedures involved in preparing a software program or application to operate within a computer or mobile device.
1,909 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 39,391 Reputation points
    2022-02-21T23:13:26.98+00:00

    Hello @oQcS3JJ2xdjHwF67

    This is likely because some GPO that is preventing this machines. Even if you disabled the inheritance, the machines may retain some GPO settings. To ensure what is applied, run a GPRESULT /H OUTPUT.HTML and in that output file you will see both User and Computer policies applied.

    The remaining policies may be still stored in the registry, you can try to delete the next keys (after taking a registry backup, for safety):

    Delete the "HKLM\Software\Policies\Microsoft" Key (looks like a folder).
    Delete the "HKCU\Software\Policies\Microsoft" Key
    Delete the "HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects" Key.
    Delete the "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies" Key.

    then execute: gpupdate /force /boot (from an elevated command prompt)

    Hope this helps with your query,

    --------
    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments