Windows Won’t Boot After an Update or Driver? Fixed

It worked perfectly last night. Then Windows installed an update — or you installed a driver — and now Windows won’t boot after an update or driver install. It might hang on the spinning dots, sit on “Working on updates” for an hour, loop through Automatic Repair, or stop at a blue screen with a code you have never seen before.

This is the most common way a healthy PC dies, and it is also one of the easiest to reverse. An update or a driver changes something in the startup chain; Windows has a record of what it changed and, in nearly every case, a way to undo it. Your files are almost certainly untouched.

Below is the complete repair path, in the order that works fastest: undo the change first, repair the damage second, and reinstall only if both fail. Both branches — failed update and bad driver — are covered, so skim to the one that matches your situation.

Why an update or a driver can stop Windows from starting

Startup is a chain, and it only takes one broken link. Roughly, Windows:

1. Loads firmware and the boot manager from the EFI or system partition
2. Reads the Boot Configuration Data (BCD) store to find the operating system
3. Loads the kernel and the boot-start drivers — the storage, file-system and bus drivers needed to read the disk at all
4. Starts core services, then the rest of the drivers, then the sign-in screen

An update replaces files at steps 2, 3 and 4. A driver install changes step 3 or 4. If the replaced file is damaged, incompatible with your hardware, or only half-written when the power went out, the chain breaks — and you never reach a desktop.

That is also why the fix is usually reversal rather than repair: put back what was there before, and the chain works again.

Method 1 — Let a stuck update finish, then force one clean rollback

Feature updates legitimately take a long time, and interrupting them is how a slow update becomes a broken one.

1. If the screen says “Working on updates” and the disk light is active, leave it for at least an hour. Two hours on a mechanical hard drive is not unreasonable.
2. If it is genuinely frozen — no disk activity for 15 minutes — hold the power button for 10 seconds to shut down.
3. Power on once. Windows will very often report “Undoing changes made to your computer” and roll itself back. Let it finish completely.
4. If you reach the desktop, go to Settings → Windows Update and pause updates for a few weeks, then retry later.

Method 2 — Uninstall the update that broke it

If Windows will not start at all, use the recovery menu. Get there by forcing three interrupted boots — hold the power button for 10 seconds as soon as the logo appears, three times — and Windows offers recovery on the fourth start. If that does not work, see the other ways into WinRE.

From the menu

1. Troubleshoot → Advanced options → Uninstall Updates.
2. Choose Uninstall latest quality update — this is the monthly cumulative update and it is the usual culprit.
3. If that does not help, repeat and choose Uninstall latest feature update.

From the command line

Open Command Prompt and list what is installed against the offline image (replace C: with your Windows volume):

dism /Image:C:\ /Get-Packages

Then remove the offending package using its full package identity from that list:

dism /Image:C:\ /Remove-Package /PackageName:Package_for_KB5041585~31bf3856ad364e35~amd64~~10.0.1.0

From Safe Mode or a working desktop, the simpler route is:

wmic qfe list brief /format:table
wusa /uninstall /kb:5041585 /norestart

Method 3 — Roll back or remove the driver

A bad driver is easier to deal with than a bad update, because you usually know exactly which one it was.

Option A: Safe Mode, then Device Manager

1. Troubleshoot → Advanced options → Startup Settings → Restart, then press 5 for Safe Mode with Networking.
2. Open Device Manager, find the device you updated, right-click it and choose Properties → Driver.
3. Use Roll Back Driver if it is available. If not, choose Uninstall device and tick Delete the driver software for this device.
4. Restart normally, then install the driver from the manufacturer’s website — not from Windows Update, and not from a driver-pack aggregator.

If getting into Safe Mode is the problem, here are the entry methods, and if the PC is stuck in Safe Mode afterwards, use these commands to clear the Safe Mode boot flag.

Option B: Remove the driver offline

When Windows will not start at all, remove the driver against the offline image. First list what is installed:

dism /Image:C:\ /Get-Drivers

Then remove the one you suspect by its published name:

dism /Image:C:\ /Remove-Driver /Driver:oem12.inf

Or use pnputil, which also works on a live system and can enumerate third-party drivers cleanly:

pnputil /enum-drivers
pnputil /delete-driver oem12.inf /uninstall /force

Method 4 — Revert a half-applied update

Sometimes the update was never fully installed — it is pending, and those pending operations are what block startup.

dism /Image:C:\ /Cleanup-Image /RevertPendingActions

Then clear pending file renames from the offline registry hive:

reg load HKLM\OFFSYS C:\Windows\System32\config\SYSTEM
reg query "HKLM\OFFSYS\Select"
reg delete "HKLM\OFFSYS\ControlSet001\Control\Session Manager" /v PendingFileRenameOperations /f
reg unload HKLM\OFFSYS

Use whichever ControlSet the Current value points to.

