Help Docs

Performance Metrics for Windows Updates Monitoring

Site24x7 Windows Updates monitor:

  • Gives you a single place to see Windows update health for each monitored host.
  • Summarizes availability and downtime, highlights pending updates, and shows a complete installation history with results.
  • Lets you search, filter and share update lists and link out to Microsoft KB articles for deeper details.

Who should use this

  • IT admins and help desk staff who patch Windows endpoints and servers.
  • Security and compliance teams who need proof of update's status.

How to navigate to Windows Update monitor

  1. Log in to Site24x7.
  2. Click Server on the left-navigation pane and then click Windows Update.

Monitored data

In the Windows Update monitor home page, you have multiple tabs:

  • Summary: High‑level health and what's pending right now.
  • Update History: Every update attempt with status, codes and categories.
  • Outages: Uptime and downtime information for the monitored device.
  • Notes: Add or view technician notes for the device.
  • Log Report: Collected logs relevant to updates and availability.
  • Alert Logs: Alerts raised by the system (failures, critical conditions, etc.)

Total Pending Updates: A focused list of updates still awaiting installation, including restart requirements.

Summary

What you see in this tab:

  • Availability: Uptime (%) for the selected period.
  • Downtimes: Count of downtime incidents in the period.
  • Total Pending Updates: Number of updates not yet installed.
  • Pending Critical Updates: Number of updates marked as critical and not yet installed.
  • Pending Security Updates: Number of updates marked as security-related and not yet installed.
  • Events Timeline: A time‑strip that marks periods as Down, Critical, Trouble, Maintenance, or Suspended.

Currently Pending Updates

Shows the concise breakdown of each type of Windows update:

  • Total Pending Updates: Overall count of all updates waiting to be installed.
  • Pending Critical Updates: High-priority fixes that address major system stability or functionality issues. These are essential for keeping Windows running properly.
  • Pending Definition Updates: Updates for Windows Defender or other security tools that refresh malware/virus definitions to detect the latest threats.
  • Pending Drivers Updates: Updates for hardware drivers (graphics, network, audio, etc.) to improve compatibility, performance, or fix bugs.
  • Pending Feature Pack Updates: Add-ons or enhancements that introduce new features or expand existing functionality in Windows.
  • Pending Security Updates: Patches that fix vulnerabilities in Windows or Microsoft software to protect against exploits and attacks.
  • Pending Service Packs Updates: Large cumulative packages that bundle previous updates and might include new features or performance improvements.
  • Pending Tools Updates: Updates for built-in Windows tools or utilities, ensuring they remain functional and secure.
  • Pending Update Rollups: Collections of multiple updates bundled together for easier deployment, often targeting specific components.
  • Pending Updates: General updates that don't fall into the above categories like bug fixes, performance tweaks, or minor improvements.
  • Pending Upgrades: Major version changes, such as moving from Windows 10 to Windows 11, or significant OS build upgrades.
  • Pending Application Updates: Updates for installed Microsoft or third-party applications (for example, Office, Edge, or other apps) to improve features, fix bugs, or patch security issues.
Tip

Click the open‑in‑new-tab icon (where available) to jump to the detailed list.

Server Details panel

  • Host Name: The unique name assigned to the host on a network.
  • IP Address: The numerical label (IPv4 or IPv6) that identifies the device on a network.
  • Operating System: The version of Windows (or other OS) installed on the machine.
  • OS Architecture: Indicates whether the system is 32-bit or 64-bit.
  • Number of CPU Cores (Logical): The count of available logical processor cores.
  • Installed Memory (MB): The total physical RAM installed, measured in megabytes.
  • Processor: The CPU model and details (for example, Intel Core i7, AMD Ryzen.)
  • Windows Update Service: Status of the Windows Update service (running, stopped, etc.)
  • Last Successful Update Time: The timestamp of the most recent update that was installed successfully.
  • Last Updated Time: The last time the system attempted an update (successful or not.)
  • Failed Updates: The number of updates that failed to install.

Updates Summary table

A quick list of the actual pending items with columns such as:

  • Name: The update title.
  • KB: Microsoft knowledge base identifier. Use the KB link to open Microsoft's article.
  • Category: How the update is classified (for example, Pending Definition Updates.)
  • KB Link: External link for release notes and prerequisites.

Use the search box to find an update by title or KB number.

Update History

This tab shows an auditable list of every installation attempt and its outcome.

Data shown in this tab:

  • Date: When the attempt was recorded.
  • Name: Update package title.
  • Status:
    • Succeeded: Installed as expected.
    • In Progress: Still installing; check again after a reboot or next scan.
    • Failed: Installation attempt did not complete.
  • HResult: Windows Update/Installer return code (see "Common codes" below.)
  • KB: KB identifier when applicable.
  • Operation(s): Installation, Uninstallation, or other actions.
  • Category: The Microsoft update channel/category (for example, "Windows 10, version 1903 and later".)

