Desperate, need help in Eight Forums, please!

[tecknot]

If bcdboot successfully ran ("Boot files successfully created") but error 0xc000000f remains, check the UEFI firmware boot order for multiple Windows Boot Manager entries. If more than one exists:

- Remove old or invalid Windows Boot Manager entries (if the firmware supports this).
- Or set the Windows Boot Manager entry corresponding to the correct EFI system partition as the first boot option.

Thanks, Celery. I have only one Windows Boot Manager entry when I go into the UEFI/Bios.

Kind regards,

tecknot

 

[tecknot]

If bcdboot successfully ran ("Boot files successfully created") but error 0xc000000f remains, check the UEFI firmware boot order for multiple Windows Boot Manager entries. If more than one exists:

- Remove old or invalid Windows Boot Manager entries (if the firmware supports this).
- Or set the Windows Boot Manager entry corresponding to the correct EFI system partition as the first boot option.

Thanks, Celery. I have only one Windows Boot Manager entry when I go into the UEFI/BIOS.

Kind regards,

tecknot

 

[Celery]

ChatGPT:

Temporarily disable Secure Boot​

On Windows 8/8.1 systems especially:

• Secure Boot can block a rebuilt boot chain
• The error message does not always change

This is a diagnostic step, not a permanent fix.

 

[tecknot]

ChatGPT:

Thanks again, Celery. Secure boot is disabled.

Kind regards,

tecknot

 

[Celery]

With Secure Boot disabled, does Windows boot now?

 

[tecknot]

With Secure Boot disabled, does Windows boot now?

Nope. Same error.

Kind regards,

tecknot

 

[Celery]

diskpart
list volume (find the EFI partition number)
select volume # (use the EFI partition number)
format quick fs=fat32 (format your EFI partition)
assign letter=z
list volume (find the Windows partition letter)
exit

bcdboot x:\windows /s z: /f uefi

- replace "x" with the Windows partition letter

 

[tecknot]

diskpart
list volume (find the EFI partition number)
select volume # (use the EFI partition number)
format quick fs=fat32 (format your EFI partition)
assign letter=z
list volume (find the Windows partition letter)
exit

bcdboot x:\windows /s z: /f uefi

- replace "x" with the Windows partition letter

Boot files successfully created.

 

[tecknot]

Boot files successfully created.

Same error.

 

[Celery]

ChatGPT:

At this point, that result is extremely diagnostic.

If:

• the EFI System Partition was explicitly formatted as FAT32
• bcdboot X:\Windows /s Z: /f UEFI reports “Boot files successfully created”
• Secure Boot is disabled
• the firmware shows one Windows Boot Manager
• and the system still throws 0xc000000f

then the conclusion is no longer “boot files” or “BCD”.

---

What this definitively means​

The firmware is loading bootmgfw.efi, but Windows Boot Manager cannot access the Windows installation it points to.

So the failure occurs after the EFI stage.

This narrows the cause to one of only a few remaining possibilities.

---

Most likely remaining causes (in order)​

The Windows partition is not where the BCD thinks it is​

Even though bcdboot succeeded, the Windows partition may be:

• on a different disk than expected
• offset incorrectly due to partition changes
• using a disk signature or partition GUID that changed

This happens frequently if:

• partitions were created/deleted manually
• disks were cloned
• disk order changed in firmware

At this stage, the BCD exists, but it points to the wrong Windows volume.

---

Disk or filesystem errors on the Windows partition​

If the Windows partition has:

• filesystem corruption
• unreadable sectors
• damaged NTFS metadata

Boot Manager will fail with 0xc000000f, even though the ESP and BCD are perfect.

This is now very likely.

Next diagnostic step (critical):

chkdsk X: /f

---

Winload-related files are missing or corrupted​

If these files are missing or damaged:

• \Windows\System32\winload.efi
• registry SYSTEM hive

The error will still reference BCD, even though BCD is fine.

This is a known quirk of Windows boot error reporting.

---

Disk controller / firmware mode mismatch​

Less common, but possible:

• SATA mode changed (AHCI ↔ RAID)
• Storage controller disabled or changed
• NVMe controller firmware issues

Windows Boot Manager loads, but cannot mount the OS volume.

---

What is​

You can now confidently rule out:

• Missing EFI files
• Corrupt ESP
• Missing or corrupt BCD
• Secure Boot
• Wrong bcdboot usage
• Windows 8 vs 8.1 differences

All of those have been exhaustively eliminated.

---

Correct next step (there is only one)​

Check and repair the Windows partition itself.

chkdsk X: /f

If that fails or reports major errors:

sfc /scannow /offbootdir=X:\ /offwindir=X:\Windows

---

Final diagnosis​

This is no longer a bootloader problem.
It is a Windows volume accessibility or integrity problem.

The boot chain is now correct — Windows simply cannot be loaded from the target partition.

 

[tecknot]

ChatGPT:

Thank you, Celery. I am confused at:

<span>chkdsk X: /f<br></span>

If that fails or reports major errors:

<span>sfc /scannow /offbootdir=X:\ /offwindir=X:\Windows<br></span>

Can you translate for me?

Kind regards,

tecknot

 

[Celery]

I am confused at:

I edited the post. It should be ok now.

 

[tecknot]

Thank you, Celery. I am confused at:

<span>chkdsk X: /f<br></span>

If that fails or reports major errors:

<span>sfc /scannow /offbootdir=X:\ /offwindir=X:\Windows<br></span>

Can you translate for me?

Kind regards,

tecknot

Nevermind the previous post. Stage 1: 0 bad file records processed; Stage 2: 0 unidexed files scanned, 0 unindexed files recovered; Stage 3: Windows has scanned the file system and found no problems. No further action is required. 0KB in bad sectors.

 

[tecknot]

Nevermind the previous post. Stage 1: 0 bad file records processed; Stage 2: 0 unidexed files scanned, 0 unindexed files recovered; Stage 3: Windows has scanned the file system and found no problems. No further action is required. 0KB in bad sectors.

sfc /scannow results: Windows Resource Protection could no perform the requested operation.

 

[Celery]

sfc /scannow results: Windows Resource Protection could no perform the requested operation.

@zbook

 

[tecknot]

@zbook

@zbook already tried to help.

 

[antspants]

sfc /scannow results: Windows Resource Protection could no perform the requested operation.

Run:

DISM /Online /Cleanup-Image /RestoreHealth

 

[tecknot]

Hi Celery,

I've got to go take care of some business. I'll be back in a few hours. Thanks for all of your help.

Kind regards,

tecknot

 

[tecknot]

Run:

DISM /Online /Cleanup-Image /RestoreHealth

Hi Sinto,

I got an error: "DISM does not support servicing Windows PE with the /Online option."

Kind regards,

tecknot

 

[antspants]

Hi Sinto,

I got an error: "DISM does not support servicing Windows PE with the /Online option."

Kind regards,

tecknot

My apologies, you’re running it in WinRE and Online doesn’t work in there, I believe.

Can not stress system images strongly enough.