Most Windows updates install without trouble, but now and then one breaks an app, a driver or a login. When that happens, you need to know what was installed and when, and how to roll back the one that caused the problem. This guide covers both, plus how to stop the same update coming straight back.
Before you start
- Administrator access over Remote Desktop to
203.0.113.10:3389, or the browser console in your VPS provider's control panel if Remote Desktop is affected. - A rough idea of when the problem started. Compare it with the install dates below.
- A recent backup or snapshot if you have one. See Back up a Windows server.
Warning: Removing a security update leaves the server exposed to whatever it fixed. Treat removal as temporary while you or the app vendor find a proper fix, then reinstall.
View update history
In Settings
- Windows 11 and Windows Server 2025: Settings → Windows Update → Update history.
- Windows 10, Server 2019 and 2022: Settings → Update & Security → Windows Update → View update history.
The list groups quality updates, driver updates, definition updates and other updates, with install dates and KB numbers.
With PowerShell
Get-HotFix lists installed updates with their KB numbers and dates:
Get-HotFix | Sort-Object InstalledOn -Descending |
Select-Object -First 10 HotFixID, Description, InstalledOnExample output:
HotFixID Description InstalledOn
-------- ----------- -----------
KB5044281 Security Update 10/9/2026 12:00:00 AM
KB5044097 Update 10/9/2026 12:00:00 AMThese KB numbers are examples. Note the ones installed just before your problem started. Search the KB number on Microsoft's support site to read its known issues. Microsoft often lists a fix or workaround there.
Get-HotFix shows Windows component updates. It does not list Defender definition updates or app updates from the Microsoft Store.
Uninstall from Settings
- Open update history as above and click Uninstall updates.
- On Windows 11 and Server 2025, a list opens in Settings. On older versions, the Installed Updates page opens in Control Panel.
- Select the KB and click Uninstall.
- Restart when asked.
Uninstall with wusa
wusa (Windows Update Standalone Installer) removes an update by its KB number. Open an elevated Command Prompt or PowerShell:
wusa /uninstall /kb:5044281Replace 5044281 with your KB number, without the letters KB. You will be asked to confirm and to restart. To restart later, add /norestart, then restart yourself when ready.
Uninstall with DISM when wusa refuses
Recent cumulative updates are often combined with a servicing stack update. For those, wusa may say the update cannot be removed. DISM can still remove the cumulative update part.
- List installed packages and find the one for your update:
DISM /Online /Get-Packages /Format:Table | findstr /i "RollupFix"Cumulative updates appear as Package_for_RollupFix~... with a version string that includes the build number.
- Remove it, copying the full package name exactly:
DISM /Online /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.2762.1.10The package name above is an example. Use the exact name from your list.
- Restart when prompted.
Warning: The restart after removing a cumulative update can take a long time while Windows rolls back. Do not force a power-off from your VPS provider's control panel during this. Watch progress in the browser console.
Stop it reinstalling straight away
Windows Update will offer the same update again at the next scan. To stop that while you wait for a fix:
- Pause updates: if your version shows Pause updates on the Windows Update page in Settings, use it. Pausing has a maximum period, after which updates resume.
- Set updates to manual: on Windows Server, run
sconfigand set the update setting to Manual or Download only. See Use sconfig to manage Windows Server quickly. - Hide the update: with the PSWindowsUpdate module,
Hide-WindowsUpdate -KBArticleID KB5044281stops that KB being offered. See Install Windows updates from PowerShell with PSWindowsUpdate.
Set a reminder to undo the pause or hide once Microsoft or the app vendor releases a fix.
Check it works
After the restart:
- Run
Get-HotFix -Id KB5044281with your KB. It should return an error saying no hotfix was found. - Check the build number with
winver. It should be lower than before. - Confirm the app or feature that broke now works.
Troubleshooting
- "The update is required by your computer and cannot be uninstalled": it is a servicing stack update. These cannot be removed. Look for a newer cumulative update that fixes the problem instead.
- wusa returns no error but the update is still listed: wusa could not remove it. Use the DISM method above.
- Server stuck at "Undoing changes" after restart: wait. If it loops, see Fix the update "undoing changes" loop.
- The problem did not go away: the update may not have been the cause. Check Event Viewer for errors around the time the issue started.
Next steps
- Plan updates around your working hours: Windows Update and server maintenance.
- Install a specific fix later: Install a Windows update manually from the Update Catalog.
