![fix grub2 windows 10 fix grub2 windows 10](https://vektorwebsolutions.com/wp-content/uploads/2020/02/windows-10-deleted-grub-886x590-1-1-300x200.jpg)
So the moral of the story is : if you have a clean hard disk and want both Windows & Linux always install Windows first. Another way is booting from a CD disk grub rescue. it means you using scripts on the installed linux as if you had booted that Linux partition. basically you can do this is you chroot the mounted partition linux is on. using a terminal windows from the OS on the usb you are going to have to "evoke" the grub script. One approach is to use linux on a usb something like knoppix you are going to have to boot from usb stick. So its a matter of getting to those grub scripts probably this one $ update-grub Now if everything is there on the linux partition it means all the grub scripts are also there. etc then it means everything is ok,simply that the boot manager has been overwritten. However if Arch is installed in BIOS-GPT in one disk and Windows is installed in BIOS-MBR mode in another disk, then the BIOS bootloader used by Arch CAN boot the Windows in the other disk, if the bootloader itself has the ability to chainload from another disk.So are you saying you installed linux and then windows? if so because Windows has no respect for anything it simply overwrote boot manager that Linux set up The only exceptions to this are grub(2) in Apple Macs in which EFI installed grub(2) can boot BIOS installed OS via appleloader command (does not work in non-Apple systems), and rEFInd which technically supports booting legacy BIOS OS from UEFI systems, but does not always work in non-Apple UEFI systems as per its author Rod Smith.
![fix grub2 windows 10 fix grub2 windows 10](https://i.stack.imgur.com/I91Pj.png)
Similarly if Arch is installed in BIOS-MBR or BIOS-GPT mode in one disk and Windows is installed in UEFI-GPT in another disk, the BIOS bootloader used by Arch cannot chainload UEFI installed Windows in the other disk. That is, if Arch is installed in UEFI-GPT or UEFI-MBR mode in one disk and Windows is installed in BIOS-MBR mode in another disk, the UEFI bootloader used by Arch cannot chainload the BIOS installed Windows in the other disk. Most of the linux bootloaders installed for one firmware type cannot launch or chainload bootloaders of other firmware type. I have attached a screen-shot of my partition table.
#Fix grub2 windows 10 windows 10
Since Windows 10 appears in the grub Menu it seems that grub recognizes Windows but seems to be looking in the wrong place for the Windows boot loader.Ĭan anyone help me in solving this problem? This process is different from restoring the legacy GRUB boot loader on older Linux distributions. You can easily restore GRUB2 from a Ubuntu live CD or USB drive. I have run update-grub but it does not help. If GRUB2 breaksfor example, if you install Windows after installing Ubuntu, or overwrite your MBRyou won’t be able to boot into Ubuntu. As stated previously selecting Windows 10 results in a black screen for a few seconds followed by the re-appearance of the grub menu. Only when Windows 10 is selected is there a problem. After the install completed the grub menu appeared as usual and booted into linux mint 18.3 with no difficulty and everything works properly. When installing I selected "Windows Boot Manager" as the device for installing the Grub boot loader and the installation proceeded normally. I deleted my linux mint 17.3 partitions (/, /home and swap) then installed linux mint 18.2 from a usb live stick. Windows 10 appears on the grub menu but if selected, the screen goes dark for a few seconds the the grub menu re-appears.
![fix grub2 windows 10 fix grub2 windows 10](https://www.howtogeek.com/wp-content/uploads/2017/05/img_590b903de311a.png)
![fix grub2 windows 10 fix grub2 windows 10](https://cdn.windowsreport.com/wp-content/uploads/2019/07/windows-10-deleted-grub-886x590.jpg)
#Fix grub2 windows 10 upgrade
After an upgrade to linux mint 18.3 from linux mint 17.3, I can no longer boot into Windows 10.