How To Repair A Window With The Rubber Seal Rising

In this commodity we will acquire how to repair Windows bootloader on a modern computer that uses UEFI instead of BIOS and GPT disk segmentation table (instead of MBR). The corruption of the Windows bootloader tin can occur after installing a 2nd Bone (in Dual Kicking configurations), incorrect actions during Windows recovery, removal of some data on subconscious partitions, malicious software (virus, ransomware, etc.) and for some other reasons.

This article provides a step-past-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 boot due to missing or damaged boot configuration file \EFI\Microsoft\Kicking\BCD.

Contents:

• The boot configuration data 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 estimator with Windows 10 installed in native UEFI mode volition fail to kicking if the EFI bootloader is corrupted. When trying to boot the reckoner, the following BSOD (Blue Screen of Death) error appears:

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

or:

Mistake code: 0xc000014c

This error indicates that the Windows bootloader configuration – Boot Configuration Information (BCD) has been corrupted or even completely removed. If you try to repair the bootloader on a UEFI estimator using the bcdedit tool, y'all will receive an fault similar this:

The boot configuration data store could non exist institute. The requested system device cannot be constitute.

The fact is that if Windows 10 is installed in native UEFI style on a GPT disk, then the Windows 10 EFI bootloader (Windows Kick Director) stores the boot manager and BCD configuration on a separate subconscious EFI volume (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 computer boots with a black screen with the bulletin "Operating System non found", most probable 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 Surround (WinRE), is usually useless in such cases. But information technology's worth a try anyway:

1. Attempt to kick your device from the recovery disc or installation Windows ten media;
2. On the installation screen, click the Restore System;
3. And so select Troubleshoot -> Startup Repair and select the Bone whose bootloader y'all want to try to recover;
4. But almost probable the result volition exist negative: Automatic Repair couldn't repair your PC.

Using BCDBoot to Manually Repair EFI Bootloader in Windows 10

Permit's motion on to the procedure for manually restoring the EFI Windows bootloader on a estimator with UEFI.

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

You tin can run Control Prompt if you only have a Windows installation media at hand. To do this, on the first screen of Windows installation (when choosing a linguistic communication and keyboard layout), press the key combination Shift+F10 (or Shift+Fn+F10 on some laptop models).

In the command prompt that opens, run the deejay management tool past typing the control:
diskpart
Display the list of drives on the reckoner:
list disk

At this stage, information technology is very important to determine the blazon of sectionalisation table on the disk on which Windows is installed: MBR or GPT. The betoken is that the EFI bootloader is used only on disks with a GPT partitioning table.

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

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

If you have an MBR partition table on your disk, this instruction won't work for your computer. Nigh likely you lot have a computer with BIOS or Legacy/Compatibility Support Fashion (CSM) option enabled in the UEFI settings.

On MBR disks, the Windows bootloader is stored on a separate Arrangement Reserved partition, non on an EFI partition (in any case, don't convert the MBR sectionalisation table to GPT until you fix the Windows bootloader !!). Use another guide to restore the BCD bootloader on MBR (Primary Boot Record) disk.

Select the disk with Windows installed (if there is one hard disk in the arrangement, its index should exist 0):
sel disk 0
Brandish the listing of partitions and volumes on the disk:
list partition
list volume

In this example, yous can see that the EFI kick partition (information technology can be easily identified by the size of 100 MB, and the FAT32 file system, almost often its label is System EFI) has the partitioning 2 index (aka Book 5 with the Hidden label). The main partition with the installed Windows with the NTFS file system (information technology can be both Windows 10 and Windows viii.one) is book ii. In that location must also be an MSR (Microsoft Arrangement Reserved) partitioning of xvi MB for Windows 10 (or 128 MB for Windows 8.one).

Assign the drive letter One thousand: to the hidden EFI volume:
select volume one
assign letter of the alphabet Yard:
A message that the drive letter has been successfully to the EFI partition should appear:

DiskPart is successfully assigned the bulldoze alphabetic character or mount point.

Shut the diskpart:
get out
Go to the bootloader directory on the hidden volume:
cd /d K:\efi\microsoft\boot\
In this instance, M: is the drive letter of the alphabet assigned to the EFI partition just above. If the \EFI\Microsoft\Boot\ directory is missing (fault The organization cannot find the path specified), try the following commands:

cd /d Chiliad:\Kick\
or
cd /d K:\ESD\Windows\EFI\Microsoft\Boot\

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 fifty-fifty:
bootrec /FixMbr (recovering MBR tape for a GPT disk looks strange)

All of these commands are applicable only for disks with MBR. If your calculator boots in UEFI mode, then it necessarily uses the GPT partition table (as in our case). Therefore, when you run bootrec commands, you will see an error: access is denied

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

Use the attrib control to remove the hidden, read-only, and organisation attributes from the BCD file:

attrib BCD -due south -h -r

Delete the current BCD configuration file by renaming it (this will proceed the one-time boot configuration every bit a backup):
ren BCD BCD.bak
Using the bcdboot.exe utility, y'all need to recreate the BCD shop by copying the UEFI boot environment files to the boot partition from the Windows directory:
bcdboot C:\Windows /l en-us /s k: /f ALL

• C:\Windows – is the path to the directory with Windows 10 installed;
• /f ALL – means that yous want to re-create the Windows Boot Environment files, including those for UEFI and BIOS computers (potential ability to kick in UEFI and BIOS systems). To re-create only the EFI bootloader, use the /f UEFI command;
• /l en-us — is a type of the arrangement locale. Past default, en-us – English language (Us) is used;
• /c – this is a new BCDBoot selection in Windows 10 that allows you to overwrite existing kicking records (including debugsettings). Utilize this pick to ignore old kicking settings and create a make clean BCD configuration;
• /v – used to enable BCDBoot verbose output.

Hint. If you utilise a localized version of Windows 10, the command volition be different. For example, in the Windows version for the UK, use the following command
bcdboot c:\Windows /50 en-britain /s Yard: /f ALL
Windows ten Dutch:
bcdboot c:\Windows /l nl-NL /s Chiliad: /f ALL
Windows 10 Deutch (German):
bcdboot c:\Windows /l de-DE /s K: /f ALL

At present, if you lot run the bcdedit control, you volition see the post-obit :

An entry should announced in the Windows Boot Manager section containing the full path to the UEFI kick file (\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI). In this example, information technology is located on volume 2 (partition=\Device\HarddiskVolume2).

Possible errors:

• BFSVC Mistake: Could not open the BCD template store . condition – [c000000f] – bank check if the entered command is right and whether you have 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 binder are damaged or deleted, try to check the integrity of the system files offline using the sfc.exe tool (you need a Windows installation disc – drive D :): sfc /scanow /OFFBOOTDIR=C:\ /OFFWINDIR=D:\WINDOWS
• BFSVC Error: Fault copying kicking files from Concluding Error = 0x570 – endeavour to check drive with the assistance of command: CHKDSK Yard: /F
• BFSVC Error: Failed to set chemical element application device. Status = [c 000000bb ] – check the EFI and Windows 10 partitions with chkdsk.exe. Verify that the hidden and arrangement aspect of the BCD file is cleared. Remove information technology:
  attrib -southward -h \EFI\Microsoft\Boot\BCD
del \EFI\Microsoft\Kick\BCD
  
• Failure when initializing library system volume – brand certain y'all are using the correct FAT32 segmentation with EFI (y'all may accept several like partitions).

Now you need to restart your computer and disconnect the bootable media. Then the Windows Boot Manager appears in the list of bootable devices, where yous can cull desired operating system to boot. Your EFI bootloader and BCD configuration have been restored successfully!

Source: http://woshub.com/how-to-repair-uefi-bootloader-in-windows-8/

Posted by: mccrayearre1983.blogspot.com

Share this post