after I've got the following error message at startup, I've tried the link below to fix my problems:
The Boot Configuration Data files is missing some required information
File: \BCD
Error code: 0xc000000d
It worked flawlessly but since then, whenever I recover my laptop from hibernation I get the old DOS-like Bitlocker Screen.
I know it's not a real problem, as evrything is working fine, but deep down in me I really dislike the DOS Screen.
So far I tried the following (obviously) without success:
Does anyone of you have a solution for me? It would be very helpful.
And please excuse my not perfect English, it's not my native language.
Thank you!
For GPT Rebuild BCD Restart Your System Windows 10 Installation Media.
Select the language - Next Go To Repair Your Computer
Troubleshoot → Advanced options → Command Prompt
Choose Command Prompt from the menu
Run the command : diskpart
Run the command : sel disk 0
Run the command : list vol
Verify that the EFI partition is using the FAT32 file system and assign a drive letter to it
Run the command :sel vol <number of volume>
Run the command :assign letter=<drive letter>:
Run the command:exit
In order to repair the boot record :
Run the command : cd /d <drive letter>:\EFI\Microsoft\Boot\
Run the command : bootrec /FixBoot
Rebuild the BCD store
First run the command below to backup the old BCD : ren BCD BCD.old
Now recreate it using this command: bcdboot c:\Windows /l en-us /s <boot letter>: All
Please remember that the <boot letter>
is replaced with whatever the letter of the drive you are booting from is.
that is C:\, D:\
Microsoft has warned in the past that you must disable Hibernation mode before utilizing Bitlocker encryption. Bitlocker functions with it, but it's not an ideal practice and Windows boots so quickly now that hibernation is unnecessary, particularly if you're security minded.
Turn off hibernation mode, in power settings, or in group policy. Then follow the steps listed above. If that still fails, I would decrypt, reinitialize the TPM, and encrypt again. If that fails again, I would do a clean install of Windows and give it another shot.
User contributions licensed under CC BY-SA 3.0