Specific errors are as follows:
BFSVC Error: Could not open the BCD template store.Status=[c000000f]
In Baidu know to answer the question, encounter a netizen Win10 computer into the system, prompt BCD error.
Reset the BCD, go to troubleshooter, advanced options, command prompt, execute:
The result is no good, prompt system cannot find the specified path. (The problem cannot be restored later, so it cannot be tested)
Execute diskPart and know GPT mode from list disk. Sel disk 0, List Part. Sel Part 1, assign letter Z, assign letter Z, assign letter Z.
The most important step is to make sure the Windows directory is on drive C by switching to Drive C, dir/A. So execute:
bcdboot c:\windows /s z: /f uefi /l zh-cn
Status=[c000000f] BFSVC Error: Could not open the BCD template store.status =[c000000f]
In this case, you can follow it with/V to see the details. At that time, I thought there was a problem with the BCD-Template file.
Because the general system files, WinSXS have relevant backup, so execute:
CD C :\ Windows \ System32 \ Configren BCD-BAK, I can restore CD C :\ Windows \ Winsxscd * bcdTemplate * if necessary. This is the path I found by searching everything on my computer. Because the folder name is too long, I use the wildcard instead. copy bcd-template c:\windows\system32\config
This method may not work on some Win10, because winSXS bCD-Template may not be a registry file, win7 is a registry file, users can also win10 computer.
will not work, if you want to use the bcdboot command to fix it, you can only copy the bcd-template from the config directory on the same system computer to your own computer.
Net friend executes above command while, I also search relevant data on the net.
Some netizens said, bCD-Template is out of order, using SFC to repair, win10 tested SFC does not support to repair the file. Others said that they had the same problem and that they had mixed up \ and/or.
Seeing this, I went back to see the user executed the command, sure enough, “Bcdboot c:/ Windows…” “To” Bcdboot c:\ Windows…” Command executed successfully! After restarting, the system can enter normally.
So, you can’t take these punctuation marks lightly.