Deployments and results
Read what each maintenance window, install, scan and restart did on every device, cancel a running deployment and retry failures.
Updated
On this page
A deployment is one run of patching across a set of devices: a maintenance window the schedule opened, an Install now, a scan, a restart, a retry or a pre-download. Patching → Deployments lists them newest first.
Filter the list
- Status: scheduled, running, completed, partial, failed, cancelled.
- Kind: maintenance windows, install now, scans, restarts, retries, pre-downloads.
Open a deployment
- Progress while it runs, updated live from device heartbeats.
- Totals: devices done, failed and skipped, updates installed, restarts scheduled, and the window.
- Skipped devices and why: offline, agent too old, turned off locally, nothing to install, paused, missed window, busy.
- Per device and per update: the result. Failed updates carry their Windows Update or winget error code with a plain-language explanation and what to do next.
- Who: the person who started it, or opened by the schedule, and who chose the updates for a manual install.
Result states
| State | Meaning |
|---|---|
| Completed | Every device finished without failures |
| Partial | Some devices or updates failed, others succeeded |
| Failed | Nothing succeeded |
| Cancelled | Stopped by someone, by turning patch management off, or by a pause |
A device that stops reporting on its job for 15 minutes is marked lost. If later heartbeats show it still running, it's picked up again (unless it was cancelled or paused meanwhile). A job is never sent twice.
Cancel
Cancel stops pending and running devices. They stop between updates; an update already installing finishes, and cancelling doesn't roll back what was installed.
Retry failed
Retry failed creates a retry deployment for the failed and partly failed devices. It reinstalls the updates that failed, timed out or ran out of window. A single failed update can also be retried from the device's Updates tab. Policies can retry a failing update automatically (1–10 attempts) in later windows.
Common failures
| Error | What to do |
|---|---|
| Ran out of window | Lengthen the maintenance window or use Download ahead |
| Needs a licence agreement | Turn on Accept licence agreements in the policy |
| winget not available | The device has no usable winget for the system account; application updates are skipped. Windows updates still install |
| Device restarted during install | The device saved no final result; check it, then retry |
| Needs a signed-in owner or MDM (macOS) | See macOS and Linux updates |
Notifications and webhooks
Failed deployments notify your team if you turned on Patch deployment had failures in Settings → Notifications,
and send the patching.deployment_failed webhook. Completed ones can notify too
(patching.deployment_completed). See Notifications and
Webhooks.
Reports
The Path to 100% patching report summarises compliance, mean time to patch and everything still in the way, including failed installs with their reasons. See Report types.