Skip to main content

How to Uninstall a Windows Update (Hotfix) in Batch Script

Occasionally, a Windows Update (KB) can cause unexpected issues such as system instability, software incompatibility, or even "Blue Screen of Death" errors. In these cases, the immediate solution is to remove the problematic update. While this can be done through the Control Panel, automating the uninstallation with a Batch script is a professional way to quickly revert changes across multiple machines or during remote troubleshooting. This guide demonstrates how to use the Windows Update Standalone Installer (wusa.exe) to uninstall updates silently and efficiently.

The Core Command: wusa.exe​

The primary utility for managing individual update packages in Windows is wusa.exe. To uninstall a specific update, we use the /uninstall switch followed by the KB number.

Essential Flags for wusa:​

  • /uninstall: Specifies that the update should be removed.
  • /kb:XXXXXXX: The ID number of the update.
  • /quiet: Performs the action without a user interface (silent).
  • /norestart: Prevents the computer from automatically rebooting after uninstallation.
Administrative Privileges Required

Removing a system-level security patch or update is a high-level system change. You MUST run your Batch script as an Administrator, or the wusa command will be rejected.

Creating the Uninstallation Script​

A robust uninstallation script should verify the update's presence before attempting to remove it and then handle the restart process gracefully.

@echo off
setlocal enabledelayedexpansion

rem 1. Define the target update
set "KB_ID=5031354"

echo ============================================================
echo   Windows Update Uninstallation Utility
echo ============================================================

rem 2. Check for Admin Rights
net session >nul 2>&1
if errorlevel 1 (
    echo [ERROR] Please run this script as Administrator.
    pause
    exit /b 1
)

rem 3. Check if the KB is actually installed
echo [PROCESS] Checking if KB%KB_ID% is installed...
powershell -noprofile -command "if (Get-HotFix -Id 'KB%KB_ID%' -ErrorAction SilentlyContinue) { exit 0 } else { exit 1 }"

if !errorlevel! neq 0 (
    echo [INFO] KB%KB_ID% is not installed on this machine.
    pause
    exit /b 0
)

echo [PROCESS] KB%KB_ID% found. Uninstalling. Please wait...

rem 4. Perform the uninstallation
wusa /uninstall /kb:%KB_ID% /quiet /norestart

rem 5. Capture the result immediately
set "wusaResult=!errorlevel!"

rem 6. Handle the result
if !wusaResult! equ 0 (
    echo [SUCCESS] KB%KB_ID% has been successfully removed.
    echo [IMPORTANT] A restart is required to finalize the process.
) else if !wusaResult! equ 3010 (
    echo [SUCCESS] KB%KB_ID% removed. A reboot is required to complete.
) else if !wusaResult! equ -2145116156 (
    echo [ERROR] This update is permanent and cannot be uninstalled.
) else (
    echo [ERROR] Failed to uninstall the update. Error Code: !wusaResult!
)

echo ============================================================
endlocal
pause

Explaining Error Code 3010​

In the world of Windows installers, the return code 3010 is not an error; it is a success code specifically meaning "Success, but a reboot is required to finish."

Common Pitfalls and How to Avoid Them​

Uninstalling Mandatory Updates​

Some cumulative updates or security baseline updates are marked as "Permanent" by Microsoft. If you try to uninstall one of these, wusa will return an error stating that the "Update is required by the operating system and cannot be uninstalled."

Wrong Way:

:: Trying to force a permanent update off
wusa /uninstall /kb:123456 /quiet
:: Result: Silent failure with no indication of what went wrong.

Correct Way: Check whether the update is uninstallable before attempting removal using DISM:

dism /online /get-packages | findstr /i "KB123456"

Packages marked as "Permanent" in the output cannot be removed.

The "No GUI" Blindness​

When using the /quiet flag, you won't see a progress bar. If the update is large, it might look like the script has frozen.

tip

If the script stays on the "Uninstalling..." line for more than 5 minutes, check Task Manager. The processes wusa.exe and TrustedInstaller.exe should show CPU activity while the removal is in progress.

Advanced: Using DISM for Persistent Updates​

If wusa fails to remove an update, you can use the Deployment Image Servicing and Management (DISM) tool as a more powerful alternative. This approach automatically finds the correct package name:

@echo off
setlocal enabledelayedexpansion

set "KB_ID=5031354"

echo [PROCESS] Searching for package matching KB%KB_ID%...

set "PKG_NAME="
for /f "tokens=3" %%p in ('dism /online /get-packages ^| findstr /i "KB%KB_ID%"') do (
    set "PKG_NAME=%%p"
)

if not defined PKG_NAME (
    echo [ERROR] No DISM package found for KB%KB_ID%.
    pause
    exit /b 1
)

echo [PROCESS] Removing package: !PKG_NAME!
dism /online /remove-package /PackageName:!PKG_NAME! /quiet /norestart

if !errorlevel! equ 0 (
    echo [SUCCESS] Package removed. A reboot is required.
) else (
    echo [ERROR] DISM removal failed. Error Code: !errorlevel!
)

endlocal
pause

Best Practices for Patch Management​

  1. Backup Data: Before uninstalling critical security updates, ensure the user has a fresh backup.
  2. Verify Post-Uninstall: After the reboot, verify the KB is truly gone: 
    powershell -noprofile -command "if (Get-HotFix -Id 'KB5031354' -ErrorAction SilentlyContinue) { Write-Host '[WARNING] Update is still present.' } else { Write-Host '[SUCCESS] Uninstallation verified.' }"
  3. Prevent Re-installation: If you don't hide the update after uninstalling it, Windows Update will simply download and install it again during the next automatic check.
info

To prevent an update from coming back, you would need to use a separate specialized tool (like the "Show or Hide Updates" troubleshooter from Microsoft) to "hide" the KB from the update servers.

Conclusion​

Uninstalling a Windows Update via Batch script is a vital recovery procedure for system maintenance. By utilizing the wusa utility with the appropriate flags for silent operation and reboot management, you can quickly mitigate issues caused by buggy patches. Whether you are managing a single workstation or a fleet of office PCs, this automated approach provides a reliable and repeatable way to maintain system stability. Always follow up a removal with a system reboot and verification to ensure the problematic code has been completely purged from your environment.

Table of Contents