Also note that the following steps should not affect an EFI GRUB install as long as you do not otherwise delete GRUB's existing directory on the ESP.įinally, write the new bootloader to the partition with bcdboot C:\windows /s N: /f UEFI. Especially do not do this if you have a Linux distro on another partition or else you'll have to reinstall GRUB as well once you're done with this.
This is probably not necessary under normal circumstances, however, as bcdboot seems to do a good job of cleaning things up itself. (Optional) If you are not currently dual booting and want to fully clean the ESP before writing a new bootloader, run format N: /FS:FAT32 to reformat it as FAT32. Run list volume again and note that the ESP is now assigned a driver letter. Now do select volume x (where x is the volume number for the ESP) and then assign letter=N: to mount the partition. Note the volume number for your EFI system partition (ESP). When prompted, choose "Repair your computer", followed by "Troubleshoot", "Advanced Options", and finally "Command Prompt". Grab the Media Creation Tool, make yourself a Windows 10 installation DVD or USB drive, and then boot into it. There's unfortunately almost no up-to-date guides on fixing the UEFI Windows Boot Manager (almost all of them just say to run the graphical Startup Repair utility, but that doesn't fix the problem in all cases), but I finally found the correct solution buried in this article, which requires the use of the bcdboot command instead: The other answers given here work great on MBR/BIOS systems, however if you're on a UEFI system like I am, bootsect will just write a semi-functional boot MBR over the GPT protective MBR and bootrec just gives an "Access denied" error message, and neither one has a functional option to fix a broken EFI system partition, which on a UEFI/GPT drive is what contains the bootloader that used to be stored in the MBR.
0 kommentar(er)
