Boot Configuration Data file is Missing in Windows 10

Posted by @Ada

July 16, 2018

Boot Configuration Data file is missing in Windows 10? You can refer to this article and find solutions.

Scenario

“I've got this blue screen every time I start up my computer that says: Your PC/Device needs to be repaired. The Boot Configuration Data file is missing some required information. File: \BCD. Error code: 0xc000000d. You'll need to use recovery tools. If you don't have any installation media (like a disc or USB device) contact your PC administrator or PC/Device manufacturer. How can I fix it? I'm using Windows 10 by the way. Thanks!”

Boot Configuration Data File is Missing Windows 10

As you know, when you boot your computer, it will check all the necessary configuration files required to make a successful startup. Therefore, if any of the file involved in this process is corrupted or missing, Windows would not be able to boot the system at all. The Boot Configuration Data file is part of configuration files. If the BCD boot file is missing or corrupted, you're likely to receive the error message: "The Boot Configuration Data for your PC is missing some required information."

How to fix Boot Configuration Data file is missing error in Windows 10?

Method 1. Run Startup Repair

You can first try to run Startup Repair to fix this issue. Startup Repair can help you to repair Windows installation files.

Step 1. To Run Startup repair, you need a Windows installation disk. Insert the Windows bootable installation disk and restart your PC.

Step 2. When prompted to Press any key to boot from CD or DVD, press any key to continue. Select language and other preferences, and click Next.

Step 3. Click Repair your computer>Troubleshoot >Advanced options>Automatic Repair.

Step 4. Wait until the Windows Automatic Repair complete.

Restart your Windows and check whether you still receive "The Boot Configuration Data file is missing" error message in your Windows 10. If yes, continue to the next method.

Method 2. Rebuild BCD

Still, you need a Windows installation disk. Then follow the steps below to rebuild BCD.

Step 1. Insert your installation media into the computer. When you are at the Windows Setup interface, click "Repair your computer."

Step 2. Navigate to Troubleshoot>Advanced options> Command Prompt. You will open the command prompt.

Step 3. Type the following command and press Enter after each command.

  • Bootrec /fixmbr 

  • Bootrec /fixboot

  • Bootrec /scanos 

  • Bootrec /rebuildbcd 

Step 4. At last, type “A” to add the installation to the boot list.

Step 5. Exit the command prompt with the X button on the top of the window.

These two methods can also be applied to fix Boot Configuration Data file is missing in Windows 8/7.

How to avoid this issue happening again?

As you know, the Boot Configuration Data file is a part of system files. It is vulnerable and may affect the whole Operating System if it is missing or damaged. Therefore, you’d better make an image backup of the system files after fixing Boot Configuration Data file is missing issue.

AOMEI Backupper is a perfect tool to backup system. It is free and easy to use. Only a few clicks, you can backup the system without efforts. This software supports Windows 7, 8, 10, Windows XP and Visa. To backup system, follow the steps below.

Step 1. Download AOMEI Backupper and launch the software. At the home page, click Backup and select System Backup.

System Backup

Step 2. Select another location as destination location. You can backup Windows to USB, external hard drive, cloud drive, internal hard drive, etc.

System Backup Task Name

Step 3. To keep the backup up to date, you can click Schedule to create automatic backup.

Step 4. Click Start Backup at last and wait for the process done.

Conclusion

When you encounter Boot Configuration Data file is missing in Windows 10 issue, you can follow the methods mentioned above and solve this issue. After fixing the issue, don’t forget creating an image backup with AOMEI Backupper to avoid this issue or similar issue happening again.