PC crashing constantly after new Security Update KB5089549

To remove a problematic Windows security update like KB5089549 using DISM, follow the supported recovery patterns from the provided context. These require using the Windows Recovery Environment (WinRE) or System Recovery Options and then uninstalling the update by package name.

Because KB5089549 is not explicitly listed in the context, use the generic DISM-based removal method and identify the exact package name first.

1. Boot into the Windows Recovery Environment (WinRE)

If Windows still boots:

1. Hold Shift and select Restart from the Start menu or sign-in screen.
2. On the Choose an option screen, select Troubleshoot > Advanced options > Command Prompt.

If Windows does not boot reliably:

1. Turn on the PC and as soon as Windows (or OEM) logo appears, hold the power button to force shutdown.
2. Repeat this power-on/force-off cycle 2–3 times until Automatic Repair appears.
3. Select Advanced options > Troubleshoot > Advanced options > Command Prompt.

Alternatively, use installation media (if needed) as described in the context:

1. On a working PC, go to the Microsoft software download website and create installation media with the Media Creation Tool.
2. Boot the affected PC from that USB/DVD.
3. On the first setup screen, choose language and keyboard, select Next, then Repair your computer.
4. Select Troubleshoot > Advanced options > Command Prompt.

(These steps follow the pattern in “How to create and use installation media to load the Recovery Environment.”)

2. Identify the Windows drive letter in WinRE

In WinRE, the Windows partition might not be C:. To verify:

wmic logicaldisk get name

or try:

dir C:\Windows

If C:\Windows shows the Windows folder, use C: in the next commands. If not, try D: or another drive until the Windows folder is found. Replace C: below with the correct drive letter if different.

3. List installed packages and find KB5089549

In Command Prompt (WinRE):

dism.exe /image:C:\ /Get-Packages

This enumerates all installed packages in the offline image. Scroll through the output and look for a package whose name contains KB5089549.

The package name will look similar to examples in the context, such as:

• Package_for_KB4056897~31bf3856ad364e35~x86~~6.1.1.4
• Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

For KB5089549, expect something like:

• Package_for_KB5089549~31bf3856ad364e35~amd64~~<version>

Copy or carefully note the full PackageName string for KB5089549.

4. Remove the KB5089549 package with DISM

Use the exact package name from the previous step. Example pattern:

dism.exe /image:C:\ /remove-package /packagename:Package_for_KB5089549~31bf3856ad364e35~amd64~~<version>

Replace the entire Package_for_KB5089549... portion with the exact string from /Get-Packages output.

This follows the same method shown in the context for other updates, e.g.:

• dism.exe /image:c:\ /remove-package /packagename:Package_for_KB4056897~31bf3856ad364e35~x86~~6.1.1.4
• dism.exe /image:c:\ /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

Wait for DISM to complete. The tool should report that the uninstallation was successful.

5. Restart into Windows
6. Close Command Prompt.
7. Select Continue to exit the Recovery Environment and boot into Windows.

If the crashes stop, KB5089549 has effectively been removed. If issues persist, consider:

• Using System Restore from WinRE to roll back to a restore point before the update (as shown in the Windows 7/8.1 resolution steps in the context).
• As a last resort, using Reset this PC with Keep my files to reinstall Windows while preserving personal data (similar to the reset guidance in the context).

Note: DISM removal is a low-level operation on the component store. Ensure the correct package is targeted and only remove the specific KB associated with the crashes.

References:

• How to recover devices from an unbootable state after installing the January 2018 security update
• MS15-115: Description of the security update for Windows: November 10, 2015