Available tools on this page:

  • Search filter: Find entries by KB or any word in the title.
  • Last Discovered Time: Timestamp of the most recent data sync from the device. Use it to confirm you are looking at fresh data.

Common HResult codes you'll see:

  • 0x0: Success.
  • 0x80070643: Windows Installer error. Often caused by a .NET or MSI problem, permissions, or a stuck Windows Update component.
  • 0x80242014: Update requires a post‑reboot step or the state after reboot is unexpected. A reboot or re‑scan usually resolves it.

How to configure alerts in Windows Update monitor

To configure alerts when any of the updates breach your desired threshold, configure a Threshold Profile.

Here are two ways to configure a Threshold Profile:

Click the hamburger icon next to the Windows Update monitor name and then click Edit.

Alternatively, you can navigate to Admin > Configuration Profiles > Threshold and Availability > Threshold Profile.

  1. In the pop-up window, select Windows Update in the Monitor Type drop-down.
  2. Provide an appropriate display name for the Threshold Profile (for example, JDoe-Q12026-UpdateMon.)
  3. Assign thresholds to these metrics as required:
  • Pending Critical Updates: Count of uninstalled OS updates classified by Microsoft as Critical.
  • Pending Definition Updates: Unapplied antivirus/antimalware signature updates (for example, Defender intelligence.)
  • Pending Drivers Updates: Hardware driver packages available via Windows Update/WSUS that aren't installed.
  • Pending Feature Pack Updates: Optional feature/enablement packages and capabilities awaiting install.
  • Pending Security Updates: Unapplied security fixes that address vulnerabilities.
  • Pending Service Packs Updates: Service‑pack style bundles still pending (mainly for legacy/LTSB builds.)
  • Pending Tools Updates: Microsoft tools/utilities delivered through WU (for example, Malicious Software Removal Tool) pending.
  • Pending Update Rollups: Cumulative/quality rollup packages not yet installed.
  • Pending Updates: Total number of all pending updates across categories.
  • Pending Upgrades: Major OS version upgrades available but not applied (for example, 21H2 to 22H2, Windows 10 to 11.)
  • Pending Application Updates: Updates for Microsoft applications delivered via Windows Update that are awaiting install.
  • Time Since Last Update Installed: Elapsed time since the device last completed a successful update installation.

How to investigate a failed update

To investigate a failed update:

  • Click the KB link to read Microsoft's article for known issues and prerequisites.
  • Check if a reboot is pending; reboot the device if allowed.
  • Verify if the Windows Update service is running and the device has internet/WSUS access.
  • Ensure there is enough free disk space on the system drive.
  • Retry the update from Windows Update on the device or your patching tool.

Total Pending Updates

Click Total Pending Updates on the Summary tab to view this tab dedicated to list all pending updates. This is a concise list of items still outstanding including a the display of the most actionable fields. This tab shows you:

  • Name and KB: The exact update you need to install the update.
  • Product: Name of the package the update applies to.
  • Server Restart Requirement: Shows if host reboot is required to complete the update.

From this tab, you can choose to:

  • Search by Update Name or KB to quickly isolate a specific package.
  • Share This button: Generate a shareable view or export (depending on your plan) to send to stakeholders.

Windows Update monitor best practices

To use Site24x7's Windows Updates monitor effectively, we recommend these best practices:

  • Open Summary and verify Availability is healthy and Downtimes is 0.
  • Review Total Pending Updates; note security or critical updates first.
  • Click KB links to review high‑priority items and to schedule their automated installation if needed.
  • Check Alert Logs for new failures.

FAQs

Q: The monitor is empty. What should I do?

A: Ensure the monitoring agent is installed and the device is reachable. Verify required services (WMI, Windows Update) are enabled.

Q: Can I install updates from this screen?

A: This module focuses only on visibility and auditing. Installation occurs via your patching workflow (Windows Update/WSUS or your RMM/patch tool.) Use the KB links and pending lists to plan and verify.

Q: There is a mismatch between the updates shown in the server and the ones shown in Site24x7. Why does this happen?

A: This is likely due to your custom organizational policy. We provide guidance here for working with Microsoft's methods for filtering updates to display in your system's "Check for Updates" dashboard.

Was this document helpful?

Would you like to help us improve our documents? Tell us what you think we could do better.


We're sorry to hear that you're not satisfied with the document. We'd love to learn what we could do to improve the experience.


Thanks for taking the time to share your feedback. We'll use your feedback to improve our online help resources.

Shortlink has been copied!