What you will achieve

See every quality and feature update Windows has installed, note KB numbers and dates, and correlate a new problem with a specific patch before you uninstall anything.

1) Open update history in Settings

Open Settings → Windows Update.
Click Update history (Windows 10: Settings → Update & Security → Windows Update → View update history).
Browse categories: Feature updates, Quality updates, Driver updates, and Definition updates.

Each entry shows a KB number (for example KB5036893) and install date. Write down the KB if troubleshooting started after a recent Tuesday patch.

2) Match KB numbers to Microsoft documentation

Search the KB on support.microsoft.com to read release notes, known issues, and whether a fix is pending. This saves you from uninstalling the wrong update.

3) View history from Command Prompt or PowerShell

For a text list useful in support tickets, open Admin PowerShell:

Get-HotFix | Sort-Object InstalledOn -Descending | Format-Table HotFixID, Description, InstalledOn -AutoSize

Cross-check suspicious dates against when symptoms began.

4) Use Event Viewer for failed installs

Press Win + X → Event Viewer.
Navigate to Applications and Services Logs → Microsoft → Windows → WindowsUpdateClient → Operational.
Filter Event ID 19 (successful install) and 20 (failed install) around the problem date.

5) Before uninstalling an update

Confirm the KB appears in history on the date problems started.
Check Microsoft’s known-issues list — a newer patch may already fix it.
Only then use Settings → Windows Update → Update history → Uninstall updates or follow our dedicated rollback guide.

6) Export history for IT documentation

When handing a PC to support, capture a snapshot:

Get-HotFix | Sort-Object InstalledOn -Descending | Out-File "$env:USERPROFILE\Desktop\update-history.txt"

Attach the text file to tickets alongside Event Viewer exports. Include Windows version from Settings → System → About — feature update build numbers explain behaviour changes that quality KBs alone do not capture. Driver updates listed separately often correlate with new hardware faults rather than Patch Tuesday issues. Keep the export dated so support can match it to logs.