Fix No Such Partition Grub Rescue in Windows 10

If Windows 10 starts at a grub rescue> prompt with “no such partition,” GRUB cannot find the Linux files or partition referenced by its boot configuration. First identify whether Linux is still installed; then either repair GRUB from a Linux live USB or restore Windows Boot Manager if you want to remove Linux.

What the error means

GRUB is a bootloader commonly installed when Linux is added alongside Windows. It runs before either operating system and uses configuration files on a Linux partition to display a menu and start the selected system. The rescue prompt appears when GRUB starts but cannot locate a partition it expects, often after partitions have been deleted, resized, moved, or reformatted.

“No such partition” does not, by itself, mean Windows is damaged or that your files have been erased. Windows may still be intact, but the computer is trying to start through an obsolete GRUB entry. The right repair depends on whether you want to keep Linux and whether the computer uses UEFI or legacy BIOS boot.

Before changing partitions

Avoid deleting or formatting partitions just to make the message disappear. A Linux partition that looks unfamiliar in Windows may contain an installation or personal files, and removing the wrong partition can make recovery harder. If important files are at risk, stop and seek help before changing the disk.

Write down the exact error and note whether it appears immediately after power-on.
Check whether you recently removed Linux, changed partition sizes, replaced a drive, or changed firmware boot settings.
Use the firmware’s one-time boot menu to see whether “Windows Boot Manager” is available. Menu keys vary by computer; consult its on-screen prompt or documentation.
If you have a Linux live USB, boot it without installing Linux. Do not choose options that erase or repartition the drive.

If Windows Boot Manager starts Windows directly, back up important files before doing further work. If the computer asks for a BitLocker recovery key after firmware or boot changes, use the key associated with the device; do not disable encryption or change partitions as a workaround.

Choose the repair that matches your setup

Keep Linux: Repair or reinstall GRUB from a live Linux environment, making sure the bootloader points to the correct Linux installation and boot mode.
Remove Linux and use Windows: Start from Windows recovery or installation media and repair Windows Boot Manager. Only remove Linux partitions after confirming that Windows boots independently and that any wanted data is backed up.
Unsure what remains: Do not guess at partition numbers. Use a live environment or qualified repair assistance to identify partitions before writing changes.

These paths are not interchangeable. Reinstalling GRUB is appropriate when Linux remains wanted; Windows startup repair is more appropriate when the intended system is Windows alone. Changing boot order may help select an existing Windows entry, but it does not repair missing Linux files.

Repair GRUB if you want to keep Linux

Create or use a live USB for the Linux distribution already installed, then choose its “Try” or live-session option rather than installing. Use the computer’s firmware boot menu to start the USB in the same mode used by the installed system: UEFI or legacy BIOS.
In the live session, identify the Linux root partition and, on UEFI systems, the EFI System Partition. Partition labels and device names differ; do not assume a particular disk number or partition such as /dev/sda2. A graphical disk utility can help inspect filesystem types and sizes. If you cannot identify the correct partitions, stop rather than run commands copied blindly.
Follow the distribution’s documented GRUB recovery procedure for its version and boot mode. Typically, the installed system is mounted, required system filesystems are made available, and GRUB is installed or its configuration regenerated for the correct target. The exact commands differ between distributions, and UEFI repair differs from BIOS repair.
Restart, remove the USB when prompted, and test the boot menu. If GRUB opens but still cannot find Linux, its configuration may reference a changed partition or UUID; regenerate it from the installed system or repeat the distribution-specific recovery procedure.

A live USB can inspect and repair an installation, but it is not a reason to reinstall Linux. Reinstalling can overwrite data if the wrong destination is selected. Keep a backup when possible, especially before mounting partitions read-write or changing boot files.

Restore Windows Boot Manager if Linux is no longer needed

Use Windows recovery media or the Windows Recovery Environment. If you can reach the sign-in screen or desktop, Windows recovery options may be available through Settings under System and Recovery; otherwise, start from Windows installation or recovery media and select the repair option rather than installing Windows.

Choose the recovery environment’s troubleshooting options, then try Startup Repair. It is designed to detect and address some Windows startup problems without reinstalling Windows.
If Windows Boot Manager is listed in the firmware boot menu, select it. If it starts Windows, set it as the preferred boot entry in firmware settings, if that option is available.
If Startup Repair does not work, use the recovery environment’s Command Prompt only with instructions that match the computer’s UEFI or BIOS setup. Windows boot-repair steps differ by mode; commands that target the wrong disk or partition can cause further startup problems.
Once Windows starts reliably, back up your data. Then, if you are certain Linux and its files are no longer needed, remove its partitions using Windows’ disk tools and extend a Windows partition only where the layout permits.

Do not format the EFI System Partition simply because it contains GRUB-related files. UEFI computers can use that partition to start Windows as well as Linux. A repair should restore or select the Windows boot entry, not indiscriminately erase shared boot files.

Why quick fixes often fail

Commands found online may assume a particular distribution, disk layout, and boot mode. For example, a command that installs GRUB to a BIOS disk is not a universal fix for a UEFI installation. Likewise, setting the Windows entry first in firmware will not help if that entry is missing or its boot files are damaged.

Linux was deleted first: GRUB may remain in the boot path while its configuration partition is gone. Restore Windows Boot Manager rather than trying to recreate Linux files.
A partition was resized or moved: GRUB may have an outdated reference. Repair its configuration after verifying the current partitions.
Boot mode changed: Switching between UEFI and legacy/CSM can make existing boot entries appear unavailable. Restore the mode previously used before attempting repairs.
The drive is failing: Repeated disappearance of partitions or read errors may indicate a storage problem. Prioritize copying recoverable data and avoid repeated repair writes.

Frequently Asked Questions

Can I boot Windows from the grub rescue prompt?
Sometimes, but the commands depend on the current disk layout and available GRUB modules. A guessed command can fail or lead to the wrong partition. If Windows Boot Manager appears in the firmware boot menu, try that first; otherwise use recovery media or a knowledgeable technician.

Will Startup Repair delete my files?
Startup Repair is intended to repair startup problems, not erase personal files, but no recovery procedure is a substitute for a backup. Avoid options labeled install, reset, format, or erase unless you understand their effects.

Does “no such partition” mean my Windows partition is gone?
No. It means GRUB cannot find a partition it expects. Windows may remain untouched, so check for Windows Boot Manager before assuming data has been lost.

Should I delete the Linux partition?
Only if you have decided to remove Linux, confirmed that Windows boots through its own boot manager, and backed up anything you want to keep. Deleting a partition does not automatically repair the boot path.

Can changing UEFI settings fix the error?
It can help if the boot order is wrong or the computer was switched from UEFI to legacy mode. Restore the previous boot mode and look for Windows Boot Manager, but do not change Secure Boot or storage settings at random.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →