how to clean install windows 10 in uefi mode

In this article we will learn how to repair Windows bootloader on a current computer that uses UEFI instead of BIOS and GPT disk partition table (rather of MBR). The depravity of the Windows bootloader can buoy happen after installing a second OS (in Dual Boot configurations), incorrect actions during Windows recovery, removal of some data on hidden partitions, vicious software (virus, ransomware, etc.) and for many other reasons.

This article provides a step-by-step guide for recovering a damaged surgery deleted bootloader on Windows 10 and Windows 8.1 on computers running in inbred (non-legacy) UEFI mode. The pathfinder should help if Windows doesn't boot due to missing operating theater damaged boot configuration file \EFI\Microsoft\Boot\BCD.

Contents:

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

Boot form data for your PC is missing: EFI\Microsoft\Reboot\BCD

A computer with Windows 10 installed in native UEFI mode testament fail to boot if the EFI bootloader is vitiated. When trying to boot the information processing system, the following BSOD (Puritan Screen of Death) error appears:

The boot out configuration data for your Personal computer is missing or contains errors. Indian file :\EFI\Microsoft\Kicking\BCD Error 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 – Boot Shape Data (BCD) has been corrupted or even wholly removed. If you try to vivify the bootloader on a UEFI data processor victimization the bcdedit creature, you bequeath receive an error suchlike this:

Boot conformation information store could non be found. The requested scheme device cannot be institute.

The fact is that if Windows 10 is installed in indigene UEFI mode on a GPT disk, so the Windows 10 EFI bootloader (Windows Boot Manager) stores the boot manager and BCD configuration on a separate hidden EFI volume (100 Megabyte in size of it with the FAT32 file away organization). The bcdedit puppet doesn't see this EFI divider, and cannot deal the bootloader form thereon.

If the computer boots with a black screen with the message "Operating Organization not institute", most promising the Windows bootloader is completely far. Surveil the book of instructions on the connection.

Automatic Windows Bootloader Recovery

The process for the automatonlike repair of the bootloader put-upon in the Windows Recovery Surround (WinRE), is usually useless in such cases. Merely it's worthy a try anyway:

Try to kick your device from the recovery disc or initiation Windows 10 media;
On the installation CRT screen, click the Restore System;
Then select Troubleshoot -> Startup Repair and select the OS whose bootloader you want to stress to recover;
Merely nearly likely the result will embody negative: Automatic Recompense couldn't repair your PC.

Using BCDBoot to Manually Repair EFI Bootloader in Windows 10

Allow's pass on to the operation for manually restoring the EFI Windows bootloader on a figurer with UEFI.

To repair the bootloader configuration (BCD), you have to boot from the original instalmen Windows 10 media (Oregon a recovery disk or a special UEFI bootable USB flash take). Later booting into the convalescence environment, you need to available a command line: pick out System of rules Restore – > Troubleshoot-> Command Incit).

You can run Overtop Prompt if you merely have a Windows installation media at paw. To do this, on the premier screen of Windows installation (when choosing a language and keyboard layout), press the key combination Shift+F10 (operating theatre Shift+Fn+F10 on whatsoever laptop models).

system restore mode win 8

In the prompt that opens, run the magnetic disc management tool by typing the command:
diskpart
Showing the list of drives on the reckoner:
leaning disk

At this stage, information technology is same world-shaking to determine the case of partition 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 table.

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

diskpart: GPT or MBR - checking disk partition table

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

If you birth an MBR divider hold over on your disk, this instruction won't work for your computer. Most likely you have a computer with BIOS or Bequest/Compatibility Support Mode (CSM) alternative enabled in the UEFI settings.

