To restore Windows 7 in the GRUB bootloader, you must repair the EFI System Partition (ESP) and regenerate the grub.cfg configuration file. This process involves mounting the ESP, ensuring the correct bootloaders are present for both Linux and Windows, and running update-grub or grub-mkconfig to detect the existing Windows installation.
Understanding the EFI Structure
The Extensible Firmware Interface (EFI) system partition is a critical component of modern UEFI-based computers. It typically resides on a small FAT32-formatted partition, often labeled as "EFI" or "System." This partition holds the bootloader files necessary for starting the operating system. When dual-booting Linux and Windows 7, both operating systems place their respective bootloaders within this shared space.
Windows 7 places its bootloader in the root directory of the EFI partition, usually at /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi. Linux distributions, depending on the package manager and distribution, typically store their GRUB files in /boot/efi/EFI/ubuntu or a similar directory specific to the distro name. If the Windows entry disappears from GRUB, it is rarely because the Windows bootloader itself is missing, but rather because GRUB’s configuration no longer points to it correctly.
Verifying the EFI Partition Contents
Before attempting to fix the bootloader configuration, you must verify that the necessary files actually exist on the disk. Boot into your Linux environment and open a terminal. First, identify the EFI partition by using the lsblk command or checking /etc/fstab. The EFI partition is usually mounted at /boot/efi.
Navigate to the EFI directory and list its contents:
cd /boot/efi
ls -l
You should see a directory named after your Linux distribution (e.g., ubuntu, fedora) and a directory named Microsoft. Inside the Microsoft folder, there should be a Boot subdirectory containing the bootmgfw.efi file. If these directories or files are missing, the issue is not merely a GRUB configuration error but a missing bootloader file. In such cases, refer to guides on repairing Accidentally Deleted UEFI Partition: Can't Boot Linux Mint scenarios, as the underlying problem is file deletion rather than configuration misalignment.
If the files are present, proceed to ensure that the GRUB utility can see them. Sometimes, permissions or mount options prevent GRUB from reading the EFI partition correctly during the generation phase.
Regenerating the GRUB Configuration
The most common solution to a missing Windows entry is to force GRUB to rescan the disks and regenerate its configuration file. This utility automatically detects installed operating systems and adds them to the menu.
Run the following command with sudo privileges:
sudo update-grub
On some systems, particularly those using older versions of GRUB or specific distributions, the command might be sudo grub-mkconfig -o /boot/grub/grub.cfg. Watch the output for lines indicating that Windows has been detected. You should see a message similar to "Found Windows 7 on /dev/sda1" or similar, confirming that the script has located the EFI bootloader.
If the command completes without errors but Windows still does not appear, check the generated grub.cfg file. Look for the section titled "### BEGIN recordfail ###" or search for "windows". If the entry is absent, it may indicate that GRUB lacks the module required to chain-load the Windows EFI bootloader. Ensure that the osprober package is installed, as it is responsible for detecting other operating systems.
sudo apt-get install osprober
After installing osprober, run update-grub again. Note that on newer Ubuntu versions, osprober is disabled by default for security reasons. You may need to enable it by adding GRUB_DISABLE_OSPROBER=false to /etc/default/grub and then running sudo update-grub.
Manual Entry Addition
In rare cases where automatic detection fails, you can manually add an entry to GRUB. Create a new script in /etc/grub.d/, such as 40_custom, and append the following block:
menuentry 'Windows 7' {
insmod part_gpt
insmod fat
set root='(hd0,gpt1)'
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
You must adjust (hd0,gpt1) to match your actual EFI partition identifier. Use grub-probe to find the correct device map if unsure. After editing, run update-grub one last time to apply the changes.
Frequently Asked Questions
Why does Windows 7 disappear from GRUB after a Linux update?
This usually happens because the Linux update overwrites grub.cfg without re-scanning for other operating systems. Running update-grub forces a rescan and restores the missing entries. Ensuring osprober is enabled prevents this recurrence.
Can I use EasyBCD to fix this issue from Windows?
No, EasyBCD is designed for legacy BIOS systems and does not support UEFI bootloaders effectively. Since Windows 7 on UEFI relies on EFI files, modifying them via Windows tools is difficult and risky. It is safer to fix the configuration from the Linux side.
What if the EFI partition is not mounted at /boot/efi?
Check /etc/fstab to see where the EFI partition is mounted. If it is mounted elsewhere, you must adjust your commands to point to that specific mount point. You can also temporarily mount it manually to verify file presence before regenerating GRUB.
Is it safe to edit /etc/grub.d/40_custom directly?
Yes, it is safe and a standard practice for adding custom boot entries. However, always back up the original file before making changes. Any edits will only take effect after running update-grub to rebuild the main configuration file.
How do I know if my system is using UEFI or Legacy BIOS?
Check if the /sys/firmware/efi directory exists. If it does, your system is using UEFI. If the directory is missing, it is likely using Legacy BIOS, in which case the Windows bootloader location would be different, and GRUB would handle it differently.