GRUB Bootloader Missing After Dual Boot or Update
Your PC boots straight to Windows or a black screen after installing Linux. The GRUB menu is gone. Here's how to get it back fast.
So you rebooted after setting up dual boot, and instead of the GRUB menu you get Windows, or a black screen with 'grub rescue>' staring back at you. I know this is annoying. I've been there myself — after a BIOS update, Windows pushed an update that wiped my GRUB clean. Don't panic. The fix is straightforward.
This article covers the three most common reasons GRUB disappears. Start with #1, it works 80% of the time. If not, move to #2, then #3. I'll give you exact commands, no fluff.
1. Windows Overwrote the Bootloader (Most Common)
This happens after Windows updates, especially the big ones like Windows 10 version 22H2 or Windows 11 2023 Update. Windows rewrites the EFI boot entries, and GRUB is kicked out. You still have Ubuntu (or your Linux distro) installed — it's just hidden.
The fastest fix: Boot-Repair
Boot from your Linux live USB (the one you used to install). Choose "Try Ubuntu" or "Try Linux Mint" — don't install again. Then:
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt update
sudo apt install boot-repair
boot-repair
Click "Recommended repair". It will scan your system, reinstall GRUB, and set the right EFI boot entry. Takes about 2 minutes. Reboot, and you should see GRUB again.
When this doesn't work: If you see a "Secure Boot" error, go into your BIOS and disable Secure Boot. Some motherboards (like ASUS B450 and Gigabyte Z490) are picky about this. Also check if your boot mode is UEFI, not Legacy. Most modern installs use UEFI.
2. You Moved or Deleted the Linux Partition
Maybe you shrunk your Ubuntu partition to free up space, or deleted a partition that held /boot. GRUB can't find the kernel files and drops to a rescue shell. You'll see something like:
grub rescue> _
Manual fix: Reinstall GRUB via chroot
Boot from the live USB again. Open a terminal. First find your Linux partitions:
sudo fdisk -l
Look for your root partition — it's usually ext4, around 20-50GB. For example /dev/sda2. If you have a separate boot partition (like /dev/sda1), note that too.
Mount everything:
sudo mount /dev/sda2 /mnt
sudo mount /dev/sda1 /mnt/boot # skip if you don't have separate boot partition
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
For UEFI systems (most common now), also mount the EFI partition:
sudo mount /dev/sda3 /mnt/boot/efi # adjust partition number
Then chroot in and reinstall GRUB:
sudo chroot /mnt
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB --recheck
update-grub
update-initramfs -u
reboot
If you're on an older BIOS system (not UEFI), skip the EFI part and just run:
grub-install /dev/sda
Real-world example: A friend tried to dual-boot on a Dell XPS 15 and accidentally deleted the boot partition while resizing. This chroot method brought GRUB back in under 5 minutes.
3. Corrupted GRUB Configuration File
Less common, but it happens. Maybe a bad package update, or you edited /etc/default/grub and made a typo. The result: your system hangs at boot with a blinking cursor, or shows a minimal GRUB command line.
Fix: Regenerate grub.cfg manually
Boot from live USB, mount your root partition as shown in #2, chroot, then:
sudo chroot /mnt
nano /etc/default/grub
Check for obvious typos — missing quotes, wrong timeout value, or a typo in GRUB_CMDLINE_LINUX. A common mistake: GRUB_TIMEOUT=0 which hides the menu instantly. Change it to GRUB_TIMEOUT=10 to get the menu back.
After fixing the config, regenerate the bootloader:
update-grub
reboot
Note: If you can't even get to the GRUB command line, skip this fix — go back to #1 or #2.
Quick-Reference Summary Table
| Cause | Symptom | Fix | Time |
|---|---|---|---|
| Windows update overwrote EFI | Boots straight to Windows | Boot-Repair from live USB | 5 min |
| Deleted/moved Linux partition | GRUB rescue prompt | Reinstall GRUB via chroot | 10 min |
| Corrupted GRUB config | Black screen or minimal GRUB | Regenerate grub.cfg | 5 min |
One last thing: if you're on a newer system with Windows 11 and Secure Boot, you might need to add GRUB as a trusted UEFI application. Boot-Repair does this automatically, but if you're doing it manually, run mokutil --disable-validation after chrooting. I've seen that trip up people on ThinkPad X1 Carbons.
That's it. You should have your dual boot menu back. If not, check the forums for your specific hardware — some Dell and HP laptops need a BIOS setting tweak too. But for 95% of cases, one of these three fixes will work.
Was this solution helpful?