Windows updates
The Windows updates page works like the update view of WSUS. It has two tabs:
- Computers lists each Windows host with the build it runs, the newest build of its product, and the updates it is missing. Select a missing count to see the list. Filter the list by Name (part of the computer name), Version (part of the installed build or the Windows release) and Cluster.
- Updates lists each cumulative update of the products in use, with the number of hosts that need it and the number that have it.
- Compliance shows how many Windows hosts follow their policy, per policy, and lists each host that does not, with the reasons.
- Policies sets how updates are installed. See below.
Status of a host
- Up to date: no published update is newer than the installed build.
- Update needed: a security or out-of-band update is missing.
- Optional update: only optional preview updates are missing.
- Unknown: the host runs a product that the update lists do not cover.
A missing update is any published cumulative update with a build newer than the installed one. Cumulative updates include all earlier fixes, so a host with a newer build has every older update too.
Where the data comes from
- Published updates. Once a day the server reads the Microsoft release health tables for Windows 11 and Windows Server, and the Windows 10 update history on the Microsoft support site. Each update is stored with its KB number, build, date and type. Security, optional preview, out-of-band and hotpatch releases are all included.
- Installed build. The agent reads the Windows build from the registry and sends it with the inventory. The server compares it with the published updates. The server does not ask the host whether updates are pending.
Microsoft offers no public interface for the update state of one machine. The comparison is made on the server against what Microsoft publishes.
Policies
A policy decides how the agents of Windows hosts install updates. The Policies tab lists them. Each host follows the default policy, and you can give a host its own policy on the Computers tab. A host cannot opt out: the agent asks its policy what to install, and every Windows host that runs the agent is under one.
- Install approved updates. Off, the policy only reports. Nothing is installed and no host restarts. The default policy starts off, so an upgrade installs nothing by itself. Turn it on when you are ready.
- Deferral. An update is approved this many days after its release.
- Deadline. After this many days an update is forced, even before the deferral is over. Zero means no deadline.
- Restart. Choose one of:
- Never: a restart is left to you. The host shows Restart pending.
- In a restart window: the agent restarts the host inside the window of the policy, when a
restart is pending. The host gets five minutes to log off, which an administrator can
cancel with
shutdown /a. - After the deadline: the agent restarts the host once an update passed its deadline and a restart is pending.
The agent installs the approved updates with the Windows Update Agent, the same service that Windows Update uses. It needs no WSUS server. A failed update shows as the last error of the host on the Computers tab.
Compliance
A computer is compliant when its policy approves no update that it lacks, its last update run did not fail, no restart is pending, and its build is known. Updates that the policy has not approved yet, because the deferral has not passed, do not count against it.
The Compliance tab reports:
- the share of compliant computers, for the whole fleet and for each policy
- computers with an approved update missing, which means the policy should have installed it
- computers with a failed run, with the error the agent reported
- computers waiting for a restart
- computers with an unknown build
A policy that only reports never installs anything. Its computers therefore show as overdue once their deferral has passed. That is what the report is for: it shows what would be installed.
Read the Updates tab
- Needed counts the hosts that have a build older than the update.
- Installed counts the hosts with the update or a newer build.
Select Only needed to hide updates that every host already has.
PDF report
Select PDF report on the page to make a PDF of the Windows hosts and the updates in your scope. It lists each computer with its build, its status and its missing updates, then the updates with the number of hosts that need them. The report also shows when the update lists were read from Microsoft. It is queued like any other report and appears on the Reports page when it is ready. Reports have no AI summary and no filter.
Limits
- Only products in use are shown, and a host shows as unknown when its product is not in the update lists. Windows 10 releases older than 21H2 are not covered.
- A host reports its build with every heartbeat, so a change appears within about a minute. A host that runs an older agent reports it with its inventory instead, which can take up to the inventory interval.
- The build changes only after the restart that finishes an update. A host that Windows Update shows as installed, but that still waits for a restart, keeps its old build until it restarts.
- Updates that are not cumulative, such as .NET or driver updates, are not listed.
- Hotpatch hosts are compared with the hotpatch builds that the release health tables list.
- The approval time follows the server's clock, and the restart window is in the server's time zone. The agent does not check its own clock.
- An update the policy approves is installed on the next update check, which is about once an hour. Test a policy on a few hosts before it installs on all of them.