What you will achieve

Tell feature updates apart from quality (security) updates, know what each changes, and plan reboots and testing accordingly.

1) Quality updates (monthly)

Released on Patch Tuesday (second Tuesday of each month) as cumulative updates.
Include security fixes, bug fixes, and sometimes driver updates — they do not change the Windows version number majorly.
View history: Settings → Windows Update → Update history. Look for entries labelled Update Stack or Security Update.

2) Feature updates (annual or semi-annual)

Move Windows to a new version (e.g. 22H2 → 23H2 → 24H2). The version changes under Settings → System → About.
Larger download, longer install, more reboots, and higher risk of app or driver incompatibility.
On Pro, defer via Group Policy: Select when Preview Builds and Feature Updates are received.

3) Identify what is pending

Settings → Windows Update shows a feature update as a distinct large download with a version name (e.g. Windows 11, version 24H2).
Quality updates appear as cumulative updates with KB numbers (e.g. KB5034765).

4) Practical handling

Install quality updates promptly — they close security holes.
Delay feature updates until your line-of-business apps and drivers are certified for the new version.
Before a feature update, create a restore point or system image if you rely on specialised software.

5) Uninstall a feature update rollback window

Settings → System → Recovery → Go back appears for ~10 days after feature upgrade if rollback files remain.
Disk Cleanup removing previous Windows installation removes rollback option.

6) Read version with PowerShell

Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" | Select-Object DisplayVersion, UBR

7) End of servicing dates

Each Windows version has an end date — quality updates stop when version falls out of support.
Check lifecycle at Microsoft lifecycle documentation for your DisplayVersion string.

8) Enablement packages

Some “version bumps” ship as enablement packages (small download activating 24H2 features already on disk) — still count as feature updates in history.

Check Update history for “Windows 11 Version 24H2 enablement package” style entries.
Reboot once after enablement — partial activation causes odd Settings version mismatches.

Verification checklist

Record DisplayVersion before and after each feature upgrade. Quality updates should not change DisplayVersion — if it jumps unexpectedly, you installed a feature package disguised as cumulative.

Reboot once after changes that affect services, drivers, or firmware.
Confirm the original problem is resolved under normal daily use, not only immediately after the fix.
Note date, Windows version (Settings → System → About), and what changed in your personal runbook for next time.