Hulp op afstand

Knowledge base

Remove a Windows update when Windows no longer boots

Use this guide when a boot loop, Automatic Repair or blue screen began directly after a Windows quality update.

Start with the built-in uninstall option in Windows Recovery Environment. Use manual offline DISM only if WinRE cannot complete the operation and you have identified the correct Windows volume and exact registered package.

Lees in het Nederlands →

Before you begin

  • protect important data;
  • check that the SSD is detected reliably;
  • make sure the BitLocker recovery key is available;
  • record the current error code and failure pattern;
  • do not change several packages, drivers and boot settings at once.

Route A: remove the update through WinRE

  1. Open Troubleshoot → Advanced options.
  2. Choose Uninstall Updates.
  3. Select Uninstall latest quality update.
  4. Allow the operation to finish.
  5. Restart and record what changes.

Expected: Windows removes the recent quality update or reports that the operation cannot be completed.

If Windows boots afterwards, test one more restart. If only the stop code or failure point changes, keep that information.

Do not jump to manual DISM removal if

  • the SSD is unreliable;
  • the update may still be incomplete;
  • package dependencies are unclear;
  • several related packages have the same date;
  • checkpoint cumulative updates are involved;
  • Windows reports Install Pending or Uninstall Pending and you do not understand the transaction;
  • you cannot identify the actual Windows volume confidently.

Route B: offline DISM from WinRE or Windows PE

The examples use D: for Windows and E: for logs and temporary files. Verify those letters on your system.

1. Check the volume and BitLocker

diskpart
list volume
exit
dir D:\Windows
dir D:\Program Files
dir D:\Users
manage-bde -status

Stop unless D: is clearly the intended, unlocked Windows installation.

2. Create log and scratch directories

mkdir E:\logs
mkdir E:\scratch

3. Save package state before changing it

dism /Image:D:\ /Get-Packages /Format:Table
dism /Image:D:\ /Get-Packages /Format:Table > E:\logs\packages-before.txt

DISM manages the registered package identity in the Windows image. Do not rely only on the downloaded .msu filename.

4. Inspect the candidate package

dism /Image:D:\ /Get-PackageInfo /PackageName:PACKAGE_IDENTITY_HERE

Check:

  • the full identity;
  • state such as Installed, Superseded or Pending;
  • installation date;
  • that it is the intended cumulative package.

Do not remove a servicing-stack package merely because it is recent.

5. Remove the registered package identity

dism /Image:D:\ /Remove-Package /PackageName:PACKAGE_IDENTITY_HERE /ScratchDir:E:\scratch /LogPath:E:\logs\dism-remove.log /NoRestart

An .msu is installation media. This command removes the registered package identity from the offline Windows image.

6. Check the state afterwards

dism /Image:D:\ /Get-Packages /Format:Table
dism /Image:D:\ /Get-Packages /Format:Table > E:\logs\packages-after.txt
dism /Image:D:\ /Cleanup-Image /ScanHealth /LogPath:E:\logs\dism-scanhealth-after-remove.log

Expected: the intended package state changes and DISM can still read the component store.

Restart Windows and record the result.

Rollback did not help

Do not automatically remove more packages. Check the component store and update state first:

Do not delete pending.xml, registry metadata or complete update caches as a default next step.

Stop if

  • package identity or prerequisites are unclear;
  • a pending transaction cannot be explained;
  • SSD or BitLocker state is uncertain;
  • you have no log location or recovery copy;
  • DISM cannot open the image reliably.

Need help? Contact Forcys →