Windows · Windows Server  ·  high  ·  Windows Update & servicing

A machine is broken by the latest update and needs it removed

Removing a cumulative update is not the same as uninstalling a program, and on a machine that will not boot it has to be done from WinRE.

What you see

After a Patch Tuesday a machine bluescreens, loses a feature, or will not boot at all, and the change needs reversing while the cause is investigated.

What is actually wrong

A regression in the update itself, or an interaction with a driver on that hardware. Either way the immediate need is to get the machine working.

Codes and articles

uninstall latest quality updatewusa /uninstallDISM /Remove-Package

Fixes (2)

Remove the update from a running Windows
Elevated PowerShell20 minutesmedium riskreversible

Windows still starts.

  1. List what went on recently and when.

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

  2. Try the simple route first.

    Command Prompt
    wusa.exe /uninstall /kb:5034441 /quiet /norestart

    wusa cannot remove a combined SSU+LCU package, which is how most cumulative updates now ship. When it refuses, use DISM below — that is expected, not a failure.

  3. If wusa refuses, find the package name.

    PowerShell
    DISM /Online /Get-Packages /Format:Table | Select-String 'RollupFix|LanguageFeatures|Package_for'

  4. Remove it by package identity.

    PowerShell
    DISM /Online /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.3803.1.9

  5. Pause updates so it does not reinstall before you have investigated.

    PowerShell
    Set-ItemProperty 'HKLM:\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings' -Name PauseUpdatesExpiryTime -Value ((Get-Date).AddDays(21).ToUniversalTime().ToString('yyyy-MM-ddTHH:mm:ssZ'))

    Without this the machine reinstalls the same update on its next scan and you are back where you started.

  6. Restart.

Confirm it workedThe update is gone and the symptom with it.
PowerShell
Get-HotFix -Id KB5034441 -ErrorAction SilentlyContinue
If you need to undo itResume updates and let it reinstall once the underlying cause is understood.
Remove the update from WinRE on a machine that will not boot
Windows Recovery Environment30 minutesmedium riskreversible

Windows no longer starts. Two failed boots normally bring WinRE up on its own.

  1. Reach WinRE — power off during boot twice, or boot installation media and choose Repair your computer.

  2. Try the built-in option first: Troubleshoot → Advanced options → Uninstall Updates → Uninstall latest quality update.

    This does exactly what the DISM commands below do, without needing the package name, and it handles combined SSU+LCU packages correctly.

  3. If that fails, open Troubleshoot → Command Prompt and find the Windows drive letter.

    Command Prompt
    diskpartlist volumeexit

  4. List the packages installed on the offline image, newest last.

    Command Prompt
    DISM /Image:D:\ /Get-Packages /Format:Table

  5. Remove the most recent one.

    Command Prompt
    DISM /Image:D:\ /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.3803.1.9

  6. Exit and restart.

Confirm it workedWindows boots to the sign-in screen.
If you need to undo itThe package can be reinstalled from the Microsoft Update Catalog once the cause is known.

Related faults

"There was a problem resetting your PC" — Reset this PC failsWindows0x80070643 installing KB5034441 — WinRE partition too smallWindows"Automatic Repair couldn't repair your PC" — the repair loopWindows0x80073712 / 0x800f081f — component store corruption or missing sourceWindows

Where this stops. This write-up was written and checked by hand. It says what each step changes, how to confirm it worked and how to reverse it, and anything destructive is flagged before you reach it. If it does not match what your machine is doing, search the Support Centre for the exact code or message — and when something needs a person, get in touch.