ERROR_ALREADY_RUNNING_LKG 0X00000432 Fix
Windows won't boot or shows this error because it's stuck in Last Known Good Configuration mode. Here's how to break that loop.
Quick Answer
Boot from a Windows installation USB, open Command Prompt (Shift+F10), then run bootrec /fixmbr, bootrec /fixboot, bootrec /scanos, and bootrec /rebuildbcd in that order. That usually clears the LKG flag and lets Windows start fresh.
What's Happening Here?
Windows has a fallback called Last Known Good Configuration. When a critical driver or registry change fails during boot, Windows automatically reverts to the last known working hardware profile. The problem? Once it's in this mode, sometimes the boot manager gets stuck — it keeps trying to apply that fallback instead of booting normally. You'll see the error 0X00000432 with the message "The system is currently running with the last-known-good configuration." This usually happens after a failed driver update, a corrupted system file, or an improper shutdown (like pulling the plug or a power outage) while Windows was saving its configuration. I've seen this most often on Windows 10 and 11 after a botched graphics driver install.
Fix It Step by Step
- Create a Windows installation USB — You'll need another PC for this. Download the Windows Media Creation Tool from Microsoft's site, run it, and choose "Create installation media for another PC." Pick a USB drive (at least 8GB). This takes 10–15 minutes.
- Boot from the USB — Plug it into the broken PC. Restart and press the key to open the boot menu (F12 on Dell, F9 on HP, F2 on Lenovo, or Esc on Asus). Select the USB drive.
- Get to Command Prompt — On the Windows Setup screen, click Next. Then click Repair your computer at the bottom left. Choose Troubleshoot > Advanced options > Command Prompt.
- Run bootrec commands — In the Command Prompt, type these one at a time, pressing Enter after each. Wait for each to finish — you'll see "The operation completed successfully" for each.
Forbootrec /fixmbr bootrec /fixboot bootrec /scanos bootrec /rebuildbcd/rebuildbcd, it'll ask if you want to add a Windows installation to the boot list. Type Y and press Enter. - Exit and restart — Type
exit, close the window, choose Continue to restart. Unplug the USB when it starts to boot.
What to Expect After Running Those Commands
Your PC should boot normally now. If it still shows the same error, don't panic. Sometimes the BCD store is too damaged for bootrec alone. In that case, go back to the Command Prompt and try this alternative sequence.
Alternative Fix: Rebuild BCD Manually
- Boot again from the USB and open Command Prompt as above.
- Find your Windows drive letter — it's usually C: but could be D: or E:. Type
diskpartthenlist volumeto see which volume has the Windows label. Note the letter. Typeexitto leave diskpart. - Run these commands, replacing C: with your Windows drive letter if different.
bcdedit /export C:\bcdbackup attrib -s -h -r C:\boot\bcd ren C:\boot\bcd bcd.old bootrec /rebuildbcd - When prompted, type Y to add the installation. Exit and restart.
If That Still Fails: Boot into Safe Mode Manually
Sometimes the LKG flag doesn't clear because a specific driver is corrupt. Booting into Safe Mode bypasses that driver and lets you remove it.
- Boot from the USB again. At the setup screen, click Repair your computer > Troubleshoot > Advanced options > Startup Settings > Restart.
- After the restart, press 4 or F4 to choose Enable Safe Mode.
- Once in Safe Mode, open Device Manager (right-click Start menu, choose Device Manager). Look for any device with a yellow exclamation mark — that's your culprit. Right-click it and choose Uninstall device. Check "Delete the driver software for this device" if available.
- Restart normally.
Prevention Tips
The real fix is avoiding the trigger. Don't interrupt Windows during a shutdown or restart — especially when it says "Configuring updates." If you're installing a driver, always create a restore point first (search "create a restore point" in the Start menu). Keep your system drive healthy — run chkdsk C: /f every few months from an admin Command Prompt. And if you see this error repeatedly, check your hard drive's health with CrystalDiskInfo or the manufacturer's tool. A failing drive can corrupt the boot files and keep you stuck in LKG hell.
Was this solution helpful?