What Needs To Be Repaired When A 2013 Gmc Terrain Reads Error Code P0603

In this article we volition larn how to repair Windows bootloader on a modern computer that uses UEFI instead of BIOS and GPT deejay partition table (instead of MBR). The corruption of the Windows bootloader can occur afterwards installing a second Os (in Dual Boot configurations), incorrect actions during Windows recovery, removal of some data on hidden partitions, malicious software (virus, ransomware, etc.) and for another reasons.

This article provides a pace-by-step guide for recovering a damaged or deleted bootloader on Windows 10 and Windows 8.1 on computers running in native (not-legacy) UEFI way. The guide should help if Windows doesn't kicking due to missing or damaged kick configuration file \EFI\Microsoft\Boot\BCD.

Contents:

The boot configuration information for your PC is missing: EFI\Microsoft\Boot\BCD
Automatic Windows Bootloader Recovery
Using BCDBoot to Manually Repair EFI Bootloader in Windows 10

The kicking configuration data for your PC is missing: EFI\Microsoft\Boot\BCD

A computer with Windows ten installed in native UEFI mode will neglect to kicking if the EFI bootloader is corrupted. When trying to kick the computer, the following BSOD (Blueish Screen of Death) error appears:

The kicking configuration data for your PC is missing or contains errors. File :\EFI\Microsoft\Boot\BCD Fault code: 0xc000000f

or:

Error code: 0xc000014c

$boot configuration errors 0xc000000f or missing file \EFI\Microsoft\Boot\BCD$

This error indicates that the Windows bootloader configuration – Kick Configuration Data (BCD) has been corrupted or even completely removed. If you try to repair the bootloader on a UEFI figurer using the bcdedit tool, you lot will receive an fault like this:

The boot configuration data store could not be found. The requested organization device cannot be found.

The fact is that if Windows x is installed in native UEFI mode on a GPT disk, and then the Windows 10 EFI bootloader (Windows Boot Manager) stores the boot managing director and BCD configuration on a separate subconscious EFI book (100 MB in size with the FAT32 file system). The bcdedit tool doesn't see this EFI sectionalization, and cannot manage the bootloader configuration on it.

If the calculator boots with a blackness screen with the message "Operating System not found", near likely the Windows bootloader is completely removed. Follow the instructions on the link.

Automatic Windows Bootloader Recovery

The procedure for the automatic repair of the bootloader used in the Windows Recovery Environment (WinRE), is usually useless in such cases. Simply information technology'due south worth a endeavour anyway:

Endeavour to boot your device from the recovery disc or installation Windows 10 media;
On the installation screen, click the Restore System;
Then select Troubleshoot -> Startup Repair and select the OS whose bootloader you want to attempt to recover;
Merely almost likely the upshot volition be negative: Automatic Repair couldn't repair your PC.

Using BCDBoot to Manually Repair EFI Bootloader in Windows 10

Let's movement on to the process for manually restoring the EFI Windows bootloader on a computer with UEFI.

To repair the bootloader configuration (BCD), you have to kicking from the original installation Windows x media (or a recovery disk or a special UEFI bootable USB flash drive). After booting into the recovery environment, yous demand to open up a command line: select System Restore – > Troubleshoot-> Command Prompt).

You can run Command Prompt if you only have a Windows installation media at manus. To practise this, on the beginning screen of Windows installation (when choosing a linguistic communication and keyboard layout), press the cardinal combination Shift+F10 (or Shift+Fn+F10 on some laptop models).

system restore mode win 8

In the command prompt that opens, run the disk management tool by typing the command:
diskpart
Display the listing of drives on the figurer:
list deejay

At this stage, it is very of import to determine the type of segmentation table on the disk on which Windows is installed: MBR or GPT. The point is that the EFI bootloader is used only on disks with a GPT partition tabular array.

If the disk has an asterisk (*) in the Gpt column, then the GPT partition table is used, if non, the MBR is used.

diskpart: GPT or MBR - checking disk partition table

If your disk uses a GPT partition table, follow the steps below in the instructions to repair the Windows EFI bootloader.

If you lot take an MBR segmentation tabular array on your deejay, this education won't work for your computer. Most likely you lot have a computer with BIOS or Legacy/Compatibility Back up Fashion (CSM) choice enabled in the UEFI settings.

