Windows boot configuration data store




















Step 5. After repairing, restart your computer. With this article, you can get simple and safe ways to fix the Boot Configuration Data file missing in Windows Some information required error in Windows 10 and other similar BCD errors.

But you are not always able to repair various boot failure. Thus, it is recommended you to back up system in advance. Way 1. Detailed steps are given below Take Windows 10 installation disc as an example : 1. Insert the Windows 10 installation disc into your computer and boot from it.

Wait patiently for your OS to be repaired. Way 2. If you enter " bcdedit " at a simple Command Prompt window, you'll probably see:. The following is what you would typically see when entering the command bcdedit all by itself:. Note that the Boot Manager program bootmgr is often located in a volume without a drive letter, such as in this example, but it could have one. If there were only one partition on the drive, then it would appear in the C: partition. And if there really was only one, then the word "control" should have had an 's' after it!

This was still true for a Windows 7 SP1 install we examined, and even Windows 8. Is this a case of "If it ain't broke, don't fix it! Apparently, the cost of qualifying a revised program outweighs this grammatical error.

Now it's incorrect for both of the last two command types:. After examining this backup file in our Documents folder using HxD , our first reaction was: "Man, this thing appears to be full of all kinds of needless 'gunk'! So, the 'backup copy' is not really a true copy. And the differences go well beyond simply changing the path name of its location. So why is this file so 'cluttered' compared to the Windows XP boot.

Its first 4 bytes are a big clue: " regf ". DAT file begins with the same 4 bytes. To test this, we used a disk editor to alter the bytes at offsets 0x 1B8 through 0x 1BB in the MBR first sector of the disk drive by simply adding 1 to each byte. In previous Windows versions, the OS would still boot up this way; even though there was the possibility some program that used the Disk Signature could then have problems.

Note: The same error message, with Status: code of 0x ce , will also be displayed if we change those NT Sig. Only if you edit these bytes back to their original values will the PC boot-up again. It's also possible to see such an error if your PC is somehow directed to start booting from a drive other than the normal boot drive, and the BCD Store on that drive points to the first drive, which will obviously contain a different Disk Sig.

How can I fix this? This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. In order to provide you with a quick resolution, please reply to these questions: 1. If you need further assistance, please reply and we will be happy to help you.



0コメント

  • 1000 / 1000