If you need to confirm whether a security patch installed correctly, Windows gives you several ways to review update history.
This guide shows how to check Windows security update history on Windows 10 and Windows 11, and how to interpret what you see.
What Windows update history actually shows
Windows Update history is a record of installed updates, failed updates, driver updates, definition updates, and cumulative quality patches.
It is useful for verifying Patch Tuesday installs, checking whether a security fix reached a device, and spotting patterns when updates repeatedly fail.
It is important to know that update history is not the same as the full installed patch inventory.
Some security updates appear as cumulative updates, servicing stack updates, or Microsoft Defender definition updates rather than as separate security bulletins.
How to check Windows security update history in Settings
The quickest method is inside the Windows Settings app.
This works on modern Windows 10 and Windows 11 systems.
- Open Settings.
- Select Windows Update.
- Choose Update history.
You will see categories such as quality updates, driver updates, definition updates, and other updates.
Security fixes are often part of quality updates or cumulative updates, so check the installed date and KB number carefully.
What to look for in the list
- KB number: The Microsoft knowledge base identifier for the update.
- Installed on: The date the update was applied.
- Status: Whether the update installed successfully or failed.
- Update name: Often includes cumulative update wording rather than a direct security label.
If you are verifying a specific vulnerability fix, compare the KB number against Microsoft’s security update guidance or the monthly security release notes.
How to check installed security updates from Control Panel
For a more traditional view, use Control Panel to see installed updates.
This can help when you need a broader list of Windows packages already present on the device.
- Open Control Panel.
- Go to Programs and then Programs and Features.
- Select View installed updates.
This screen shows Microsoft updates installed on the system, including Windows security-related patches.
You can sort by name or installed date and search for a KB number directly.
Because Windows often bundles security fixes into cumulative updates, the same patch may not appear as a standalone “security update.” Instead, you may see the cumulative package that contains the fix.
How to use Command Prompt or PowerShell for update history?
If you prefer a command-line method, Windows can list installed hotfixes and update records.
This is especially useful for IT teams, remote support, and audit checks.
Command Prompt
Open Command Prompt and run:
wmic qfe list brief /format:table
This displays installed hotfixes with their KB numbers and installed dates.
Although WMIC is considered legacy on newer systems, it still appears in many environments.
PowerShell
Open PowerShell and run:
Get-HotFix
This command returns a list of installed updates, including the description, hotfix ID, installed by, and installed date.
For more detailed reporting, administrators often use Windows Update logs, Microsoft Endpoint Configuration Manager, or Intune reporting instead.
How to find update details for a specific KB number
Once you have a KB number, the next step is to identify what it contains.
Search the KB number on Microsoft Support or in the Microsoft Update Catalog to see whether it includes security fixes, cumulative changes, or servicing stack updates.
This step matters because the same update can address multiple vulnerabilities.
A cumulative update may contain fixes for Microsoft Edge, Windows kernel components, Hyper-V, or other subsystems depending on the release cycle.
How to tell whether a security update failed
Update history also shows failures, but the reason may not be obvious.
If a security update did not install, Windows may show an error code in the history list or in the Windows Update page.
- Download or installation errors: The update never completed.
- Pending restart: The patch may be staged but not fully applied.
- Rollback after reboot: The update started but was removed because of a system issue.
If a security update fails repeatedly, check disk space, system file integrity, network access to Microsoft servers, and third-party security tools that may block the installation.
How to verify security patches on managed devices
In business environments, update history on one machine is often not enough.
Administrators usually verify compliance with centralized tools such as Microsoft Intune, Windows Server Update Services (WSUS), Microsoft Configuration Manager, or endpoint protection dashboards.
These platforms can show deployment status across multiple devices, missing updates, and failure trends.
They are especially useful when confirming whether a security baseline has been applied across a fleet of laptops, desktops, and servers.
What about Microsoft Defender updates?
Microsoft Defender Antivirus also receives frequent security intelligence updates.
These are usually listed separately in update history as definition updates or similar entries.
If your goal is malware protection status rather than operating system patching, review the Defender version and definition age in Windows Security.
That gives a more accurate picture of antivirus update freshness than the standard Windows Update list alone.
Common reasons update history looks incomplete
Sometimes users think Windows is missing a patch, when the issue is actually how the update is recorded.
Common reasons include the following:
- Cumulative updates combine many fixes into one package.
- Feature updates may reset or reorganize some update records.
- Servicing stack updates can appear separately from security patches.
- Device reimaging or reset may clear older local history.
- Enterprise management tools may apply updates before the local history is refreshed.
When history looks incomplete, cross-check with the installed KB list, system build number, and Microsoft’s release notes for the month in question.
Best practices for checking Windows security update history
- Look for the KB number, not just the update title.
- Confirm the install date against the security release cycle.
- Check both Windows Update history and installed updates if you need certainty.
- Use PowerShell or management tools for bulk verification.
- Review Microsoft security advisories when validating a specific vulnerability fix.
For most users, the Settings app is the fastest way to check Windows security update history.
For admins and troubleshooting, PowerShell, Control Panel, and endpoint management tools provide the detail needed to verify patch compliance with confidence.