Repair BCD that does not contain valid operating-system information

Windows Recovery reports that the Boot Configuration Data file does not contain valid information for an operating system, normally with error code 0xc0000098. The BCD file may exist but contain an invalid, incomplete, or stale Windows loader definition.

Searchable Windows error codes and exact messages

Search the exact File: value with the code. Common values are \BCD, \Boot\BCD, \EFI\Microsoft\Boot\BCD, or \Windows\System32\winload.efi. When winload.efi is named, determine whether the BCD path is wrong or the file itself is missing before choosing FIX-012 or FIX-013.

Use this procedure when the Windows and system partitions are readable and the BCD store either fails enumeration or lacks a coherent loader for the intended Windows installation.

Do not use it when the drive is absent, the system partition is missing, a specific system file has a checksum failure, or BCD inspection shows a coherent loader that points to the correct Windows volume.

The exact build and the event that damaged BCD may remain unknown. The Windows volume, system partition, partition style, and BCD-store location must be detected.

• Windows Recovery Environment or installation media
• Command Prompt
• Readable Windows and system partitions
• Free space on the Windows volume for a BCD backup

Open Repair your computer > Troubleshoot > Advanced options > Command Prompt. W: represents the detected Windows volume and S: the detected system partition.

1. Record the error code, message, and File: value.

2. Detect and map the layout:

   diskpart
   list disk
   list volume
   select volume <Windows-volume-number>
   detail volume
   assign letter=W
   select disk <Windows-disk-number>
   list partition
   select partition <system-partition-number>
   detail partition
   assign letter=S
   exit
   

3. Verify the intended installation:

   dir W:\Windows\System32\Config\SYSTEM
   dir W:\Windows\System32\winload.*
   

4. For UEFI/GPT, enumerate the store:

   dir S:\EFI\Microsoft\Boot\BCD
   bcdedit /store S:\EFI\Microsoft\Boot\BCD /enum all /v
   

5. For BIOS/MBR, use:

   dir S:\Boot\BCD
   bcdedit /store S:\Boot\BCD /enum all /v
   

6. Confirm one or more of these conditions:

   • BCDEdit cannot open or parse the existing store.
   • No Windows Boot Loader entry describes the intended installation.
   • The loader's path, systemroot, device, or osdevice is absent or demonstrably wrong.
   • The store contains an incomplete setup/upgrade loader but no valid normal loader.

7. If the store enumerates correctly and its loader points to the intended Windows volume and loader file, stop. 0xc0000098 may instead describe the named file, signature, disk, or memory path.

UEFI/GPT branch

1. Create the backup directory:

   md W:\BootRepairBackup
   

2. Preserve the current BCD file even if BCDEdit cannot parse it:

   copy S:\EFI\Microsoft\Boot\BCD W:\BootRepairBackup\BCD-before-0xc0000098-repair
   

3. Attempt the least disruptive reconstruction first:

   bcdboot W:\Windows /s S: /f UEFI /v
   

4. Re-enumerate the store:

   bcdedit /store S:\EFI\Microsoft\Boot\BCD /enum all /v
   

5. Restart and test.

6. If the identical 0xc0000098 BCD error remains and the store is still demonstrably invalid, return to Command Prompt and preserve the invalid store under a second name:

   attrib -h -s -r S:\EFI\Microsoft\Boot\BCD
   ren S:\EFI\Microsoft\Boot\BCD BCD.invalid-0xc0000098
   

7. Build a fresh BCD store from the verified Windows installation:

   bcdboot W:\Windows /s S: /f UEFI /v
   

8. Restart twice.

BIOS/MBR branch

1. Back up the existing BCD:

   md W:\BootRepairBackup
   copy S:\Boot\BCD W:\BootRepairBackup\BCD-before-0xc0000098-repair
   

2. Run the non-destructive repair:

   bcdboot W:\Windows /s S: /f BIOS /v
   

3. If the same BCD-specific error remains and the store still cannot be parsed, preserve it by renaming it:

   attrib -h -s -r S:\Boot\BCD
   ren S:\Boot\BCD BCD.invalid-0xc0000098
   

4. Build a fresh store:

   bcdboot W:\Windows /s S: /f BIOS /v
   

5. Restart twice.

• BCDBoot creates a coherent loader and Windows starts: The invalid BCD definition was repaired.
• BCDBoot reports success but 0xc0000098 still names winload.efi or a driver: Use FIX-013 or FIX-018 according to the file and message.
• The new store omits an intentional dual-boot entry: Restore or reconstruct that entry only after the primary Windows installation starts reliably.
• BCDBoot cannot copy files: Verify the selected Windows directory, system partition, free space, and file-system health.
• The disk or partition becomes intermittently unreadable: Stop; BCD reconstruction is not a storage-hardware repair.

• Do not delete the original BCD file before making a copy.
• Do not assume every 0xc0000098 is a BCD failure; follow the displayed File: value.
• Do not format the ESP or System Reserved partition.
• Do not use a BCD store found on another Windows disk without proving firmware uses it.
• Do not mix UEFI and BIOS repair commands on the same detected installation.

Return to WinRE, preserve the newly generated store, and restore the backup to its original path. Restoring an invalid store will normally restore the error; rollback is mainly for recovering intentional entries and comparing configuration.

• Windows starts normally twice.
• bcdedit /enum all /v shows a coherent Windows loader.
• device, osdevice, path, and systemroot match the intended installation.
• The Recovery screen no longer reports 0xc0000098.
• Intentional recovery or dual-boot entries are either preserved or deliberately reconstructed.

Confidence is approximately 85% when the screen names BCD and store inspection proves missing or invalid loader information. Stop when BCD is coherent, the displayed file is a named system binary, the storage path is unstable, or the correct system partition cannot be distinguished.