Recovering Windows 11 after an Ubuntu installation overwrites the bootloader requires restoring the EFI System Partition and repairing the Windows Boot Manager. This process involves booting from a Windows 11 recovery drive, accessing the command prompt to identify the correct partition, and using bcdboot to reinstall the boot files. The goal is to re-establish the GRUB/Windows dual-boot menu without losing data on either operating system.
Assessing the Damage and Preparing Recovery Media
When Ubuntu replaces or significantly modifies the EFI System Partition (ESP), it often removes the Windows Boot Manager entries. This leaves the system unable to find the Windows bootloader, resulting in a "No Bootable Device" error or dropping directly into the GRUB shell. Before attempting repairs, you must ensure that your Windows 11 installation media is accessible. Create a bootable USB drive using the Microsoft Media Creation Tool on another working computer. This tool allows you to download the latest Windows 11 ISO and write it to a USB stick. Ensure the USB drive has at least 8GB of free space. Once created, insert the USB into the Lenovo laptop and restart the machine. Access the BIOS/UEFI settings by pressing F2 or Fn+F2 repeatedly during startup. Navigate to the Boot tab and set the USB drive as the primary boot device. Save changes and exit. If the system boots into the Windows Setup screen, select "Repair your computer" instead of installing Windows. This option leads to the Recovery Environment, which contains the necessary tools for disk repair. Do not proceed with a fresh installation, as this will erase all existing data on the drives.Identifying Partitions Using Diskpart
The first critical step is to locate the EFI System Partition. In a standard dual-boot configuration, the ESP is a small FAT32 partition (usually 100-500MB) that contains the bootloaders for both Linux and Windows. Use the built-indiskpart utility to list all disks and partitions.
Open the Command Prompt from the Recovery Environment and type diskpart, then press Enter. Inside the diskpart prompt, enter the following commands sequentially:
list disk
select disk 0
list volumeS). If no volume letter is assigned, assign one by typing assign letter=S. It is crucial to correctly identify this partition because subsequent commands will target it. Incorrectly targeting the main Windows partition can lead to further corruption.
Once identified, exit diskpart by typing exit twice. You should now have a mapped drive letter for the EFI partition.
Restoring the Windows Boot Manager
With the EFI partition mapped, you need to copy the Windows boot files back to this location. Thebcdboot command is designed specifically for this purpose. It recreates the Boot Configuration Data store and copies necessary boot files.
Determine the drive letter of your Windows installation. In most cases, it is C:, but in the recovery environment, it might be different (e.g., D:). To verify, type dir C:\Windows and check if the folder exists. If not, try dir D:\Windows. Assume your Windows partition is C: for the following steps.
Execute the following command to restore the bootloader:
bcdboot C:\Windows /s S: /f ALLC: with your actual Windows drive letter and S: with the EFI partition letter you identified earlier. The /f ALL flag ensures that firmware-based boot files are created, which is essential for UEFI systems like modern Lenovo laptops. If successful, the command will return "Boot files created successfully."
After running the command, reboot the computer. Remove the USB drive when prompted. The system should now present the Windows Boot Manager, allowing you to choose between Windows 11 and Ubuntu.
Reinstalling GRUB for Dual-Boot Functionality
While restoring Windows boot files fixes the ability to start Windows, it may remove the GRUB bootloader entry for Ubuntu. To maintain dual-boot capability, you need to reinstall GRUB from within Ubuntu or use a live Linux USB. Boot into a Ubuntu Live USB and open a terminal. Identify your Ubuntu root partition and EFI partition usinglsblk. Mount the EFI partition to /boot/efi and the root partition to /mnt. Then, chroot into the installed system:
sudo mount /dev/sdXN /mnt
sudo mount /dev/sdYM /mnt/boot/efi
sudo chroot /mnt
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=ubuntu
update-grubsdXN with your Ubuntu root partition and sdYM with the EFI partition. This process reinstalls GRUB and updates the boot menu to include both Windows and Ubuntu. Reboot the system to verify that both operating systems appear in the boot selection menu.
Handling Partition Conflicts
Sometimes, the EFI partition may contain remnants of previous installations that cause conflicts. If the boot process hangs or fails after these steps, consider backing up the contents of the EFI partition and clearing it before repeating thebcdboot and GRUB installation steps. Always backup important data before modifying partition tables.
For more information on managing files in a dual-boot setup, see Dual-Booting Linux (Manjaro) and Windows. Additionally, if you encounter issues extending volumes after deleting partitions, refer to Can't Extend Volume in Windows After Deleting Ubuntu Dual Boot.
Frequently Asked Questions
Will repairing the bootloader delete my Ubuntu data?
No, repairing the bootloader only affects the EFI System Partition and does not touch the data stored in your Ubuntu root partition. However, always ensure you have backups of critical files before making any changes to boot configurations.Why did my Windows partition disappear from the disk list?
This usually happens if the partition table is corrupted or if the wrong disk was selected indiskpart. Verify that you are selecting the correct physical disk where Windows is installed. If the partition is missing, it may indicate severe corruption requiring professional data recovery.
Can I use a Linux Live USB to fix Windows boot issues?
While you can reinstall GRUB from a Live USB, fixing the Windows Boot Manager typically requires Windows-specific tools likebcdboot. Using third-party Linux tools to repair Windows boot may not guarantee success due to differences in how each OS handles UEFI variables.