To check your Windows update history in Windows 11, open Settings > Windows Update > Update history, which lists what installed, when it installed, and, for failed updates, usually an error code. If that list looks incomplete or you need more detail, PowerShell and Event Viewer hold deeper records, and all three tools are already built into Windows 11.
What Each Tool Shows (and What a KB Number Is)
Windows 11 doesn’t keep update history in one place. These four tools each show a different slice of it, and the export section later adds Get-WindowsUpdateLog for a full technical trace:
| Tool | Best for | Limits |
|---|---|---|
| Settings > Update history | Quick, plain-language list by category, with dates and failure codes | Can look empty or incomplete after a feature upgrade or reset |
PowerShell Get-HotFix | Fast table of installed hotfixes with KB numbers and dates | Lists only updates installed through Component Based Servicing (CBS), so it misses MSI-installed updates, drivers, and Defender definitions |
PowerShell Get-WinEvent | Searching the detailed update log from the command line | Output is wordy and needs filtering |
| Event Viewer (WindowsUpdateClient > Operational) | A detailed, timestamped record of update activity | Busier interface, more technical messages |
You’ll see the term KB number in every one of these tools. “KB” stands for Knowledge Base. Microsoft gives each update an ID like “KB” followed by a number, and it publishes a support article under that same number explaining what the update changes. The KB number is how you look up an update, confirm it installed, report it to support, or uninstall it.
Before You Begin
- A PC running Windows 11 (Home, Pro, Enterprise, Education, or another supported edition)
- An administrator account. It isn’t strictly needed for Settings, but it is recommended for running PowerShell as administrator
- Nothing to download. Settings, PowerShell, and Event Viewer ship with Windows 11
| Requirement | Details |
|---|---|
| Device | Any Windows 11 PC |
| OS version | Windows 11, any supported version |
| Permissions | Administrator recommended for PowerShell |
| Cost | Free, all tools are built in |
Step-by-Step Guide
Step 1: Open Update History in Settings
- Press
Win + Ito open Settings. - Select Windows Update in the left sidebar.
- Select Update history.
Expected result: A page opens with collapsible categories, such as Feature updates, Quality updates, Driver updates, Definition updates, and Other updates.
Step 2: Read the Categories and Spot Failed Updates
- Expand Quality updates. This category holds the monthly cumulative and security updates, which are the ones most likely to cause or fix problems.
- Read each entry. Each one shows the update name, the KB number in parentheses, and a status line such as “Successfully installed on” followed by a date.
- Look for any entry that says Failed to install on followed by a date. An error code is typically shown alongside it.
- Write down the KB number and the full error code exactly as shown. Don’t round or shorten it, because the exact code is what you’ll search for and what support will ask for.
- Expand Driver updates and Definition updates if you’re chasing a hardware problem or a Microsoft Defender issue. These update types don’t show up in
Get-HotFixlater, so Settings and Event Viewer are where you’ll find them.
Expected result: You know which updates installed, when they installed, and whether any failed and with which error code.
Tip: The Uninstall updates link sits further down this same page under Related settings. Don’t use it yet. Finish identifying the problem update first.
Step 3: Confirm Your Windows Version and Build
Microsoft publishes separate update lists for each Windows 11 release, such as 24H2 and 25H2. Check which one you’re on before comparing KB numbers.
- Open Settings > System > About.
- Scroll to Windows specifications.
- Note the Version (for example, 24H2 or 25H2) and the OS build number.
Expected result: You have the version and build to match against Microsoft’s Windows 11 release information page or the update-history page for your version (24H2, 25H2). The last number in your OS build often corresponds to a specific cumulative update, but it doesn’t identify that update on its own; confirm the match by comparing your build number against Microsoft’s release-history page for your version.
Warning: As of Microsoft’s release-health information retrieved in October 2026, Windows 11 version 24H2 Home and Pro editions reached their end of updates on October 13, 2026. If About shows 24H2 on a Home or Pro PC, check the release information page for current dates. Missing new updates may simply mean the version is out of support.
Step 4: List Installed Updates With Get-HotFix
- Right-click the Start button and select Terminal (Admin).
- Click Yes on the User Account Control prompt.
- Make sure the tab is a PowerShell tab. It is the default in most setups.
- Run this command:
Get-HotFix | Sort-Object InstalledOn -DescendingExpected result: A table appears with the newest entries at the top. The HotFixID column holds the KB numbers, Description labels the entry (such as “Update” or “Security Update”), and InstalledOn shows the date.
What Get-HotFix misses: This cmdlet reads the Win32_QuickFixEngineering WMI class, which Microsoft documents as returning only updates supplied by Component Based Servicing (CBS). Updates supplied by Microsoft Installer (MSI) or the Windows Update site aren’t returned, so it also won’t show driver updates or Microsoft Defender definition updates. Some entries may also have a blank InstalledOn date. If an update you expect is missing here, don’t assume it isn’t installed. Check Settings or Event Viewer before you decide.
Step 5: Check Whether a Specific KB Is Installed
Use this step when an article or support agent says “install KB such-and-such” and you want to confirm it’s on the PC.
- In the same PowerShell window, run the command below. Replace
KBXXXXXXXwith the real KB number from Settings or Microsoft’s update-history page:
Get-HotFix -Id KBXXXXXXX- Read the result.
Expected result: If the update is listed, you’ll see one row with its install date. If it isn’t found, PowerShell returns an error saying it cannot find the hotfix. Because of the limits in Step 4, that error means “not in Get-HotFix’s list.” It doesn’t always mean “not installed,” so cross-check with Settings before reinstalling anything.
Step 6: Search the Full Update Log With Get-WinEvent
The WindowsUpdateClient operational log records detection, download, installation, and failure events, including attempts that never appeared in Settings.
- In the admin PowerShell window, show the 50 most recent Windows Update events:
Get-WinEvent -LogName "Microsoft-Windows-WindowsUpdateClient/Operational" -MaxEvents 50- To show only events that mention a failure, run:
Get-WinEvent -LogName "Microsoft-Windows-WindowsUpdateClient/Operational" | Where-Object { $_.Message -like "*fail*" } | Format-List TimeCreated, Message- To show every event mentioning a specific update, replace
KBXXXXXXXand run:
Get-WinEvent -LogName "Microsoft-Windows-WindowsUpdateClient/Operational" | Where-Object { $_.Message -like "*KBXXXXXXX*" } | Format-List TimeCreated, MessageExpected result: Timestamped messages describing what Windows Update did. Failure messages usually include the update’s name and often an error code, so you can line them up with the failed entry from Step 2.
Step 7: Open the WindowsUpdateClient Log in Event Viewer
If you prefer clicking to typing, Event Viewer shows the same log in a graphical window.
- Press
Win + R, typeeventvwr.msc, and pressEnter. - In the left pane, expand Applications and Services Logs.
- Expand Microsoft > Windows > WindowsUpdateClient.
- Select Operational.
Expected result: The center pane fills with Windows Update events, newest first. Clicking any event shows its full message on the General tab below the list.
Step 8: Find a KB or Failure in Event Viewer
- With Operational selected, click Find in the right-hand Actions pane.
- Type the KB number, for example
KBXXXXXXX, or a word likefailed. - Click Find Next and read the highlighted event’s General tab.
- Repeat Find Next to move through the other matches.
- For a cleaner list, click Filter Current Log in the Actions pane and set Logged to a time range around when the problem started.
Expected result: You can see exactly when Windows started, finished, or failed each install. This is the timeline to share with whoever is helping you troubleshoot.
Export and Share Your Update History
Export the hotfix list for a support ticket. This command saves a CSV file to your desktop that you can attach to an email:
Get-HotFix | Sort-Object InstalledOn -Descending | Export-Csv "$env:USERPROFILE\Desktop\hotfixes.csv" -NoTypeInformationGenerate a readable WindowsUpdate.log. Windows 11 stores its detailed Windows Update trace as .etl files rather than a plain text log. In an admin PowerShell window, run:
Get-WindowsUpdateLogThis merges and converts those trace files into a single WindowsUpdate.log file, saved to your desktop by default. It’s more technical than Event Viewer, but it’s what support staff often ask for. See Microsoft’s Get-WindowsUpdateLog reference for options.
Save the Event Viewer log. With Operational selected, click Save All Events As in the Actions pane to export an .evtx file that another technician can open in their own Event Viewer.
Get updates sooner. In Settings > Windows Update, you’ll find a Get the latest updates as soon as they’re available toggle. Turning it on can make update rollouts, including feature updates, available to the PC sooner. Check its current state before changing it, and leave it as-is on a PC you can’t afford to troubleshoot.
Check known issues before blaming the PC. Microsoft’s release-health pages list confirmed problems for each version, for example 24H2 known issues and 25H2 known issues. If your KB number appears there, the fix may be on Microsoft’s side.
What to Do Once You Have the KB Number
- The update broke something: Search the KB number on Microsoft’s update-history page for your version to read what it changed, then follow Microsoft’s steps for how to uninstall a Windows update by KB number. Back up important files to an external hard drive first.
- The update keeps failing or hangs: Note the exact error code and match it to the surrounding events in Event Viewer (Step 8) before you start troubleshooting.
- You need breathing room: After uninstalling a bad update, use Pause updates in Settings > Windows Update so it doesn’t reinstall before Microsoft ships a fix.
Tips and Troubleshooting
Update history in Settings is empty or missing entries
Why it happens: The list can reset after a feature upgrade or a reset of Windows Update’s local history, and some update types may not be recorded there.
Fix: Run Get-HotFix | Sort-Object InstalledOn -Descending (Step 4), then check Event Viewer’s WindowsUpdateClient > Operational log (Step 7) for installation events that Settings doesn’t show.
A KB from Microsoft’s website isn’t on this PC
Why it happens: Microsoft’s pages cover several versions and builds, and a KB may apply to a different release line than the one you’re running.
Fix: Compare Settings > System > About (Step 3) against the correct 24H2, 25H2, or 26H2 page before assuming the update is missing.
Get-HotFix returns nothing or looks incomplete
Why it happens: It only lists CBS-supplied updates, not MSI-installed updates, drivers, or Defender definitions.
Fix: Confirm you’re in an admin PowerShell window and the syntax is exact, then use Get-WinEvent (Step 6) or Event Viewer for the fuller history.
Windows Update reports a failure
Why it happens: Failed attempts usually log an error code that points toward the cause, although some codes are generic.
Fix: Take the code from Update history (Step 2), then find the same timestamp in Event Viewer (Step 8) for the surrounding events.
A feature update isn’t being offered yet
Why it happens: Feature updates roll out in phases to eligible devices.
Fix: In Settings > Windows Update, turn on Get the latest updates as soon as they’re available and select Check for updates. If the PC is eligible, a Download & install option appears.
Wrapping Up
Settings > Update history answers “did it install, and did it fail?” for most people in under a minute, and it’s where I’d always start. Use Event Viewer when Settings looks incomplete, because it often records attempts Settings doesn’t show.
Get-HotFix is handy for a quick KB check, but it doesn’t show every update type, so a missing entry there doesn’t prove an update is missing. If installs keep failing with different error codes across several months, look beyond Windows Update. Run a malware scan and check your drive’s health, because a failing disk often shows up this way first.
| Step | Action | Applies To |
|---|---|---|
| 1–2 | Check Settings > Windows Update > Update history | Everyone, first stop |
| 3 | Confirm version and build in System > About | Matching KBs to Microsoft’s pages |
| 4–5 | Get-HotFix list and KB check | Quick technical cross-check |
| 6 | Get-WinEvent filtered search | Command-line deep dive |
| 7–8 | Event Viewer WindowsUpdateClient > Operational | Detailed, timestamped record |