• Windows 10 Update Broke Grub2 (UEFI System)


    I had a dualboot setup with windows 10 and antergos on one physical drive. I first installed Windows, disabled fastboot, then later installed antergos. Everything went fine until the recent windows update. Now even the BIOS doesn’t seem to see the Grub entry anymore.

    My efi partition is on /dev/sda2, my windows install on /dev/sda4 and my root directory for antergos is on /dev/sda5. I can boot with the antergos live cd and checked the boot order and got this output:

    [[email protected] ~]$ efibootmgr
    No BootOrder is set; firmware will attempt recovery
    Boot0000  opensuse
    

    I don’t have opensuse installed, never on this particular drive even (on a different drive using the same motherboard and cpu, but everything else is different) so I’m not sure why that shows up but nothing else. When I hit F12 during boot my bios sees this mystery opensuse entry and the windows bootmanager, but Grub is gone.

    when I installed antergos i mounted sda2 as /boot/efi. I’m trying to follow guides for reinstalling grub but with no success so far.

    [[email protected] ~]$ sudo mount /dev/sda5 /mnt
    [[email protected] ~]$ sudo mount /dev/sda2 /mnt/boot/
    [[email protected] ~]$ sudo mount --bind /dev /mnt/dev &&
    > sudo mount --bind /dev/pts /mnt/dev/pts &&
    > sudo mount --bind /proc /mnt/proc &&
    > sudo mount --bind /sys /mnt/sys
    [[email protected] ~]$ sudo chroot /mnt
    [[email protected] /]# pacman -S efibootmgr grub
    [[email protected] /]# grub-install --efi-directory=/boot
    Installing for x86_64-efi platform.
    efibootmgr: EFI variables are not supported on this system.
    efibootmgr: EFI variables are not supported on this system.
    Installation finished. No error reported.
    

    I also tried the following two commands, which also give me error messages:

    [[email protected] /]# os-prober
      /run/lvm/lvmetad.socket: connect failed: No such file or directory
      WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
    grub-probe: error: cannot find a GRUB drive for /dev/sdd1.  Check your device.map.
    [[email protected] /]# update-grub
    Generating grub configuration file ...
      /run/lvm/lvmetad.socket: connect failed: No such file or directory
      WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
    grub-probe: error: cannot find a GRUB drive for /dev/sdd1.  Check your device.map.
    done
    

    Note: /dev/sdd is the antergos live-usb.

  • @Michael-Senter said in Windows 10 Update Broke Grub2 (UEFI System):

    when I installed antergos I mounted sda2 as /boot/efi.

    Then, you should do the same. Do not use /boot but /boot/efi:

    sudo mount /dev/sda5 /mnt
    sudo mount /dev/sda2 /mnt/boot/efi
    ...
    sudo grub-install --efi-directory=/boot/efi
    

    Hope this helps.

  • @karasu That was my first instinct as well, but it gave me the same error message. I also noticed that using this method I get grub in the structure /boot/efi/EFI/ which seemed odd to me.

    [[email protected] ~]$ sudo mount /dev/sda5 /mnt
    [[email protected] ~]$ sudo mount /dev/sda2 /mnt/boot/efi/
    [[email protected] ~]$ sudo mount --bind /dev /mnt/dev
    [[email protected] ~]$ sudo mount --bind /dev/pts /mnt/dev/pts
    [[email protected] ~]$ sudo mount --bind /proc /mnt/proc 
    [[email protected] ~]$ sudo mount --bind /sys /mnt/sys
    [[email protected] ~]$ sudo chroot /mnt
    [[email protected] /]# grub-install --efi-directory=/boot/efi
    Installing for x86_64-efi platform.
    efibootmgr: EFI variables are not supported on this system.
    efibootmgr: EFI variables are not supported on this system.
    Installation finished. No error reported.
    [[email protected] /]# ls /boot/efi/EFI/
    antergos  antergos_grub  Boot  Microsoft
    
  • I can’t really help you here, as I’ve had this happen an innumerable amount of times with Windows 10.
    I fully believe that something in the Windows updates are purposefully screwing up dual boots, because every time I do any sort of windows update (even if it’s not an “upgrade” but just a plain update) it completely breaks the boot sequence when I have a dual boot set up. And most recently, I had to completely reinstall windows too because SOMEHOW it broke its own boot loader in the process and I couldn’t even recover that.

    I hope you can figure out an easy fix to this, but in my experience, completely reinstalling Antergos (or any linux distro) has always seemed to be the easiest fix for me, albeit the most annoying one.

    Hopefully you get a better response than what I have to offer though.

  • I found a solution from Windows that doesn’t require reinstalling antergos. I downloaded EasyUEFI (the free version). Install and start the software. It won’t show grub, so click “Create a new Entry” (second icon from top, middle column). Chose the EFI partition and enter the following path:

    \EFI\antergos_grub\grubx64.efi
    

    in description give it the name you want the firmware to see, such as “grub2” or “grub” or whatever. Hit “OK”. Then use the up-arrow icon to make it the first entry in the bootloading sequence. Reboot and voila - antergos boots.

  • Here is a good solution, Get rid of that crappy Windows 10 and if you must have Windows for some reason or another then use 7!!

uefi34 windows37 grub224 broke12 Posts 6Views 1834
Log in to reply