0
Our company has set up a group policy "Turn off auto-restart for updates during active hours" and set the period from 8 am to 11 pm. Everything works fine, but on a single laptop, Windows seems to be ignoring this policy. This is a laptop with Windows 10 Professional v1903 x64 (build 18362.628). At the same time, there are a dozen other laptops with the identical version of Windows, and there the policy works fine.
Today in the morning on a problem laptop, an even more interesting story happened. At 9:50 the next update was installed, a message appeared on the screen about the need for a reboot, the user clicked the "postpone" button. After that, at 10:05 the system automatically rebooted, because of which the user lost some unsaved data!
In the installation log, I see the following events:
9:40 Initiating changes for package KB4532693. Current state is Absent. Target state is Installed. Client id: WindowsUpdateAgent.
9:50 A reboot is necessary before package KB4532693 can be changed to the Installed state.
9:50 Initiating changes for package KB4538674. Current state is Absent. Target state is Installed. Client id: WindowsUpdateAgent.
9:51 A reboot is necessary before package KB4538674 can be changed to the Installed state.
9:51 Initiating changes for package KB4537759. Current state is Absent. Target state is Installed. Client id: WindowsUpdateAgent.
9:51 A reboot is necessary before package KB4537759 can be changed to the Installed state.
At the same time, rsop.msc shows that the policy is applied on the problem laptop, and the Windows Update Center shows active hours from 8 am to 11 pm. What am I missing?
P.S. We use Windows Server 2012 R2 as the domain controller and deploy updates with WSUS.
yurybx
Posted 2020-02-12T13:33:09.450
Reputation: 1
Are there (were there) outstanding updates to be done on this problem computer? Try resetting active hours back to 9 or 10pm. I have run into limits trying to make active hours too long. Mine are 14 hours long. – John – 2020-02-12T13:56:24.233