Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

How to handle reboots after Windows Updates?

When I'm looking at Windows Updates in PDQ Deploy, I see this linke: A reboot is required but will not be initiated by this deployment, however depending on your environment Windows Update may reboot the computer.

With WSUS, when we patch servers, we do them at a specific time so I guess I could add a manual "Reboot" as a Post-Step. However, if there were multiple patches that needed to be installed, that could mess things up if it rebooted after the wrong one.

When we patch Laptops, we want them to install whenever they want, but then to reboot at night like it does with our current WSUS setup.

What options are there for having PDQ Deploy handle reboots after patches are installed?



Date Votes
  • Inventory - Screenshot 1

    Create dynamic collection for computers that have status of "Needs Reboot".


    Deploy - Screenshot 2, 3, 4 and 5

    Create package that restarts computer. (CMD with shutdown /r or something similar)

    Create a schedule to run package against the collection during after hour. Also disable the option to retry if devices are offline. Otherwise they will restart once they come online. There is no way to set a time frame, but reboot shouldn't take 5 hours, so a time frame is not needed most of the time.

    reboot2 reboot3 reboot4 reboot5

  • You may also give the wuforce.vbs script from Rob Dunn a shot. This way you can force the machine to update and when finished, reboot it.

    I am using this all the time.