Last Tuesday, your Windows PC was humming along. Today, it’s crashing, slow, or refusing to print. Before you reinstall Windows or haul it to a repair shop, there’s a single, built-in page that can tell you exactly what changed: Windows Update History. It’s a chronological log of every patch, driver, and definition update that Microsoft pushed to your machine, and it’s the fastest way to connect a sudden problem to a recent change.

Millions of users tap the “Check for updates” button without ever exploring the “Update history” link right next to it. That’s a missed opportunity. The history page doesn’t just satisfy curiosity—it’s a diagnostic instrument. It shows installation dates, links updates to their Knowledge Base (KB) identifiers, and, when needed, provides a direct route to uninstall a troublesome update. Use it wisely, and you can stop a reboot loop, fix a compatibility glitch, or at least gather the facts before calling IT support.

What the update history actually records (and what it doesn’t)

Windows Update History is a local ledger, not a complete system changelog. It records every update delivered through Windows Update: monthly cumulative quality fixes, driver updates from Microsoft’s servers, Security Intelligence updates for Windows Defender, and the big feature updates that bump your OS to a new version. Each entry includes a KB number—a unique identifier that Microsoft uses across its documentation—and the date the update was applied.

Crucially, the history page is not a universal inventory. It won’t show you every app you installed, every Microsoft Store refresh, or third-party driver packages from your hardware vendor. It also won’t reflect updates deployed by enterprise management tools like Intune or Configuration Manager. For a home or small-business PC, however, it’s the most honest snapshot you’ll get of what Windows changed underneath the hood.

Its value lies in simplicity. A quick glance answers three essential troubleshooting questions:
- What installed recently? (check the dates)
- Was it a major change (quality update, driver, or feature update)?
- Can I look up the KB number to read known issues? (yes, via Microsoft’s release health dashboard or support articles)

Knowing these details transforms a vague “something broke after an update” into a specific, investigable event.

A tale of two Settings paths: Windows 11 vs. Windows 10

Microsoft relocated the Windows Update section in Windows 11, so the navigation differs between the two operating systems. The good news: a single Run command works on both, bypassing the click-through entirely.

Windows 11
Settings → Windows Update → Update history

Windows 10
Settings → Update & Security → Windows Update → View update history

The terminology shift trips up support guides. If you’re helping someone on a Windows 10 PC, don’t say “go to Windows Update” without specifying “Update & Security” first. For the fastest access, press Windows key + R, type ms-settings:windowsupdate-history, and hit Enter. This URI opens the update history page directly and is especially handy for remote troubleshooting instructions. Microsoft documents this scheme as part of its Settings URI reference.

One more thing: although free support for Windows 10 ended in October 2025, devices still running the OS—particularly those under extended servicing agreements—retain this same history interface. Navigating it on a Windows 10 machine remains just as relevant for checking the last security patch or documenting a problem before contacting IT.

Decoding the update categories: From quality fixes to drivers

Once you open the history page, resist the urge to scan only the first list you see. Windows 11 groups updates into collapsible categories: Quality Updates, Driver Updates, Definition Updates, Other Updates, and Feature Updates. A security cumulative fix might live under Quality Updates, while a Wi-Fi driver that tanked your connectivity could be tucked inside Driver Updates. Expand every section before drawing conclusions.

Each entry provides three vital clues:
- KB number (e.g., KB5035853). This is your lookup key for Microsoft’s release notes, which detail security fixes, known issues, and mitigations.
- Installation date. Match it against the moment the trouble began.
- Classification. A quality update (monthly security patch) behaves differently than a driver update or a full feature update. If the problem started after a feature update, you may need a system rollback rather than a simple uninstall.

Feature updates—the big annual upgrades that change your Windows version—are labeled separately. Their KB numbers often link to “What’s new” pages rather than patch notes. A quality update within the same version can usually be removed with minimal collateral damage; reverting a feature update is a heavier lift (more on that later).

When to uninstall an update — and when to pause

The “Uninstall updates” link at the top of the history page can feel like a tempting “fix everything” button. Microsoft, however, explicitly recommends uninstalling only when a specific update causes verifiable problems. Here’s the uncomfortable truth: removing a cumulative quality update also removes all the security patches bundled inside it. Your PC becomes vulnerable until the next update cycle.

Before pulling the trigger, do a sanity check:
1. Confirm the timeline. Did the symptom appear right after the update’s install date?
2. Look up the KB number on the Windows release health page. Is there a documented known issue that matches your symptoms?
3. Check for simpler fixes first. A driver rollback in Device Manager might solve a display glitch without touching Windows system files.
4. Consider a repair install instead. Windows 11’s “Fix problems using Windows Update” option (Settings → System → Recovery) reinstalls the same OS version while preserving apps and files—a less drastic step than patch removal.

