question

Hi midhunPS-0986,

Thanks for your posting on Q&A.

It is difficult for us to restart the computer manually after installing updates in Windows 10. It is recommended to refer to the following policies to configure:

1. Patch needs to install on a specific day and time.

2. Post successful patch installation suppress the reboot, engineer will login and perform the reboot manually.

Here is the below policy about restarting the computer for your reference:

(Location: Group Policy Management Editor\Policies\Administrative Templates\Windows Components\Windows Update)
This policy does help to restart the computer manually after installing the updates when the user logs in. But if there is no one login after installing updates, the computer will restart as usual.

3. User should receive a periodic popup when the patch is install and also when its in the pending reboot state.

WSUS does not have this feature currently. This may need to be implemented using a script. I may need more time to research.

Regards,
Rita

---

If the response is helpful, please click "Accept Answer" and upvote it.

[2]: /answers/storage/attachments/21370-15.png

[4]: /answers/storage/attachments/21404-17.png

For the popup and alternative thoughts on how to deploy updates, check out part 4 of my 8 part blog series on How To Setup, Manage, and Maintain WSUS.

https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-4-creating-your-gpos-for-an-inheritance-setup/

For the popup - please scroll down to the section entitled:

I Want Notifications!!!

Thanks for the detailed explanation.

If WSUS doesn't have any option for manual reboot, how long we can extend or configure the Automatic reboot.
Like post patch installation, reboot pending, wait for 15 days for auto reboot, in between Admin can reboot.

Hi midhunPS-0986,

We could apply the following policy on the client to pend restart:

[Specify deadline before auto-restart for update installation]

(Location: Group Policy Management Editor\Policies\Administrative Templates\Windows Components\Windows Update)

Reference picture:

Please note that the policy has a conflict with the following policies:
1. No auto-restart with logged on users for scheduled automatic updates installations.
2. Always automatically restart at scheduled time.

Regards,
Rita

---

If the response is helpful, please click "Accept Answer" and upvote it.

Thanks Rita, I will test this on a server 2019 and will update the status soon..

Hi

My 2019 server was waited for only 15 mints for reboot even though I have selected for 30 days. I can see the attached options for scheduled the update but its a manual activity. One more thing I was using a deadline for that approval. Please check and help me

Thanks for the update.

I read that if we configure the deadline from WSUS console, it will override the policy Specify deadline before auto-restart for update installation and will perform an immediate reboot.
So I have approved patch without deadline, Patch installed successfully on scheduled time and waited for reboot. But the dialogue box shows that machine will reboot out of the active hours and I have the options for reschedule or restart now (same mentioned in my last post).

I have selected 30 days for the policy (Specify deadline before auto-restart for update installation.) but again server restarted after 3 hours in the non active hours.

Is there anyway can we disable the reboot of active hours ? server OS is windows server 2019.

Thanks Rita, going through many other forums understood that many others are facing the same situation and not sure MS is doing something for this. please find below the WSUS deadline explained article.

https://docs.microsoft.com/de-de/security-updates/windowsupdateservices/18127631

Hi MidhunPS,

we released this policy back in January 2020 specifically for servers which are affected by default active hours reboot behavior, this way the server does not reboot unless you press the restart now button or schedule the reboot (WSUS deadlines still override policies so do not deploy updates with mandatory deadline if you want to avoid this):

If you do not see this policies, please apply the latest ADMX templates from 2004:
https://support.microsoft.com/en-us/help/3087759/how-to-create-and-manage-the-central-store-for-group-policy-administra

HTH,
Andrei