Method 5 — Repair the boot configuration and boot files

A failed update frequently leaves the boot files or the BCD store inconsistent. Run Startup Repair once from Troubleshoot → Advanced options, then rebuild manually if needed.

diskpart
list vol
exit

Note your Windows volume and the small FAT32 EFI partition, then (adjusting letters):

bcdboot C:\Windows /s S: /f UEFI

For Legacy BIOS / MBR systems use /f BIOS. If bcdboot is not enough, fall back to:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

Known errors here have specific fixes: Element not found, the system cannot find the path specified, and the complete BCD rebuild guide.

Method 6 — Repair the Windows image

Once the change has been undone, repair whatever the failure damaged. Always run DISM first — it fixes the component store that SFC restores files from.

DISM /Image:C:\ /Cleanup-Image /RestoreHealth
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Back on the desktop, finish with the online versions:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

DISM takes 10–30 minutes and may appear frozen partway through. Errors like 0x800f081f or 0x80073712 are fixable — see the DISM and SFC error guide or the full system-file repair walkthrough.

Method 7 — System Restore

Windows normally creates a restore point before installing updates and drivers. Rolling back undoes the driver, service and registry changes in one step, and leaves your personal files completely alone.

1. Troubleshoot → Advanced options → System Restore.
2. Pick a restore point dated before the update or driver install.
3. Use Scan for affected programs to review the impact, then confirm.

Method 8 — Find a service that hangs at startup

Sometimes the update or driver is fine, but a service it installed never finishes starting, and Windows waits forever. This is what a clean boot is designed to isolate.

On a system that reaches the desktop slowly

1. Press Win + R, type msconfig and press Enter.
2. On the Services tab, tick Hide all Microsoft services, then click Disable all.
3. On the Startup tab, open Task Manager and disable every startup item.
4. Restart. If the PC starts normally, re-enable services in small groups — a handful at a time — restarting between batches until you find the one that hangs.

On a system that will not boot

You cannot use msconfig, but you can disable a service in the offline registry. Load the hive, find the active control set, and set the service’s Start value to 4 (disabled):

reg load HKLM\OFFSYS C:\Windows\System32\config\SYSTEM
reg query "HKLM\OFFSYS\Select"
reg add "HKLM\OFFSYS\ControlSet001\Services\ServiceName" /v Start /t REG_DWORD /d 4 /f
reg unload HKLM\OFFSYS

Record the original value first so you can put it back. Never disable core Windows services at random — that replaces one startup failure with another.

Method 9 — Check the disk

Forced shutdowns during an update are a classic cause of file-system damage, and that damage will keep breaking startup even after the update is gone.

chkdsk C: /f

If chkdsk repairs a lot or reports bad sectors, verify the drive before trusting the installation: how to check hard disk health.

The one-click option: undo the change and repair the damage in one pass

Fix it in three steps

1. Build a rescue USB on any working PC with the toolkit’s Create Rescue USB function, then boot the broken machine from it.
2. Let the environment scan finish. It locates your Windows installation, drives, boot mode and encryption status automatically.
3. Choose the repair that matches your situation — Manage Windows Updates to remove the update, Device Manager to disable the driver, or Guided Boot Failure Repair to run the whole chain. Then reboot.

Frequently asked questions

Will uninstalling an update or driver delete my files?

No. Uninstalling updates, rolling back drivers, System Restore, DISM, SFC and chkdsk all leave your personal files, programs and settings intact.

How long should I wait on “Working on updates” before I give up?

At least an hour, and up to two on a mechanical hard drive — provided the disk activity light is still blinking. Only force a shutdown if there has been no disk activity at all for 15 minutes or more.

I do not know which update or driver caused it.

Start with the most recent: uninstall the latest quality update first, then the latest feature update. For drivers, remove the one you installed last. If you are unsure, the toolkit’s log analysis reads the Windows recovery logs and names the root cause for you.

Can I stop Windows from doing this again?

Partly. Pause updates for a week or two after a failure so a fixed build ships, set active hours so restarts do not catch you out, and install drivers from the manufacturer rather than letting Windows Update choose them. Keeping a current rescue USB is the real safety net.

Should I just reset the PC?

Reset is slower and more disruptive than everything above, and it usually is not necessary. Try the reversal methods first — Methods 2, 3 and 7 resolve the majority of these cases. Keep reinstall as the last resort, not the first response.

Conclusion

When Windows stops booting after an update or a driver install, the fix is almost always reversal rather than reinstallation. Undo the change, then repair what the failure damaged, and the startup chain works again — with your files, applications and settings exactly where you left them.

Work down the methods in order, write down every change so you can reverse it, and if the command prompt is not where you want to spend your evening, the VMTechs Boot Repair Toolkit removes the update, disables the driver, repairs the boot chain and tells you what it found — even on a PC that refuses to start.

Please follow and like us: