An update is stuck
Three different things get called a stuck update. Work out which one you have first, because the fix is different for each.
Which kind is it
| You see | It is |
|---|---|
| The machine is under Overdue or Behind | An operating-system update that is not installing. |
| The machine is under Restart | An update that installed but cannot finish until a restart happens. |
| The machine is under Agent | RemediateDesk's own agent is behind the current version. |
A system update will not install
Open the machine's chat and ask the AI to find out why. It will typically check free disk space, the Windows Update service, any pending restart and the error codes in the update history, then propose a fix for you to approve.
A common finding is a restart that was never done. Installing does not restart the machine, so a pending restart quietly blocks the next update.
A restart is pending
Approve a restart, and pick the maintenance window on the approval card so it happens when nobody is working. A restart always asks, and the card says which kind of notice the person at the machine will get.
The agent is behind
Agents update themselves once a night, and again shortly after the service starts, so a machine that was off overnight catches up when it next starts. A machine that stays behind for days is usually off, offline or failing its own update.
Check it is online first. If it is online and still behind after a night, open the Chat tab and use Restart agent. If that does not help, write to support@remediatedesk.com with the machine name and the version it shows. A reinstall from the company's install panel replaces the agent and keeps the machine's identity.