Grub deleted after Windows update

I had dual booted Garuda with windows 10, giving 50GB HDD to the former. I had used up 40 GB / 50 GB of the user space. Today Windows forced an update due to which i cannot enter grub anymore, whenever it tries to enter GRUB it throws filesystem err and enter into GRUB rescue mode. Fortunately i can somehow boot up Windows.
Now whenever i boot using a live USB i can see that the 40GB used space of Garuda is still there unharmed, but i cannot boot the thing up. Any way i can get into my earlier Garuda without wiping the partition away?
Your suggestions will surely help me!!



First of all, it could be that Windows simply set itself as default boot, and this could be checked from your live USB entering in a terminal efibootmgr. You should see the Windows entry as first, and then the Garuda one. The order can be changed with e.g.

sudo efibootmgr -o 0002,2001,2002,2003,0000

The sequence you can take from the first efibootmgr check and change as needed.
If Garuda is not shown at all, you'll have to reinstall the bootloader and update the grub.
To do that, you could follow this guide:


Reinstall Grub. Looks like someone had to do it here:


You could also look to see if Windows played with the BIOS settings, such as Fast Boot - and many BIOS allow you to select which NVRAM entry has control of booting (thus skipping the efibootmgr access requirement). Might be easier :grin:




I decided to install Garuda on a new drive, not beside Windows. I use BIOS-/UEFI-boot selector to choose which to boot. So they cannot mix.

In my mind, the best way to "Dual Boot". Highly recommended.


I think you've had enough suggestions to resolve your issue now. This has all been covered on the forum before and if you are unaware this is precisely why Garuda does not officially support multi-booting.

If you wish to multi-boot, you are expected to be capable of managing how to sort the problems it creates yourself. Otherwise, perhaps like skydiving you should figure out the pitfalls first before taking the leap.

Windows will do this sometimes. You need to figure out how to resolve this yourself, or perhaps you shouldn't have installed a dual boot without doing your research first.