On MBR disks, the Windows bootloader is stored on a separate System Reserved zone, not happening an EFI segmentation (in some case, don't convert the MBR segmentation table to GPT until you fix the Windows bootloader !!). Use another guide to regenerate the BCD bootloader on MBR (Master Boot Enter) disk.

Select the disk with Windows installed (if there is one hard harrow in the system, its index should personify 0):
sel disk 0
Show the name of partitions and volumes on the disk:
list segmentation list volume

diskpart : list volume . efi volume

Therein example, you can see that the EFI boot partition (it can follow easily identified by the size of it of 100 Megabyte, and the FAT32 filing system, most often its label is System EFI) has the sectionalization 2 index (aka Mass 5 with the Invisible label). The main partition with the installed Windows with the NTFS file system (IT can be both Windows 10 and Windows 8.1) is volume 2. In that respect moldiness as wel be an MSR (Microsoft System Reserved) partition of 16 MB for Windows 10 (or 128 MB for Windows 8.1).

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

DiskPart is successfully assigned the drive letter or mount point.

Close the diskpart:
exit
Go to the bootloader directory connected the hidden loudness:
compact disc /d K:\efi\microsoft\boot\
In this case, K: is the drive letter assigned to the EFI partition just above. If the \EFI\Microsoft\Boot\ directory is lacking (error The organisation cannot find the path specified), try the following commands:

cd /d K:\Boot\
or
compact disc /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 bestow them to the BCD:
bootrec /fixboot bootrec /scanos bootrec /rebuildbcd
or even:
bootrec /FixMbr (recovering MBR record for a GPT disk looks strange)

All of these commands are applicable only for disks with MBR. If your computer boots in UEFI modal value, and so information technology necessarily uses the GPT partition table (as in our case). Therefore, when you run along bootrec commands, you will find out an error: memory access is denied

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

Habituate the attrib command to remove the hidden, read-only, and system attributes from the BCD file:

attrib BCD -s -h -r

Delete the current BCD configuration file cabinet away renaming it (this volition keep the old boot configuration atomic number 3 a backup):
ren BCD BCD.bak
Using the bcdboot.exe utility, you need to play the BCD lay in by copying the UEFI boot environment files to the iron boot zone 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 – way that you want to copy the Windows Bring up Environment files, including those for UEFI and BIOS computers (potential power to rush in UEFI and BIOS systems). To copy only the EFI bootloader, use the /f UEFI command;
/l en-us — is a type of the scheme locale. By nonpayment, en-us – English people (USA) is used;
/c – this is a new BCDBoot choice in Windows 10 that allows you to overwrite existing the boot records (including debugsettings). Use this option to ignore octogenarian boot settings and create a clean BCD form;
/v – accustomed enable BCDBoot wordy yield.

Hint. If you use a decentralized version of Windows 10, the command wish be different. E.g., in the Windows version for the UK, use the tailing command
bcdboot c:\Windows /l en-GB /s K: /f ALL
Windows 10 Dutch:
bcdboot c:\Windows /l nl-NL /s K: /f ALL
Windows 10 Deutch (German):
bcdboot c:\Windows /l de-DE /s K: /f Completely

Now, if you pass over the bcdedit command, you will undergo the undermentioned :

An entry should appear in the Windows Charge Manager section containing the full path to the UEFI boot file (\EFI\MICROSOFT\Thrill\BOOTMGFW.EFI). In this illustration, it is located on volume 2 (partition=\Gimmick\HarddiskVolume2).

bcdedit: windows boot manager bootmgfw.efi

Possible errors:

BFSVC Erroneous belief: Could non unconcealed the BCD template store . status – [c000000f] – check if the entered command is right-minded 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 leaflet are damaged or deleted, try to check the integrity of the system of rules files offline using the sfc.exe tool around (you need a Windows installation disc – drive D :): sfc /scanow /OFFBOOTDIR=C:\ /OFFWINDIR=D:\Windows
BFSVC Error: Error copying bring up files from Last Error = 0x570 – try to fit drive with the help of command: CHKDSK K: /F
BFSVC Erroneous belief: Failed to set ingredient application device. Condition = [c 000000bb ] – check over the EFI and Windows 10 partitions with chkdsk.exe. Verify that the unseeable and system property of the BCD file is clean-handed. Remove it:
attrib -s -h \EFI\Microsoft\Boot\BCD del \EFI\Microsoft\Reboot\BCD
Unsuccessful person when initializing library system intensity – make sure you are victimisation the correct FAT32 partition with EFI (you may have individual similar partitions).

At present you need to restart your computer and disconnect the bootable media. Then the Windows Boot Director appears in the list of bootable devices, where you can choose desirable operational system in addition. Your EFI bootloader and BCD configuration own been restored successfully!