F5F Stay Refreshed Software Operating Systems Windows 10 error code BCD indicates a specific technical issue.

Windows 10 error code BCD indicates a specific technical issue.

Windows 10 error code BCD indicates a specific technical issue.

Pages (3): Previous 1 2 3 Next
S
SillyDragon
Senior Member
586
02-06-2016, 10:01 AM
#11
I attempted it and it shows a BFSVC issue: failed to verify boot manager checksum (C:\Windows\boot\EFI\bootmgfw.efi). Error code? oxc1.
S
SillyDragon
02-06-2016, 10:01 AM #11

I attempted it and it shows a BFSVC issue: failed to verify boot manager checksum (C:\Windows\boot\EFI\bootmgfw.efi). Error code? oxc1.

E
ExtremeDragonK
Junior Member
44
02-11-2016, 12:44 PM
#12
Initiate a BIOS reset to restore defaults and reboot automatically if a command-line error appears. Use regedit to repair any corrupted registry entries or replace damaged files with a fresh copy from the live disc you possess. If you receive a command prompt message and access your disk drive, navigate to the Windows folder, type win.exe or explorer.exe, and verify they start correctly.
E
ExtremeDragonK
02-11-2016, 12:44 PM #12

Initiate a BIOS reset to restore defaults and reboot automatically if a command-line error appears. Use regedit to repair any corrupted registry entries or replace damaged files with a fresh copy from the live disc you possess. If you receive a command prompt message and access your disk drive, navigate to the Windows folder, type win.exe or explorer.exe, and verify they start correctly.

M
Mandi_64
Member
202
02-15-2016, 07:07 AM
#13
I’m not sure if I got the details right, but I reset the BIOS and reboot still shows an error. The only way to check is using a Windows 10 setup (which I do). You’re asking about which file to copy if there’s a bad file—what file should be used?
M
Mandi_64
02-15-2016, 07:07 AM #13

I’m not sure if I got the details right, but I reset the BIOS and reboot still shows an error. The only way to check is using a Windows 10 setup (which I do). You’re asking about which file to copy if there’s a bad file—what file should be used?

P
PerkyPup0217
Junior Member
15
02-15-2016, 09:25 PM
#14
If you encounter an error screen, note the number and search online for "bad file." Locate a copy of the file and transfer it from the source to your D: drive using the path d:/copy d:/folders/filename. Save it at c:/folderspotneeded/filename.
P
PerkyPup0217
02-15-2016, 09:25 PM #14

If you encounter an error screen, note the number and search online for "bad file." Locate a copy of the file and transfer it from the source to your D: drive using the path d:/copy d:/folders/filename. Save it at c:/folderspotneeded/filename.

X
XxTRoOoJNxX
Junior Member
3
02-17-2016, 04:06 AM
#15
It seems there may be issues with the file. Use the command in the installation prompt to try copying the required files. Then continue from your earlier message.
X
XxTRoOoJNxX
02-17-2016, 04:06 AM #15

It seems there may be issues with the file. Use the command in the installation prompt to try copying the required files. Then continue from your earlier message.

C
Connecticut
Junior Member
47
02-17-2016, 11:56 AM
#16
It doesn’t locate the directory for copying. When you navigate to C:\Windows\boot\EFI, it can’t find it. The system is currently in EFI mode, which may affect operations. Copying the EFI folder from the installation environment is generally safe if done correctly.
C
Connecticut
02-17-2016, 11:56 AM #16

It doesn’t locate the directory for copying. When you navigate to C:\Windows\boot\EFI, it can’t find it. The system is currently in EFI mode, which may affect operations. Copying the EFI folder from the installation environment is generally safe if done correctly.

J
JynxHype
Member
67
02-17-2016, 08:18 PM
#17
The setup environment might have altered the drive letters. Check DiskPart to view the assigned volume letter for your Windows drive. This should be acceptable as a final option.
J
JynxHype
02-17-2016, 08:18 PM #17

The setup environment might have altered the drive letters. Check DiskPart to view the assigned volume letter for your Windows drive. This should be acceptable as a final option.

N
Nicke456
Junior Member
44
02-19-2016, 03:32 AM
#18
I checked how it works when I run cd or dir, but I don’t see an EFI folder in c:\windows\boot.
N
Nicke456
02-19-2016, 03:32 AM #18

I checked how it works when I run cd or dir, but I don’t see an EFI folder in c:\windows\boot.

M
maskeddeath85
Member
168
02-27-2016, 02:49 AM
#19
The path you provided doesn't match any known locations. It seems your system might be older. If you follow the steps in my initial message—after completing prior actions and adjusting the command—you should see "Boot files successfully created." You can then configure UEFI settings, disable Secure Boot, and enable legacy boot if needed. This usually restores compatibility with older systems.
M
maskeddeath85
02-27-2016, 02:49 AM #19

The path you provided doesn't match any known locations. It seems your system might be older. If you follow the steps in my initial message—after completing prior actions and adjusting the command—you should see "Boot files successfully created." You can then configure UEFI settings, disable Secure Boot, and enable legacy boot if needed. This usually restores compatibility with older systems.

M
Manas_
Member
57
02-27-2016, 03:21 AM
#20
The system reports an error indicating it couldn't set the element's application device. The status code is c00000bb. You've already attempted this in legacy mode and restored to defaults, but it still doesn't work. There are many options available; however, you mentioned disliking laptops.
M
Manas_
02-27-2016, 03:21 AM #20

The system reports an error indicating it couldn't set the element's application device. The status code is c00000bb. You've already attempted this in legacy mode and restored to defaults, but it still doesn't work. There are many options available; however, you mentioned disliking laptops.

Pages (3): Previous 1 2 3 Next