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.

Reboots from PDQ Deploy randomly don't go through lately

All too often lately, but randomly, reboots sent as part of a PDQ Deploy package don't go through. PDQ Deploy will sit and wait forever for the remote PC to restart, but nothing happens, as if the remote PC never received a restart command. If I notice a reboot sitting in the queue, I will manually send a shutdown command to that PC from my own command line, the PC reboots, and PDQ continues. But it really messes up our process when we've scheduled things to install overnight and the whole thing gets hung up because of a reboot that isn't happening.

I have no idea what's causing this. This problem only started happening in the past few months.

1

Comments

1 comment
Date Votes
  • I'm not sure which method PDQ is using to reboot the machine, but it sounds like there may be a prompt on the user machine that is requiring interaction (an error popup waiting for someone to hit "okay" for example). I've ran into several machines over the last couple days that randomly have an error related to a Windows update component crashing pop up when trying to reboot - the machine will sit there forever until that "ok" button is pressed, then it will finish restarting like normal. This is a different kind of popup than what you'd see if a user had files open that needed saving, or if a machine was locked.

    Which command are you using that works when PDQ doesn't? Using something like shutdown -r -f (or /r /f) forces Windows to ignore all warnings or prompts and restart, but again - haven't ever looked into how PDQ is handling reboots, so I can't say for sure what (if anything) would cause it to hang.

    1