Fix ERROR_BOOT_ALREADY_ACCEPTED (0x00000434) on Windows

What's Actually Happening Here

The error code 0x00000434 with the message "The current boot has already been accepted for use as the last-known-good control set" isn't a crash or a failure—it's Windows telling you that the boot configuration already performed an action you're trying to repeat. The system already marked your current boot session as stable and copied it to the LastKnownGood control set in the registry.

This usually pops up when you manually try to force a last-known-good save via bcdedit or when a third-party tool (like a boot manager or driver updater) attempts to set the boot entry's lastknowngood flag after Windows already did it automatically during a successful boot. You'll see it most often on Windows 10 and 11 systems that have been modified with BCD tweaks or dual-boot setups.

The good news: your system is fine. The boot is already accepted. The bad news: the error keeps showing because something is trying to re-set a flag that's already set. The fix is to stop that retry.

Quick Fix (30 seconds) – Clear the BCD Flag

Open Command Prompt as Administrator. Hit Windows key, type cmd, right-click Command Prompt, select "Run as administrator." Then run:

bcdedit /deletevalue {current} lastknowngood

What this does: it removes the custom lastknowngood parameter from your current BCD entry entirely. The OS will then fall back to its default behavior—automatically accepting a boot as good after 30 seconds of uptime. No more manual flag attempts, no more error.

Why this works: The error fires when a tool or script calls bcdedit /set {current} lastknowngood on but the current boot session already has LastKnownGood set to 1 in the registry hive. By deleting the BCD entry, the tool's next attempt will either succeed (because Windows will re-create the flag fresh) or fail silently—but either way, the specific conflict is gone.

If the error came from a scheduled task or startup script, that's still going to run. But removing the value stops the error from appearing because there's no stale flag to collide with. Reboot is optional—the change takes effect immediately for the current boot session.

Moderate Fix (5 minutes) – Check Startup Scripts and Scheduled Tasks

The quick fix stops the symptom. If the error comes back after reboot, something is re-applying the BCD setting. Here's how to find it.

Step 1: Check Task Scheduler

Open Task Scheduler (taskschd.msc). Look under Task Scheduler Library for any task that runs bcdedit.exe or bcdboot.exe or contains the string "lastknowngood" in its actions. You can search by sorting the Actions column or by exporting all tasks to XML and grepping:

schtasks /query /xml > tasks.xml

Then open tasks.xml in Notepad and search for "lastknowngood". If you find one, disable or delete that task. Common culprits: driver installation helpers, OEM recovery tools, and boot manager updaters like EasyBCD or rEFInd.

Step 2: Search for Startup Scripts

Check these locations for a .bat, .ps1, or .vbs script that calls bcdedit:

• %SystemRoot%\System32\GroupPolicy\Machine\Scripts\Startup\
• %AppData%\Microsoft\Windows\Start Menu\Programs\Startup\
• C:\Windows\System32\Tasks\ (though these are Task Scheduler entries, not scripts)

Open each file and search for "lastknowngood" or "bcdedit /set". If found, remove that line or delete the script. Be careful—some scripts are there for legitimate reasons like BitLocker PIN recovery. Don't nuke the whole file; just comment out the offending line with REM (batch) or # (PowerShell).

Step 3: Check for Third-Party Boot Managers

If you use a tool like EasyBCD, open it and look under Edit Boot Menu or Advanced Settings. Some versions have a checkbox labeled "Automatically save boot as last known good" or similar. Uncheck it. Also check the Tools menu for any "Force Last Known Good" setting. Apply changes and reboot.

Advanced Fix (15+ minutes) – Manual BCD Rebuild and Registry Cleanup

If the error persists after clearing the BCD flag and removing scripts, the problem might be deeper—a corrupted BCD store or a stale registry key. This fix rebuilds the boot configuration from scratch and cleans up the registry.

Step 1: Backup and Rebuild BCD

Back up your current BCD store first:

bcdedit /export C:\bcd_backup.dat

Then delete and recreate the store. Warning: This only works if your system partition (usually the EFI partition or System Reserved) is intact. You'll need the Windows installation media for the next step if this fails.

bcdedit /createstore C:\BCD.new
bcdedit /import C:\BCD.new
bootrec /rebuildbcd

If bootrec /rebuildbcd doesn't find your Windows installation, you'll need to manually add it. First find your Windows partition drive letter (usually C: but could be different in recovery). Then:

bcdedit /create {bootmgr} /d "Windows Boot Manager"
bcdedit /set {bootmgr} device partition=C:
bcdedit /create /d "Windows 10" /application osloader
bcdedit /set {GUID} device partition=C:
bcdedit /set {GUID} path \Windows\system32\winload.exe
bcdedit /set {GUID} osdevice partition=C:
bcdedit /set {GUID} systemroot \Windows
bcdedit /displayorder {GUID} /addlast

Replace {GUID} with the actual GUID returned by the /create command. Reboot.

Step 2: Clean Registry ControlSet Entries

The LastKnownGood flag also lives in the registry under HKLM\SYSTEM\Select. An invalid pointer there can cause the error even after BCD is clean.

1. Open Regedit as Administrator.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\Select.
3. Look at these values:
   • Current – points to the current control set (usually 1).
   • Default – should match Current.
   • Failed – should be 0 if no failed boot.
   • LastKnownGood – should point to a control set number that exists under HKLM\SYSTEM\ControlSet00x.
4. If LastKnownGood points to a control set that doesn't exist (e.g., ControlSet003 when only 001 and 002 exist), set it to the same value as Current. The typical safe setting is 1.
5. If Failed is set to a non-zero value, change it to 0.

Why this matters: The registry Select key tells Windows which control set to load as LastKnownGood. If it references a missing set, Windows may try to force an accept via BCD to compensate—triggering the conflict. Aligning the values stops that.

Step 3: Reset WMI Repository (Rare Case)

In very stubborn cases, a corrupted WMI repository can cause boot configuration tools to misreport state. This is uncommon but worth trying if nothing else worked. Run:

winmgmt /salvagerepository
winmgmt /resetrepository

This rebuilds the WMI database. You'll need to reboot and re-run bcdedit /deletevalue {current} lastknowngood afterwards. Only do this if you've exhausted other options—it can break WMI-dependent services like Windows Update or System Restore if the repair fails.

When to Give Up and Restore

If you've done all three fixes and the error still appears, you're likely dealing with a deeply corrupted boot environment or a hardware issue (failing disk, bad RAM writing garbage to the BCD store). The pragmatic next step: boot from a Windows installation USB, go to Repair your computer → Troubleshoot → System Restore to a point before the error started. If no restore points exist, use Reset this PC keeping your files. That will rebuild the boot configuration from scratch and give you a clean start.

The error is annoying but not dangerous. Don't lose sleep over it.