About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
A server being 'compliant' in a patch report means only that it matches whatever the report counts. The status words that produce that result are narrower than they sound. In the terms used by Windows Server Update Services (WSUS, Microsoft's update management service for Windows), "installed" and "not applicable" are counted together, "needed" includes updates that are already installed but waiting for a restart, and "no status" means the server has not reported at all.
So a high compliance figure can coexist with servers that are exposed. The two statuses to read most carefully are pending restart and no status. The rest of this guide defines each status from Microsoft's documentation, shows where a report can mislead, and ends with checks and questions you can use on a real report.
Why it matters
Patch compliance is a figure that boards, insurers and customers ask for, and it is usually a single percentage. A percentage hides which servers fall into the remainder and why. Two servers can both count as non-compliant for opposite reasons: one has a failed installation that needs repair, the other has finished installing and needs only a restart.
A server that has installed an update but not restarted is not yet running the new code. Microsoft's definition of the pending-restart state puts it plainly: the update is installed "but the update does not take effect until the user restarts the computer" (Microsoft, UpdateInstallationState). In practice, that gap is where exposure can persist, because a report that records "installed" may not tell you whether the restart happened (our reading).
This article is about reading statuses. It does not cover how often to patch or how to schedule restarts; for that, see the existing article on patching hosted Windows applications.
What a report is built from
A patch report has three ingredients, and each can change the result.
- The set of updates counted. WSUS reports against updates it knows about and has approved or is tracking. Microsoft notes that an update set to Not Approved "will remain in the default list of available updates and will report client compliance, but won't be installed on clients" (Microsoft, Updates Operations). So an update can show in a report without anyone intending it to be installed.
- The set of computers counted. A report covers computers that have registered with the update server. A server that was never enrolled, or has stopped contacting it, is missing from the numbers or sits in a status of its own.
- The time of the last report from each computer. Statuses are what each computer last told the server, not what is true now.
Our reading: before trusting a percentage, ask what the denominator is. Which updates, which computers, and measured when.
The statuses, one at a time
These definitions come from Microsoft's WSUS documentation. Other tools, including third-party management tools, use their own labels, and we have not reviewed them here.
Installed and Installed/Not Applicable
For a single update on a single computer, installed means the update "is installed on the computer" (Microsoft, Terminology for Update Status; the page content is in English at the German-locale address we fetched). In the group view, "Installed/Not Applicable" is a single column. For one computer Microsoft says it "means the update is not applicable to or required by that computer", and for a group it shows the number of computers for which the update is not applicable or not required.
The consequence is that a high figure here can be made up partly of computers that simply do not need the update. That is correct behaviour, but it means the number should not be read as 'this many servers have the patch'.
One legitimate source of not-applicable results is replacement. Microsoft's documentation says "the superseded update becomes Not Applicable to a computer or device once the newer update has been installed" (Updates Operations page, above). An older update that is not applicable may therefore be a sign of progress.
Needed
For one computer, needed means the update is compatible with the computer and should be installed. Microsoft lists several situations that produce it, including that you have approved the update but the computer has not contacted the server since; that the update has been downloaded but not installed; that it has been neither downloaded nor installed; and that "the client computer must be restarted before changes go into effect, and the client computer has not yet been restarted" (Terminology page, above).
Needed is therefore a broad status. It covers a server that has not been told yet, a server that has not tried, and a server that has finished and is waiting for a restart. Those need different actions, so a count of needed servers is only a starting point for a list.
Pending restart
Microsoft's programming documentation lists a state called InstalledPendingReboot, described as an update installed on the client but not taking effect until a restart (UpdateInstallationState). The PowerShell cmdlet for WSUS also accepts InstalledPendingReboot as a state value (Microsoft, Get-WsusComputer).
The console's own status table, in the pages we read, does not list pending restart as a separate word. From the Needed definition above, our understanding is that the console files such servers under Needed. A report built from the console may therefore show a restart-pending server as simply not done.
Failed
Failed means "an error occurred when either a detection or an installation was attempted on the computer for the update" (Terminology page, above). Detection is the check of whether the update applies; installation is the attempt to apply it. The programming reference describes the same state as the installation failing on the client.
A failed update is an action item with a cause behind it, such as a servicing fault, disk space or a conflicting package. Repeated failure of the same update on the same server is the case to escalate.
No status
This status "usually means that since the time that the update was synchronized to the WSUS server, the computer has not contacted the WSUS server" (Terminology page, above). The programming reference has a related state, Unknown, noting that the client "may not have synchronized with the WSUS server".
This is the most dangerous word in the report because it says nothing about the server. It may be patched, unpatched or off. Our recommendation: treat no status as unpatched until a report arrives.
Last contacted
Microsoft defines this as "the date on which the computer last contacted the WSUS server". It is the freshness stamp for everything else on that row. A server showing Installed/Not Applicable with a last contact several weeks ago is telling you about the past.
How a report can look healthy and not be
These patterns follow from the definitions above. They are our reading and not documented failure cases.
- Not applicable inflates the good column. If many updates are not applicable to a server, the combined Installed/Not Applicable figure rises without any patching.
- Pending restart hides inside needed or installed. A report that counts installed without checking restart state can overstate the protection, and a report that counts needed can understate what is already done.
- Silent servers fall out of the denominator. A server that stops reporting may disappear from a percentage that only counts reporting servers.
- A single update is not a policy. A report on one month's update says nothing about earlier months or about updates not approved.
Read-only checks
The following checks only read information. We did not run them, and output will depend on your update server version and configuration. Check the cmdlet's documentation for your version first.
PowerShell, run on a WSUS server with the UpdateServices module:
Get-WsusComputer -ComputerUpdateStatus FailedOrNeeded
The documentation says -ComputerUpdateStatus specifies "the computer update state as represented in the WSUS Console user interface", and FailedOrNeeded is one of its accepted values (Get-WsusComputer). This lists computers with failed or needed updates.
PowerShell, on the same server, to find computers that have not reported since a chosen date:
Get-WsusComputer -ToLastReportedStatusTime ([datetime]'2026-11-01')
The documentation says -ToLastReportedStatusTime specifies the latest reported status time to search for. Pick a date one cycle ago. The result lists computers whose last report is older than that.
PowerShell, on an individual server, to list installed hotfixes:
Get-HotFix
Get-HotFix lists the hotfixes installed on a computer. It cannot show updates that are pending, failed or needed, so it only confirms what is already installed.
Without command-line access, a provider can export or show you the same data. Ask for: the date of the last report from each server, the list of servers in failed, needed and no-status states, and the restart state of each server.
Questions to put to your provider
- Which tool produces the 'compliant' figure, and what are its status labels?
- What is the denominator: which servers, which updates, and as of what date?
- Are servers with no status counted as compliant, non-compliant or excluded?
- How are servers pending restart reported, and who is responsible for the restart?
- How many servers have been pending restart for longer than one patch cycle, and why?
- For failed updates, what is the ticket, the cause and the expected fix date?
- Does your report show the date each server last reported?
A worked example (illustrative)
The following is invented. A firm is told its eight Windows servers are 75 per cent compliant. Asked what the denominator is, the provider says the figure counts servers (6 of 8 servers = 75 per cent), not individual updates, and that a server counts as compliant only if it is installed or not applicable for every approved update. (A report that counted each server-and-update pair instead would give a different percentage from the same data, which is why the denominator matters.) The detail is that six servers are installed or not applicable, one has a failed update with a clear cause, and one is needed. Looking closer at the needed server, the provider finds the update was installed three weeks ago and the server has been waiting for a restart ever since, because the restart window was never agreed with the firm's accounting team.
The headline figure was true for the percentage it measured. The exposed server was the restart-pending one, which the headline did not isolate. The firm and provider agree a monthly restart window and a rule that any restart pending beyond one cycle is escalated.
Read next
Related articles you may want next.
- HostingReading an availability figure in a service report: what was measured, from where, and what was left outHow to read a service report's availability percentage: what counts as downtime, where it is measured, how intervals work and what is excluded.Read article
- Hosting.NET on Windows Server: what Windows Update patches and what it leaves to youWhy a fully patched Windows server can still run an out-of-support .NET runtime: the difference between .NET Framework and modern .NET, how each is updated on Windows Server, what self-contained applications mean for patching, and why .NET 8 and 9 support ended on 10 November 2026.Read article
- HostingPatching hosted Windows applications: monthly updates, hotpatch and maintenance windowsHow often a Windows server running business software has to restart for updates, when Microsoft's monthly release lands in Australian time, what hotpatching on Windows Server 2025 really removes, and how to agree a maintenance window the business can live with.Read article
Risks and limits
- This article describes WSUS terminology. Patch tools differ, and we did not review Microsoft's other reporting products or third-party tools.
- The console and the programming reference do not name statuses identically. Our claim that the console files pending-restart servers under Needed is our reading of Microsoft's wording.
- The Microsoft terminology page we cited shows an older update date and was fetched at a German-locale address; wording may have changed in newer pages.
- Commands were not tested. They are read-only by their documentation, but confirm against your environment.
- A patch report shows what was applied, not whether the application still works after the update.
Next step
Take your latest compliance report and list every server that is pending restart, failed or silent, with the date it last reported. Flag any server pending restart for longer than one cycle and ask your provider for the cause in writing. If you are reviewing a hosted service, the Managed Services page is a starting point for that conversation; ask for the scope in writing.
Sources
- Terminology for Update Status, Microsoft Learn; displayed date 2021-11-22 (English content at the German-locale address).
- UpdateInstallationState, Microsoft Learn; displayed date 2009-08-07.
- Updates Operations, Microsoft Learn; last updated 2023-07-12.
- Get-WsusComputer, Microsoft Learn; date unavailable.
- Get-HotFix, Microsoft Learn; date unavailable.
All accessed 15 November 2026.
Learning notes
- 'Compliant' is a result, not a fact; ask what it counts.
- Installed and not applicable share a column, so a high number is not the same as many patched servers.
- Pending restart means installed but not yet in effect.
- No status means no report, and tells you nothing about the server.
- Always ask when each server last reported.
This article was originally published on .