How to Roll Back a Windows Update and Verify It Worked

If a recent Windows update made your PC crash, break drivers, slow down, or fail to boot, uninstalling that update or rolling the feature update back will often restore the previous working state. Pick the rollback path that matches what you can access now: the desktop, Safe Mode, or the Windows Recovery Environment. Follow the matching steps, then check the OS build and logs before allowing updates again.

Which symptom do you have right now? (pick a path)

Start with this quick checklist to pick the safest rollback method and understand risk.

• Desktop works, some apps crash or drivers fail intermittently: uninstall the offending update from Settings or Control Panel. Risk: low to moderate; reversible if you have a restore point or backup.

• Desktop boots but the system is unstable, UI crashes, or drivers fail in normal mode: start in Safe Mode and uninstall the update there. Risk: moderate; Safe Mode uses minimal drivers, so test devices after a normal restart.

• Windows won’t boot, shows a blue screen, or loops on startup: use WinRE to run System Restore or Uninstall Updates. Risk: moderate to high; if restore points or previous build files are missing, rollback may fail and you’ll need other recovery steps.

• A recent major feature update (a new build) completed and the system is worse: use the feature-update rollback (the “Go back” option) if it’s available within the rollback window and the previous installation files are present. Risk: higher and time-limited; this can remove apps or drivers installed after the update.

• Managed device (Intune, WSUS, GPO): check with your admin before rolling back — management tools can reinstall the update immediately.

What you need before you start

Collect permissions, backups, and the exact update identity before making changes.

• Accounts and permissions:
• You must be signed in as an Administrator or be ready to supply Administrator credentials when prompted.
• If you have only a standard account, get admin credentials before you begin; don't proceed without them.

• Identify the update (KB or build):
• If you can reach Settings, open Settings > Windows Update > Update history to note the KB number or feature update name and the install date.
• If Settings is unavailable, query updates from WinRE or a command prompt later; instructions appear in the WinRE and verification sections.

• Backups and restore points:
• Confirm you have current backups of important files (OneDrive sync, File History, or a manual copy to external media). If the desktop is reachable, copy critical documents now.
• Check for a System Restore point: open System Protection (Settings > System > About > Related links > System protection) or run rstrui.exe to view restore points before uninstalling anything.

• Collect troubleshooting evidence:
• Take screenshots or photos of error messages, BSOD stop codes, and the update entry showing the KB or build and timestamp.
• If you can run PowerShell as Administrator, collect system identifiers and installed updates with these commands:

Get-ComputerInfo | Select WindowsVersion, OsBuild, OsName
wmic qfe get HotFixID,InstalledOn,Description

• BitLocker and disk encryption:
• If BitLocker or another disk encryption is enabled, have the recovery key before you attempt rollback or restore operations; some recovery steps will require it.

Rollback steps for your situation (Settings, Safe Mode, WinRE, feature downgrade)

Pick the path you matched and follow the ordered steps exactly.

1) Normal desktop — uninstall via Settings or Control Panel

1. Confirm you are signed in as an Administrator.
2. Open Settings > Windows Update > Update history.
3. Select "Uninstall updates." This opens the Installed Updates view in Control Panel.
4. Find the offending update by KB number or recent install date, select it, and choose Uninstall.
5. Restart when prompted and test the affected app or driver.

If you prefer the command line and know the KB number, run this from an elevated Command Prompt:

wusa /uninstall /kb:5006670

If wusa reports the update can't be uninstalled, the update may be part of the current build and you should use the WinRE path.

2) Safe Mode — when the desktop starts but things are unstable

1. From the working desktop, open Start > Power, hold Shift, and click Restart to enter WinRE.
2. Choose Troubleshoot > Advanced options > Startup Settings > Restart.
3. Press the number for Safe Mode (usually 4 or 5).
4. In Safe Mode, open Settings > Windows Update > Update history > Uninstall updates, or Control Panel > Programs and Features > View installed updates.
5. Uninstall the KB and then restart to normal mode to test functionality.

3) Unbootable — use WinRE to restore or uninstall

1. If Windows fails to boot, reach WinRE by letting the system attempt to start three times and allow automatic repair, or boot from Windows installation media and select Repair your computer.
2. In WinRE choose Troubleshoot > Advanced options.

• To run System Restore:

1. Select System Restore, choose a restore point dated before the update, and run it.

• To uninstall the last quality or feature update:

