Issue
A Windows device continues to show a "Needs Reboot" status in Automox even after it has been restarted.
Environment
- Automox (current agent release)
- Windows 10 / 11, Windows Server
Cause 1: A feature/OS update is still finalizing
After a Windows feature update, WindowsUpdateBox.exe can continue finalizing servicing operations in the background for anywhere from ~30 seconds to several hours. Until it completes, the pending-reboot state — and the Automox flag — remains set.
Cause 2: A prior update left a pending-reboot state a normal restart didn't clear
The "Needs Reboot" flag reflects Windows' own pending-reboot state. A previous update that failed or was interrupted (for example, the device was powered off mid-install) can leave that state set, and an ordinary restart may not clear it. This same lingering pending reboot can also block the next patch from installing — so a stuck flag and subsequent patch failures often share this root cause.
Resolution
- Perform a full shutdown (not just a restart): shut the device down completely, wait at least 30 seconds, then power it back on. This lets Windows complete pending servicing operations.
- Give a recent feature update time to finish finalizing before concluding the flag is stuck.
- Rescan the device in Automox and re-check the status.
- If the device also shows recent patch installs failing, treat a lingering pending reboot as the likely common cause — reboot fully, then rescan.
Notes
If the flag persists after a clean full shutdown and rescan, contact Automox Support with the device name/ID and the agent log.