On MBR disks, the Windows bootloader is stored on a separate System Reserved partition, not on an EFI partition (in any case, don't catechumen the MBR sectionalization tabular array to GPT until you fix the Windows bootloader !!). Use another guide to restore the BCD bootloader on MBR (Master Boot Tape) disk.

Select the deejay with Windows installed (if there is ane hard disk in the system, its alphabetize should be 0):
sel disk 0
Brandish the list of partitions and volumes on the disk:
list partitioning list volume

diskpart : list volume . efi volume

In this example, you can meet that the EFI boot partition (it can exist easily identified by the size of 100 MB, and the FAT32 file system, most oft its label is Organisation EFI) has the partitioning ii index (aka Volume 5 with the Hidden label). The main sectionalisation with the installed Windows with the NTFS file arrangement (it tin can be both Windows ten and Windows eight.1) is volume 2. At that place must also exist an MSR (Microsoft System Reserved) partition of 16 MB for Windows x (or 128 MB for Windows eight.1).

Assign the drive letter of the alphabet K: to the hidden EFI volume:
select book 1
assign letter K:
A message that the drive letter of the alphabet has been successfully to the EFI partition should appear:

DiskPart is successfully assigned the drive letter or mount signal.

Close the diskpart:
get out
Go to the bootloader directory on the hidden volume:
cd /d Thou:\efi\microsoft\boot\
In this case, K: is the drive letter assigned to the EFI division only above. If the \EFI\Microsoft\Kicking\ directory is missing (error The organization cannot detect the path specified), try the post-obit commands:

cd /d Thou:\Kicking\
or
cd /d K:\ESD\Windows\EFI\Microsoft\Kicking\

At this point, many guides recommend running the following commands, which should overwrite the partition boot record, find the installed Windows and add them to the BCD:
bootrec /fixboot bootrec /scanos bootrec /rebuildbcd
or even:
bootrec /FixMbr (recovering MBR tape for a GPT disk looks strange)

All of these commands are applicable simply for disks with MBR. If your computer boots in UEFI manner, then it necessarily uses the GPT sectionalization table (as in our example). Therefore, when you run bootrec commands, you will see an error: admission is denied

To fix boot records on an EFI partition, y'all need to utilise the BCDBoot tool. The BCDBoot tools allows you to restore bootloader files on the system partitioning by copying them from the organization directory on the Windows sectionalization. The BCD bootloader configuration is recreated using the %WINDIR%\System32\Config\BCD-Template file.

Apply the attrib control to remove the hidden, read-merely, and system attributes from the BCD file:

attrib BCD -s -h -r

Delete the current BCD configuration file past renaming it (this will keep the old boot configuration every bit a fill-in):
ren BCD BCD.bak
Using the bcdboot.exe utility, you need to recreate the BCD store by copying the UEFI boot environment files to the boot partition from the Windows directory:
bcdboot C:\Windows /50 en-the states /s k: /f ALL

C:\Windows – is the path to the directory with Windows 10 installed;
/f ALL – means that y'all desire to copy the Windows Boot Environment files, including those for UEFI and BIOS computers (potential ability to boot in UEFI and BIOS systems). To re-create only the EFI bootloader, utilize the /f UEFI control;
/l en-usa — is a type of the system locale. By default, en-u.s.a. – English (USA) is used;
/c – this is a new BCDBoot option in Windows 10 that allows you lot to overwrite existing boot records (including debugsettings). Utilize this pick to ignore sometime boot settings and create a clean BCD configuration;
/v – used to enable BCDBoot verbose output.

Hint. If you use a localized version of Windows 10, the command will be different. For example, in the Windows version for the Great britain, use the following command
bcdboot c:\Windows /50 en-uk /south K: /f ALL
Windows 10 Dutch:
bcdboot c:\Windows /l nl-NL /due south K: /f ALL
Windows 10 Deutch (German):
bcdboot c:\Windows /l de-DE /due south Thou: /f ALL

At present, if you run the bcdedit command, you will run across the following :

An entry should appear in the Windows Boot Manager section containing the full path to the UEFI boot file (\EFI\MICROSOFT\Kick\BOOTMGFW.EFI). In this example, it is located on book 2 (partition=\Device\HarddiskVolume2).

bcdedit: windows boot manager bootmgfw.efi

Possible errors:

BFSVC Error: Could non open up the BCD template shop . status – [c000000f] – check if the entered command is correct and whether you take a localized Windows version installed. In this case you need specify the correct local language code. The bcdboot tool copies the BCD template files from the \Windows\System32\Config directory. If the BCD templates in this folder are damaged or deleted, try to cheque the integrity of the arrangement files offline using the sfc.exe tool (you need a Windows installation disc – bulldoze D :): sfc /scanow /OFFBOOTDIR=C:\ /OFFWINDIR=D:\WINDOWS
BFSVC Error: Error copying boot files from Last Fault = 0x570 – try to check bulldoze with the help of command: CHKDSK K: /F
BFSVC Error: Failed to set element application device. Status = [c 000000bb ] – check the EFI and Windows 10 partitions with chkdsk.exe. Verify that the subconscious and system attribute of the BCD file is cleared. Remove it:
attrib -south -h \EFI\Microsoft\Kick\BCD del \EFI\Microsoft\Boot\BCD
Failure when initializing library arrangement volume – make sure you are using the correct FAT32 partition with EFI (y'all may have several similar partitions).

Now you need to restart your computer and disconnect the bootable media. And then the Windows Boot Manager appears in the list of bootable devices, where y'all tin choose desired operating system to boot. Your EFI bootloader and BCD configuration have been restored successfully!