1. Select Uninstall Updates.
2. Choose either "Uninstall latest quality update" or "Uninstall latest feature update" depending on which you need to remove.

3. Follow prompts and allow the machine to restart. After WinRE completes, boot to desktop and test.

If WinRE isn't available automatically, boot from Windows installation media, choose Repair your computer, and follow the same Advanced options path.

4) Feature-update rollback (major build)

1. If Settings > System > Recovery shows a "Go back" option, use it. This option appears only while the previous version files (Windows.old) are present and within the rollback window.
2. Click Go back, follow the on-screen prompts, keep the PC plugged in, and let the process run.

Typically takes 20–60 minutes and will reboot several times.

5) When command-line removal is necessary (advanced)

1. If GUI or WinRE options fail and you can boot to Safe Mode with Command Prompt or WinRE Command Prompt, query installed packages and attempt removal with DISM or package-specific removal commands.

How to verify the rollback succeeded

Start by checking the OS build, update history, logs, and basic functionality.

• Check OS build and update history:

1. Open Settings > System > About and confirm the OS build and version match the expected previous version.
2. Open Settings > Windows Update > Update history to confirm the KB or feature update shows an uninstall timestamp or no longer appears as installed.

• Verify with command-line queries (run as Administrator if possible):

Get-ComputerInfo | Select WindowsVersion, OsBuild, OsName
wmic qfe get HotFixID,InstalledOn,Description

• Inspect logs for rollback events:
• Open Event Viewer > Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational and look for uninstall or rollback entries.
• Generate or review WindowsUpdate.log with Get-WindowsUpdateLog if needed and inspect C:\Windows\Logs\CBS\CBS.log for component store activity during uninstall.

• Functional checks:
• Run the apps or reproduce the actions that failed before.
• Test peripherals, printers, Wi‑Fi/Ethernet, and GPU-accelerated tasks if drivers were involved.
• If a driver caused the issue, confirm the device shows a working driver in Device Manager and that Windows Update did not reinstall a problematic driver automatically.

• What to do if verification fails:
• If the build or KB still shows as installed, collect logs and notes, then retry using WinRE System Restore or move to an image restore.
• If specific hardware still fails after rollback, reinstall the OEM driver from the vendor rather than relying on Windows Update.

Block the update and next actions if problems persist

After a successful rollback, prevent Windows from reinstalling the same update immediately and plan follow-up steps.

• Short-term consumer controls:
• Pause updates in Settings > Windows Update > Pause updates for up to the available period.
• Use the Microsoft Show/Hide updates troubleshooter to hide a specific KB; verify the tool’s availability before using it.

• Managed devices:
• Local measures may be overridden by WSUS, Intune, or Group Policy. Ask your IT admin to block or delay the update at the management server.

• If rollback repeatedly fails or the device stays unbootable:
• Stop repeated rollback attempts and collect a support bundle: msinfo32 system summary, Get-ComputerInfo output, wmic qfe list, WindowsUpdate and CBS logs, and screenshots of errors. Note timestamps for installs and rollback attempts.
• Restore from a verified system image if one is available, or use Settings > System > Recovery > Reset this PC (Keep my files) only after you have good backups.

• When to get professional help:
• Escalate when you can’t reliably boot, when BitLocker or other encryption blocks access and you don’t have the recovery key, or when data recovery is required.

• Common post-rollback fixes:
• Reinstall OEM drivers from the vendor website if drivers still misbehave.
• If activation or profile issues occur, sign in with the Microsoft/Azure AD account used before and check Settings > System > Activation.
• If encrypted volumes are inaccessible, locate the BitLocker recovery key before any further changes.

What to collect when asking for help

Provide exact update IDs, logs, and a clear sequence of what you tried when you ask for support.

• Exact KB or build IDs and install timestamps.
• Steps you took to roll back and any error messages you saw.
• Exports or copies of WindowsUpdate and CBS logs, and Event Viewer entries around the install and rollback times.
• msinfo32 system summary and the output of the PowerShell commands shown earlier.
• Note whether the machine is managed and whether BitLocker is enabled, and include the recovery key location if asked (do not transmit the key insecurely).

Conclusion

After rollback and verification, decide whether to pause updates, block the problematic KB, or reinstall fixed updates and drivers. If the device remains unstable or unbootable, stop repeating rollback attempts, collect logs, and escalate to IT or vendor support. Always keep backups and the BitLocker recovery key handy.