View update history and uninstall a bad Windows update

See which updates are installed, remove one that broke an app with Settings, wusa or DISM, and stop it from reinstalling straight away.

  • Intermediate
  • Windows VPS · Admin RDP
  • 5 min read

By RunRacks Team · Published

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:12230, or the browser console in your Dashboard 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.

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:

PowerShell
Get-HotFix | Sort-Object InstalledOn -Descending |
  Select-Object -First 10 HotFixID, Description, InstalledOn

Example output:

Text
HotFixID  Description      InstalledOn
--------  -----------      -----------
KB5044281 Security Update  10/9/2026 12:00:00 AM
KB5044097 Update           10/9/2026 12:00:00 AM

These 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

  1. Open update history as above and click Uninstall updates.
  2. On Windows 11 and Server 2025, a list opens in Settings. On older versions, the Installed Updates page opens in Control Panel.
  3. Select the KB and click Uninstall.
  4. 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:

Command Prompt
wusa /uninstall /kb:5044281

Replace 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.

  1. List installed packages and find the one for your update:
Command Prompt
   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.

  1. Remove it, copying the full package name exactly:
Command Prompt
   DISM /Online /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.2762.1.10

The package name above is an example. Use the exact name from your list.

  1. Restart when prompted.

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:

Set a reminder to undo the pause or hide once Microsoft or the app vendor releases a fix.

Check it works

After the restart:

  1. Run Get-HotFix -Id KB5044281 with your KB. It should return an error saying no hotfix was found.
  2. Check the build number with winver. It should be lower than before.
  3. 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

Was this guide helpful?

Still stuck?

Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.

Troubleshooting

Fix Nginx 413 Request Entity Too Large

Nginx returns 413 Request Entity Too Large when an upload is bigger than client_max_body_size. Raise the limit for one site or the whole server, match PHP's limits, and test.

  • Beginner
  • Linux VPS
  • 5 min read

Troubleshooting

Is your ISP or router blocking port 12230? How to tell

Work out whether your internet provider, home router, parental controls or a proxy is blocking RDP port 12230, and collect the details support needs to help.

  • Intermediate
  • Windows VPS · Admin RDP
  • 5 min read