If you do decide to uninstall, the path is:
- On Windows 11: Settings → Windows Update → Update history → Uninstall updates.
- On Windows 10: Settings → Update & Security → Windows Update → View update history → Uninstall updates.
Select the problematic KB and click Uninstall. Some updates—particularly servicing stack updates and certain cumulative bundles—cannot be removed.

If Windows won’t start: Enter the Recovery Environment

A no-boot situation after an update denies you the luxury of poking around in Settings. That’s where the Windows Recovery Environment (WinRE) takes over. From the automatic repair screen (or a bootable USB drive), navigate to Troubleshoot → Advanced options → Uninstall Updates. You’ll see two choices: “Uninstall latest quality update” and “Uninstall latest feature update.”

WinRE doesn’t display a full history; it targets only the most recent applicable patch. This is enough to restore bootability in the majority of cases. If the system remains unbootable, you may need to use System Restore or a full recovery—but starting with the latest update removal is the least destructive move.

Separate from WinRE is the “Go back” option for feature updates. If you’ve upgraded to a new Windows version within the last 10 days (the default rollback window), and the previous installation files weren’t deleted, you can go to Settings → System → Recovery → Go back. This returns you to the prior Windows version, but it removes apps and drivers installed after the upgrade. It’s a broader reset than removing a monthly patch, so use it only when the feature update itself is the clear culprit.

Beyond the Settings app: PowerShell, CIM, and when to skip WMIC

The Settings history page is the most user-friendly view, but power users and help desk technicians often need command-line tools for scripting or remote audits. The two most common are Get-HotFix in PowerShell and its underlying CIM query Get-CimInstance -ClassName Win32_QuickFixEngineering. Both list installed hotfixes—but with a critical disclaimer: they report only updates delivered through Component Based Servicing (CBS). This means they won’t include every MSI-installed update, some driver packages, or updates that arrived outside the CBS pipeline. Consequently, the output can differ from what you see in Settings.

For a broader inventory, Dism /Online /Get-Packages in an elevated Command Prompt enumerates servicing packages, while systeminfo provides a compact hotfix list. These are supplementary, not replacements. Reserve them for situations where you need to script a scan across dozens of machines or capture a quick snapshot for a support ticket.

One tool to retire from your workflow immediately: WMIC. Microsoft deprecated the Windows Management Instrumentation Command-line utility years ago, and Windows 11 version 25H2 removes it during a feature update. Scripts that rely on wmic qfe will break on newer systems. Always use Get-HotFix or CIM cmdlets instead.

For managed or Surface devices, the rules adjust slightly. On a work PC, the local update history may not reflect deployment rings or deadlines set by your admin. Surface owners should check the Surface app’s Help & support section for firmware status; Microsoft warns that Surface firmware updates cannot be uninstalled or reverted. That means an entry in update history that points to a firmware change needs special attention—don’t assume you can roll it back like a driver.

A five-step workflow for post-update detective work

Rather than flailing between tools, adopt a disciplined sequence. Here’s a repeatable process that works on any Windows 11 or Windows 10 PC:

Step 1: Open update history the fast way
Press Win+R, type ms-settings:windowsupdate-history, press Enter. Expand every category so you don’t miss a driver or definition update.

Step 2: Identify the most recent entry that aligns with the problem start
Note its KB number, type (quality, driver, feature), and installation date.

Step 3: Check Microsoft’s release health documentation
Search for the KB number in your browser. Microsoft’s Windows release health pages list known issues, mitigations, and whether the update is part of a larger servicing change. This step alone often reveals that the issue is acknowledged and a fix is incoming.

Step 4: Before uninstalling, try a softer approach
- If it’s a driver issue, roll back the driver in Device Manager.
- If you suspect system file corruption, run DISM /Online /Cleanup-Image /RestoreHealth and then SFC /scannow.
- For Windows 11, consider the “Fix problems using Windows Update” repair reinstall.

Step 5: Uninstall only when necessary
Use the Update history → Uninstall updates path. If Windows won’t boot, use the Recovery Environment. Document the KB you removed—it will likely reappear in the next update cycle unless you temporarily pause updates (Settings → Windows Update → Pause updates) while you investigate the root cause.

Outlook: The bedrock of Windows servicing transparency

Microsoft continues to shift update controls toward the modern Settings app, but the update history page has remained conceptually unchanged for years. That’s a feature, not a bug. In an era of increasingly automated servicing and cloud-driven quality updates, the ability to see a local, timestamped list of changes is more crucial than ever.

As Windows 10 fades from mainstream support and Windows 11’s servicing model evolves, the tools around update history will likely grow more intelligent—perhaps offering one-click rollback suggestions or deeper integration with the Windows release health dashboard. For now, though, the page is exactly what it should be: a straightforward, no-blame record of what landed on your PC, ready for you to read and act upon. Next time your machine misbehaves after Patch Tuesday, don’t guess. Make “Update history” your first stop.