Error cannot find grldr in all devices

Information on the origins of and resolution to the boot-time error message “No GRLDR” and similar GRLDR errors affecting these Windows versions: Windows XP Windows Vista, Windows 7, Windows 8 and Windows 8.1

About “Cannot find GRLDR”

The following information on this error has been compiled by NeoSmart Technologies, based on the information gathered and reported by our global network of engineers, developers, and technicians or partner organizations.

Description and Symptoms

The error messages, alerts, warnings, and symptoms below are tied to this error.

Symptom 1: “Cannot find GRLDR” shown at boot

Upon attempting to boot a PC, the error “Cannot find GRLDR.” is shown, possibly accompanied by one or more error messages before and after, like the ones shown in the example below:

Try (hd0,0): Extended:
Try (hd0,1): NTFS5: No grldr
Try (hd0,2): invalid or null
Try (hd0,3): invalid or null
Try (hd0,4): NTFS5: No grldr
Try (fd0): invalid or null
Cannot find GRLDR.
Press space bar to hold the screen, any other key to boot previous MBR ...
Timeout: 5

Symptom 2: “Cannot find GRLDR in all devices” shown at boot

A variation on the “Cannot find GRLDR” message from Symptom 1, but utilizing slightly different text and additional advice/instructions:

Try (hd0,0): NTFS5: 2
Try (hd0,1): Extended:
Try (hd0,2): invalid or null
Try (hd0,3): invalid or null
Try (hd0,4): NTFS5: No grldr
Try (hd1,0): Extended:
Try (hd1,1): invalid or null
Try (hd1,2): invalid or null
Try (hd1,3): invalid or null
Try (hd1,4): NTFS5: No grldr
Error: Cannot find GRLDR in all devices. Press Ctrl+Alt+Del to restart.

Symptom 3: “No WUBILDR”

An error message similar to the ones above is listed, but the Try (hdx, y) message indicates a failed search for a different file (WUBILDR):

Try (hd0,0): NTFS5: No wubildr
Try (hd0,1): Extended:
Try (hd0,2): invalid or null
Try (hd0,3): invalid or null
Try (hd0,4): FAT32: No WUBILDR
Error: Cannot find GRLDR in all devices. Press Ctrl+Alt+Del to restart.

Causes of this Error

This error has been known to occur as a result of one or more of the following:

Cause 1: Failed Linux installation

GRLDR is a nickname/abbreviation for the GRUB bootloader for Windows (also known as Grub4Dos or Grub for Dos), and is often used to set up a PC to dual-boot into Windows and one or more Linux (or other *nix-based) operating systems.

While most Linux distribution (such as Debian’s, Ubuntu’s, or Fedora’s) normally install the GRUB or GRUB2 bootloader, the installation routines of some distributions will attempt to set up the Windows bootloader to co-exist with the Linux installation by adding GRLDR either to the BCD menu or by replacing BOOTMGR with GRLDR entirely (and attempting to load it instead).

This error can occur either immediately after such a Linux distribution is installed or at some point in the future when Automatic Update or Windows Update patches the bootloader files or the bootsector itself, breaking the GRLDR-based configuration.

The Ubuntu-based “Wubi” is one such example. Wubi attempts to install Ubuntu to a virtual hard disk stored as a local file on your Windows NTFS/FAT partition instead of assigning it an actual disk partition. Wubi then integrates WUBILDR (a variation of GRLDR and short for “Wubi Loader”) into the BCD or BOOT.INI to chainload Wubi from this virtual disk as a boot-time startup option.

Cause 2: Use of Windows activation bypass

A “crack” in circulation used to bypass the Windows activation and Genuine Windows Validation tests for Windows Vista and Windows 7 attempts to inject certain code directly into the boot process.

As a stock, unmodified BOOTMGR will refuse to load unsigned kernels or Windows kernels that have been tampered or modified, the GRUB for Windows bootloader “grldr” is used instead.

This Windows activation crack can either fail to load correctly from the very start, causing this error to manifest immediately after applying the Windows Vista or Windows 7 activation patch, or it can work successfully for any length of time (months to years) until the patched GRLDR file in the root of the boot partition can no longer be loaded due to changes to the bootsector, often caused by Automatic Updates or Windows Updates, causing the “No GRLDR” message to appear at boot and the PC to fail to load.

Cause 3: NTFS bootsector incorrectly updated

Certain system-level software and utilities will attempt to reconfigure, upgrade, update, or repair the NTFS or FAT32 bootsector for the boot partition. Normally, the bootsect or bootrec command-line tools are used for this procedure. 3rd party software attempting unsupported/unofficial updates to the bootsector can break the delicate boot chain and cause the “no GRLDR” to appear.

Fix no grldr in Windows XP

Fix #1: Rebuild BOOT.ini and other boot components via Easy Recovery Essentials

The one-click automated Windows repair feature of the latest versions of EasyRE supports the full reconstruction of the Windows XP boot process. Its use will correct the “no grldr” error (and all variations thereof) by automatically rebuilding boot.ini with the correct configuration, and setting up the MBR and bootsector to load NTLDR (instead of GRLDR).

Easy Recovery Essentials is guaranteed to fix the “no grldr” error automatically using its built-in Automated Repair option. EasyRE is currently available for Windows XP, Vista, 7 and 8 and can be downloaded and created on any PC.

1. Download Easy Recovery Essentials. Make sure to note your Windows version (XP, Vista, 7 or before you download EasyRE. This guide can help you identify what version of Windows you have installed.
2. Burn the image. Follow these instructions on how to burn the bootable ISO image very carefully, as making a bootable CD can be tricky! Alternatively, these instructions explain how to create a bootable EasyRE recovery USB stick/drive.
3. Boot up your PC from the Easy Recovery Essentials CD or USB you created.
4. Once EasyRE is running, choose the “Automated Repair” option and click Continue.

   

   Choose “Automated Repair” in Easy Recovery Essentials

5. After EasyRE scans your computer’s drives, identify and select the drive letter for your Windows installation from the list, and then click on the Automated Repair button to begin.

   

   Choose the drive associated with the Windows installation you’re trying to repair.

6. Easy Recovery Essentials will start analyzing the selected drive for problems. EasyRE will test for and attempt to automatically correct errors with the disk, partition, bootsector, filesystem, bootloader, and registry. No intervention is required, as EasyRE’s repair is fully automated:

   

   Easy Recovery Essentials searches for errors and makes corrections to the selected Windows installation.

7. Once the process is complete, EasyRE will report its findings. Click on the Restart button to reboot your PC and test the changes.
8. The “no grldr” error should now be fixed as your PC begins to load:

   

   Windows, booting up successfully.

You can download Easy Recovery Essentials from here.

Fix #2: Manually attempt recreation of boot.ini

Windows Setup CD/DVD Required!
Some of the solutions below require the use of the Microsoft Windows setup CD or DVD. If your PC did not come with a Windows installation disc or if you no longer have your Windows setup media, you can use Easy Recovery Essentials for Windows instead. EasyRE will automatically find and fix many problems, and can also be used to solve this problem with the directions below.

For machines running Windows XP suffering from the “no GRLDR” error, a repair of boot.ini and the MBR/bootsector can take care of the problem.

A boot.ini file is used by Windows to configure and display its operating system options. Instructions on manually recreating the boot.ini file are also available, but require a moderate level of computer expertise. The instructions below will guide you on recreating boot.ini automatically from the Windows XP setup CD.

Unable to boot into the Windows setup CD?
See our guide on setting up a PC to boot from the CD or DVD for troubleshooting and more detailed instructions.

1. Insert your Windows XP CD and restart your computer.
2. Press a key to boot into the CD when you see the “Press any key to boot from CD” message.
3. When you arrive at the “Welcome to Setup” message, press R to start the Recovery Console.
4. Type in your Administrator password; hit Enter
5. The next command you need to write is below; hit Enter afterwards:

   bootcfg /rebuild

The above command, bootcfg /rebuild, will scan your computer for installed Windows copies. If you have Windows XP, here are the next steps:

1. Press Y if the command prompt shows a message similar to the one below:

   Total Identified Windows Installs: 1
   
   [1] C:Windows
   Add installation to boot list? (Yes/No/All)

2. When you receive a message like this:

   Enter Load Identifier

   You are being asked to provide a name to be assigned and shown in the boot menu for the installation you picked in the previous step. Examples:

   Enter Load Identifier: Windows XP Professional (Recovered)

3. (Optional) When you receive a message like this:

   Enter OS Load options

   Type in /fastdetect followed by Enter

4. Restart your computer.

Fix no grldr in Windows Vista, 7, 8

Fix #1: Rebuild MBR with EasyRE

For the cases that present the “no GRLDR” error due to a misconfigured MBR/bootsector or a corrupted chainload, EasyRE’s automated boot repair procedure can isolate and fix the affected components, restoring boot to the PC.

Easy Recovery Essentials is guaranteed to fix the “no grldr” error automatically using its built-in Automated Repair option. EasyRE is currently available for Windows XP, Vista, 7 and 8 and can be downloaded and created on any PC.

1. Download Easy Recovery Essentials. Make sure to note your Windows version (XP, Vista, 7 or before you download EasyRE. This guide can help you identify what version of Windows you have installed.
2. Burn the image. Follow these instructions on how to burn the bootable ISO image very carefully, as making a bootable CD can be tricky! Alternatively, these instructions explain how to create a bootable EasyRE recovery USB stick/drive.
3. Boot up your PC from the Easy Recovery Essentials CD or USB you created.
4. Once EasyRE is running, choose the “Automated Repair” option and click Continue.

   

   Choose “Automated Repair” in Easy Recovery Essentials

5. After EasyRE scans your computer’s drives, identify and select the drive letter for your Windows installation from the list, and then click on the Automated Repair button to begin.

   

   Choose the drive associated with the Windows installation you’re trying to repair.

6. Easy Recovery Essentials will start analyzing the selected drive for problems. EasyRE will test for and attempt to automatically correct errors with the disk, partition, bootsector, filesystem, bootloader, and registry. No intervention is required, as EasyRE’s repair is fully automated:

   

   Easy Recovery Essentials searches for errors and makes corrections to the selected Windows installation.

7. Once the process is complete, EasyRE will report its findings. Click on the Restart button to reboot your PC and test the changes.
8. The “no grldr” error should now be fixed as your PC begins to load:

   

   Windows, booting up successfully.

You can download Easy Recovery Essentials from here.

Fix #2: Use Startup Repair to recreate BCD and bootsector

Windows Setup CD/DVD Required!
Some of the solutions below require the use of the Microsoft Windows setup CD or DVD. If your PC did not come with a Windows installation disc or if you no longer have your Windows setup media, you can use Easy Recovery Essentials for Windows instead. EasyRE will automatically find and fix many problems, and can also be used to solve this problem with the directions below.

Startup Repair is an automated diagnosis and repair tool that is available from the Windows setup disc and can be used to find and repair some common problems. More information about how Startup Repair operates and what it does can be found in our knowledgebase. The following steps will initiate Startup Repair from the Windows setup disc:

Unable to boot into the Windows setup CD?
See our guide on setting up a PC to boot from the CD or DVD for troubleshooting and more detailed instructions.

1. Insert your Windows installation DVD into your PC’s CD-ROM drive,
2. Fully power down your PC, and make sure it has fully shut off,
3. Power up your PC,
4. Press any key when you see “Press any key to boot from CD or DVD..”
5. Click the link titled “Repair your computer” in the bottom-lefthand corner, after first selecting your language and keyboard options.
   
6. Wait for Startup Repair to scan your PC for Windows installations, then select your install from the list it shows:
   
7. Choose “Startup Repair” from the list of available recovery options to begin:
   
8. Startup Repair will begin scanning your installation for known issues and will attempt a repair, if possible.
   

Fix #3: Obtain valid Windows Vista/7 license

In the case that the “No GRLDR” boot-time error message is caused by the (attempted) usage of an activation bypass crack, it will be necessary for the owner/operator of the PC in question to obtain a valid license for Windows Vista or Windows 7 (see links below).

Note that in cases where the “No GRDLR” error appears at boot because of an activation patch for Windows, correcting the issue with the above fixes will normally cause Genuine Windows Validation to fail and activation prompts or nag screens to appear upon successful boot of Microsoft Windows.

Fix #4: Use EasyBCD to configure Linux entries

If this error is encountered in the process of setting up a dual-boot between Windows and a Linux distribution (or a virtual-disk-based Wubi install), NeoSmart Technologies’ EasyBCD boot manager can instead be used to correctly set up and configure the dual-boot between Windows Vista, Windows 7, or Windows 8 or 8.1 and Linux.

Instructions on using EasyBCD and creating a dual-boot with Linux can be found in the EasyBCD-specific section of our knowledgebase.

More Information

Linked Entries

The errors below have been verified as being associated with or related to this problem:

• No G2LDR, a similar error but for the GRUB2 version of GRLDR
• bootcfg

Support Links

• Easy Recovery Essentials for Windows – our repair and recovery disk.

  It’s an easy-to-use and automated diagnostics disk. It’s available for Windows 8, Windows 7 and Windows Vista. It’s also available for Windows XP and Windows Server.

  Read more at Windows Recovery Disks.

• The NeoSmart Support Forums, member-to-member technical support and troubleshooting.
• Get a discounted price on replacement setup and installation discs: Windows XP, Windows Vista, Windows 7, Windows 8.

Applicable Systems

This Windows-related knowledgebase article applies to the following operating systems:

• Windows XP (all editions)
• Windows Vista (all editions)
• Windows 7 (all editions)
• Windows 8 (all editions)
• Windows 8.1 (all editions)
• Windows Server 2003 (all editions)
• Windows Server 2008 (all editions)
• Windows Server 2012 (all editions)

Propose an edit

Как-то создавая мультизагрузочную флэшку с помощью Novicorp WinToFlash v1.13, у меня возникла проблема с загрузкой с этой флэшки на одном из компьютеров (материнка ASUS Maximus Formula), даже на более древнем (2006) ноутбуке проблем с загрузкой с этой флэшки не было. А тут выдает ошибку, что не найден grldr (Cannot find GRLDR).

Методом долгого тестирования, я выяснил, что виноват grub4dos, входящий в состав. Банальной заменой файла grldr из состава WinToFlash на новый из программы Grub4DOS так просто проблему не решить. Как я это сделал читайте ниже.
Вообще там что-то связано с загрузочной областью MBR.

Требуемый софт:

• Novicorp WinToFlash v1.13
• BOOTICE v1.3.4 — by Pauly
• Grub4dos Installer v1.1
• новая версия Grub4DOS

Вариант 1 (простой или тем кто только создает мультизагрузочную флэшку )

 Создание мультизагрузочной флэшки с помощью программы NoviCorp WinToFlash 1.13 с уже обновлённым Grub4DOS

1. Открываем папку WinToFlashComponentsMultibootManagerBootCore. Там переименовываем файл grldr например в grldr_org. Запускаем программу Bootice от имени администратора. Нажимаем закладку «Утилиты». Редактор меню Grub4DOS. Откроется Редактор меню Grub4DOS. Открываем файл grldr_org (иконка папки со стрелкой). Копируем все содержимое в буфер обмена (CTRL+A, потом CTRL+С). Не закрываем окно.

2. Скачиваем последнюю версию Grub4DOS с сайта разработчика выбрав последний год. Я использовал версию grub4dos-0.4.6a-2019-03-25. Если с более новыми будут проблемы используйте ту, что и я.  Распаковываем из архива grub4dos-0.4.6a-2019-03-25.7z файл grldr в папку WinToFashComponentsMultibootManagerBootCore.

3. Возвращаемся в Bootice Редактор Grub4DOS. Открываем файл grldr из папки WinToFlashComponentsMultibootManagerBootCore, выделяем весь текст (CTRL+A) и вставляем содержимое из буфера (CTRL+V). Сохраняем, нажав на дискету с буквой A (ANSI). Закрываем Редактор и Bootice. Теперь можно удалить старый grldr_org из WinToFlashComponentsMultibootManagerBootCore

4. Запускаем WinToFlash от имени администратора (правая кнопка мыши на запускном файле и выбрать Запуск от имени администратора). Добавляем образы и запускаем создание мультизагрузочной флэшки. Дождаться завершения.

5. Вот теперь у нас обновленная версия Grub4DOS на флэшке созданной в WinToFlash. Версию можно увидеть в редакторе Grub4DOS в строке состояния, открыв файл grldr на флэшке. Так же можно проверить какая версия Grub4DOS на флэшке, то нужно загрузиться с флэшки (или воспользоваться эмулятором QEMU) и переходя из меню в меню можно увидеть версию в верхней строке.

Вариант 2 (более сложный или тот кто уже сделал мультизагрузочную флэшку, но не хочет создавать ее заново начать с 4 пункта)

Создание мультизагрузочной флэшки с помощью программы NoviCorp WinToFlash 1.13 с последующим обновлением Grub4DOS

1. Форматируем флэшку в NTFS стандартной программой в Windows

2. Запускаем WinToFlash от имени администратора (правая кнопка мыши на запускном файле и выбрать Запуск от имени администратора). Добавляем образы, отключаем форматирование, если с форматированием NTFS (бывает ругается), то пропустить следующий пункт 3), запустить создание мультизагрузочной флэшки. Дождаться завершения.

3. Запускаем grubinst_gui.exe от имени администратора. Выбираем флэшку (не ошибитесь с выбором диска) и нажимаем Install (если будут проблемы с загрузкой флэшки, поиграться с Опциями Disable PrevMBR и Previous MBR first)

4. Переименовываем файл grldr, который находится на флэшке, например в grldr_org. Запускаем программу Bootice от имени администратора. Выбираем флэшку в «Диск назначения». Нажимаем закладку «Утилиты». Редактор меню Grub4DOS. Откроется Редактор меню Grub4DOS. Открываем файл grldr_org (иконка папки со стрелкой). Копируем все содержимое в буфер обмена (CTRL+A, потом CTRL+С). Не закрываем окно.

5. Скачиваем последнюю версию Grub4DOS с сайта разработчика выбрав последний год. Я использовал версию grub4dos-0.4.6a-2019-03-25. Если с более новыми будут проблемы используйте ту, что и я.  Распаковываем из архива grub4dos-0.4.6a-2019-03-25.7z файл grldr на флэшку.

6. Возвращаемся в Bootice Редактор Grub4DOS. Открываем grldr с флэшки, выделяем весь текст (CTRL+A) и вставляем содержимое из буфера (CTRL+V). Сохраняем, нажав на дискету с буквой A (ANSI). Закрываем Редактор и Bootice. Теперь с флэшки можно удалить grldr_org

7. Вот теперь у нас обновленная версия Grub4DOS на флэшке созданной ранее в WinToFlash. Версию можно увидеть в редакторе Grub4DOS в строке состояния, открыв файл grldr на флэшке. Так же можно проверить какая версия Grub4DOS на флэшке, то нужно загрузиться с флэшки (или воспользоваться эмулятором QEMU) и переходя из меню в меню можно увидеть версию в верхней строке.

Here we can see “Cannot find GRLDR: Fix for Windows XP, Vista, 7, 8, 8.1”

Symptoms and description

This Error is linked to the error messages, alerts, warnings, and symptoms listed below.

Symptom 1: The message “Cannot detect GRLDR” appears at boot.

When attempting to boot a computer, the error “Cannot detect GRLDR.” appears, potentially followed by one or more error messages, such as the ones given below:

Try (hd0,0): Extended:
Try (hd0,1): NTFS5: No grldr
Try (hd0,2): invalid or null
Try (hd0,3): invalid or null
Try (hd0,4): NTFS5: No grldr
Try (fd0): invalid or null
Cannot find GRLDR.
Press space bar to hold the screen, any other key to boot previous MBR ...
Timeout: 5

Symptom 2: At boot, the message “Cannot find GRLDR in all devices” appears.

A somewhat altered version of Symptom 1’s “Cannot find GRLDR” notice, with slightly changed language and additional advice/instructions:

Try (hd0,0): NTFS5: 2
Try (hd0,1): Extended:
Try (hd0,2): invalid or null
Try (hd0,3): invalid or null
Try (hd0,4): NTFS5: No grldr
Try (hd1,0): Extended:
Try (hd1,1): invalid or null
Try (hd1,2): invalid or null
Try (hd1,3): invalid or null
Try (hd1,4): NTFS5: No grldr
Error: Cannot find GRLDR in all devices. Press Ctrl+Alt+Del to restart.

Symptom 3: “No WUBILDR”

The Try (hdx, y) message indicates a failed search for a different file (WUBILDR): An error message similar to the ones above is listed.

Try (hd0,0): NTFS5: No wubildr
Try (hd0,1): Extended:
Try (hd0,2): invalid or null
Try (hd0,3): invalid or null
Try (hd0,4): FAT32: No WUBILDR
Error: Cannot find GRLDR in all devices. Press Ctrl+Alt+Del to restart.

This Error’s Causes

One or more of the following factors have been linked to this error:

Cause 1: Failed Linux installation

The GRUB bootloader for Windows (also known as Grub4Dos or Grub for Dos) is often used to set up a PC to dual-boot into Windows and one or more Linux (or other *nix-based) operating systems. GRLDR is a nickname/abbreviation for the GRUB bootloader for Windows (also known as Grub4Dos or Grub for Dos) and is often used to set up a PC to dual-boot into Windows and one

While most Linux distributions (such as Debian, Ubuntu, or Fedora) normally install the GRUB or GRUB2 bootloader, some distributions’ installation routines will attempt to coexist the Windows bootloader with the Linux installation by adding GRLDR to the BCD menu or replacing BOOTMGR with GRLDR entirely (and attempting to load it instead).

This issue can occur immediately after installing a Linux distribution or later when Automatic Update or Windows Update modifies the bootloader files or the bootsector itself, breaking the GRLDR-based configuration.

One such example is the Ubuntu-based “Wubi.” Instead of designating an actual disk partition, Wubi attempts to install Ubuntu on a virtual hard disk kept as a local file on your Windows NTFS/FAT partition. The WUBILDR (a variant of GRLDR and short for “Wubi Loader”) is then integrated into the BCD or BOOT by Wubi. INI can chainload Wubi from this virtual drive as a boot-time startup option.

Cause 2: Bypassing Windows activation.

A “crack” in circulation for Windows Vista and Windows 7 aims to insert certain code directly into the boot process, bypassing the Windows activation and Genuine Windows Validation tests.

The GRUB for Windows bootloader “grldr” is used instead of BOOTMGR because it refuses to load unsigned kernels or Windows kernels that have been tampered with or modified.

This Windows activation crack can either fail to load correctly from the start, causing this error to appear shortly after applying the Windows Vista or Windows 7 activation patch, or it can work successfully for months or years until the patched GRLDR file in the root of the boot partition can no longer be loaded due to changes to the bootsector, often caused by Automatic Updates or Windows Updates, resulting in the “No GRLDR” message appearing.

Cause 3: The NTFS bootsector has been changed erroneously.

Certain system-level software and utilities will rearrange, upgrade, update, or repair the boot partition’s NTFS or FAT32 bootsector. This technique is usually performed with the bootsect or bootrec command-line utilities. Unsupported/unofficial modifications to the bootsector by third-party software can break the delicate boot chain, resulting in the “no GRLDR” error.

In Windows XP, resolve the issue of no grldr

Fix 1: Using Easy Recovery Essentials, rebuild BOOT.ini and other boot components.

The latest versions of EasyRE support the entire reconstruction of the Windows XP boot process with its one-click automated Windows repair capability. Its use will fix the “no grldr” error (and all variations thereof) by automatically rebuilding boot.ini and setting up the MBR and bootsector to load NTLDR (instead of GRLDR).

Easy Recovery Essentials’ built-in Automated Repair tool is guaranteed to instantly fix the “no grldr” fault. EasyRE can be downloaded and produced on any PC and is presently available for Windows XP, Vista, 7, and 8.

1. Easy Recovery Essentials is a free download. Before you download EasyRE, note your Windows version (XP, Vista, 7, or 8).
2. The image should be burned.
3. Start your computer with the Easy Recovery Essentials CD or USB you made.
4. After EasyRE has started, select “Automated Repair” and click Continue.
5. After EasyRE has finished scanning your computer’s disks, find and pick the drive letter for your Windows installation from the list, and then click the Automated Repair option to start the repair process.
6. Easy Recovery Essentials will begin looking for faults on the selected drive. EasyRE will scan the disk, partition, bootsector, filesystem, bootloader, and registry for faults and rectify them automatically. EasyRE’s repair is automated, thus no interaction is required:
7. EasyRE will provide its findings after the process is completed. To reboot your PC and test the changes, click the Restart option.

Fix 2: Manually attempt recreation of boot.ini

A boot fix is required for PCs running Windows XP and experiencing the “no GRLDR” problem.

The problem can be solved using ini and the MBR/bootsector.

Windows uses the boot.ini file to customize and show its operating system choices. Manually rebuilding the boot.ini file is also possible, but it necessitates a moderate level of computer knowledge. The steps below will walk you through automatically recreating boot.ini from the Windows XP setup CD.

1. Restart your computer after inserting the Windows XP CD.
2. When you see the message “Press any key to boot from CD,” press a key to boot into the CD.
3. When the “Welcome to Setup” display appears, press R to open the Recovery Console.
4. Hit Enter after entering your Administrator password.
5. The following is the next command you must type; after that, press Enter:

bootcfg /rebuild

The above command, bootcfg /rebuild, will look for installed Windows copies on your computer. If you’re using Windows XP, follow these steps:

1. If the command prompt displays a message similar to the one below, press Y:

Total Identified Windows Installs: 1

[1] C:Windows
Add installation to boot list? (Yes/No/All)

2. When you get a message like this, you should:

Enter Load Identifier

You’ll be prompted to give the installation you chose in the previous stage a name that will be allocated to it and shown in the boot menu. Examples:

Enter Load Identifier: Windows XP Professional (Recovered)

3. (Optional) If you get a message like this, type /fastdetect and press Enter.

Enter OS Load options

4. Your computer should be restarted.

In Windows Vista, 7, and 8, there is no grldr

Fix 1: Use EasyRE to rebuild the MBR

EasyRE’s automated boot repair technique can isolate and restore the complex components, restoring boot to the PC, in circumstances where the “no GRLDR” error is caused by a misconfigured MBR/bootsector or a corrupted chainload.

Easy Recovery Essentials’ built-in Automated Repair tool is guaranteed to instantly fix the “no grldr” fault. EasyRE can be downloaded and produced on any PC and is presently available for Windows XP, Vista, 7, and 8.

1. Download Easy Recovery Essentials. Before you download EasyRE, note your Windows version (XP, Vista, 7, or 8).
2. The image should be burned.
3. Start your computer with the Easy Recovery Essentials CD or USB you made.
4. After EasyRE has started, select “Automated Repair” and click Continue.
5. After EasyRE has finished scanning your computer’s disks, find and pick the drive letter for your Windows installation from the list, and then click the Automated Repair option to start the repair process.
6. Easy Recovery Essentials will begin looking for faults on the selected drive. EasyRE will scan the disk, partition, bootsector, filesystem, bootloader, and registry for faults and rectify them automatically. EasyRE’s repair is automated, thus no interaction is required:
7. EasyRE will provide its findings after the process is completed. To reboot your PC and test the changes, click the Restart option.

Fix 2: Recreate the BCD and bootsector with Startup Repair

Startup Repair is an automated diagnosis and repair program that comes with the Windows installation disc and may be used to discover and fix various issues. In our knowledge base, you may learn more about how Startup Repair works and what it does. The Startup Repair procedure from the Windows setup CD is as follows:

1. Place your Windows installation DVD in the CD-ROM drive of your computer.
2. Make sure your computer is completely turned off by shutting it down completely.
3. Turn on your computer.
4. When you see “Press any key to boot from CD or DVD,” press any key.
5. After selecting your language and keyboard selections, click the “Repair your computer” link in the bottom-lefthand corner.
6. Wait for Startup Repair to finish scanning your computer for Windows installations, then choose yours from the list:
7. To get started, select “Startup Repair” from the list of potential recovery options:
8. Startup Repair will begin checking your installation for known problems and, if possible, will repair them.

Fix 3: Obtain valid Windows Vista/7 license

Suppose the “No GRLDR” boot-time error message is generated by the (attempted) use of an activation bypass crack. In that case, the owner/operator of the PC in issue will need to purchase a valid Windows Vista or Windows 7 license.

Note that if the “No GRDLR” error happens at startup due to a Windows activation patch, using the following remedies will usually result in Genuine Windows Validation failing and activation prompts or nag screens appearing after a successful boot of Microsoft Windows.

Fix 4: To configure Linux entries, use EasyBCD

If this error occurs while setting up a dual-boot between Windows and a Linux distribution (or a virtual-disk-based Wubi install), EasyBCD boot manager can be used instead to properly set up and configure the dual-boot between Windows Vista, Windows 7, Windows 8, or Windows 8.1 and Linux.

The EasyBCD-specific section of our knowledge base has instructions on using EasyBCD and creating a dual-boot with Linux.

Conclusion

I hope you found this information helpful. Please fill out the form below if you have any queries or comments.

User Questions

1. What exactly is G2LDR?

The G2LDR bootloader (short for “GRUB2 Loader”) is a fork of the GRUB2 and Grub4Dos bootloaders. It’s a newer version of Grub4Dos (aka GRLDR) compatible with and built around the GNU GRUB 2 bootloader (rather than legacy GRUB)… The “no g2ldr” issue can occur when a Linux installation fails.

2. What exactly is Wingrub?

GRUB4DOS and WINGRUB are stated as “GRUB for DOS is GRUB’s DOS extension.” The project includes WINGRUB, a graphical user interface (GUI) for configuring and installing GRUB in the Windows environment. It is categorized as a Boot Manager in the OS & utility category.

3. In Kali Linux, what is the GRUB boot loader?

A bootloader, often known as a boot program or bootstrap loader, is a piece of operating system software that loads into a computer’s working memory once it is turned on. A bootloader is often launched by a bootable medium such as a hard drive, a CD/DVD, or a USB stick shortly after a device starts for this purpose.

4. Laptop is missing grldr

Laptop is missing grldr from computers

5. ‘Cannot find grldr’ after I plugged in a new SSD

‘Cannot find grldr’ after I plugged in a new SSD from techsupport

1. Hi — My first post — please don’t bite me?!

   I’ve been really impressed by a friend’s ubuntu machines, and wanted to give it a try.

   He said I could do this ‘risk free’ by installing it inside windows, and even gave me a copy of the latest ubuntu.

   It installed OK, and now I have the option to boot into either Windows or Ubuntu. But when I pick Ubuntu, I get the error message

   Cannot find GRLDR in all devices.

   I asked my friend, who told me to do a ‘defrag’ and disk check. I did, but still got the problem. Then he admitted he was clueless about it, but he told me I would ‘definitely’ get a solution here.

   I’m not sure about that, because you’ll probably need all sorts of tech info, to help me?
   And I’m a PC user, not a PC expert.

   I would LOVE to be a Ubuntu user, and would be grateful if anyone can either advise me what’s wrong or (gently) let me know that I’m not enough of an expert to ever fix this.

   But I’m hoping someone can help, since this is ‘Linux for Human Beings.’

   Thanks!

   ---

2. Impossible problem? Cannot find GRLDR in all devices?
   

   Hi,

   Sorry to post this as a ‘reply’ to my own question, but I’m totally 100% stuck.

   I’ve found other forum threads on the exact same problem (some of them YEARS old!), and reading through them, it seems that the problem is either:

   a) impossible to fix, so just try a different sort of Linux instead (PCLinuxOS was mentioned)

   or

   b) Really, really, really, really, really, really hard to fix. (In which case, I have no chance whatsoever)

   So I thought I’d have one more try. My Ubuntu friend said I would definitely get an answer of some sort in this forum, but it seems not….

   Maybe it’s just God’s way of saying, ‘Stick with Windows, dummy — you’re not smart enough for Ubuntu!’ Anyway, if anybody can help, I’d be really grateful.

   ---

3. Re: Error: Cannot find GRLDR in all devices?
   

   This is why Linux in general will always be obscure garbage. I mean really? I’ve dabbled in Ubuntu and other flavors over the years and am by no means knowledgeable but know quite a bit about computers in general.

   I got a new notebook I wanted to have an unbuntu install on. Come to the website and go with a Wubi install as its «simple and safe.»

   But the ******* thing doesn’t work.

   «Error: Cannot find GRLDR in all dvices. Press Ctrl+Alt+Delete»

   Are you kidding me? Searches on this provide results from over 4 years ago WITH NO RESOLUTIONS.

   Way to fail.

   ---

4. Re: Error: Cannot find GRLDR in all devices?
   

   Originally Posted by d1gw33d
   

   This is why Linux in general will always be obscure garbage. I mean really? I’ve dabbled in Ubuntu and other flavors over the years and am by no means knowledgeable but know quite a bit about computers in general.

   I got a new notebook I wanted to have an unbuntu install on. Come to the website and go with a Wubi install as its «simple and safe.»

   But the ******* thing doesn’t work.

   «Error: Cannot find GRLDR in all dvices. Press Ctrl+Alt+Delete»

   Are you kidding me? Searches on this provide results from over 4 years ago WITH NO RESOLUTIONS.

   Way to fail.

   Please refer to http://ubuntu-with-wubi.blogspot.com…and-grldr.html for a discussion of this issue and the potential causes.

   Wubi is designed for easy trial for Windows users that are afraid of partitioning or don’t want to unless they are sure they will keep Ubuntu. It does work for most without hassle, but of course not everyone (for obvious reasons).

   I suggest — if you cannot resolve this problem — then you can try out Ubuntu in the following ways:
   1. from a CD or USB stick
   2. from a virtual machine
   3. from a direct install (with partitioning)

   While it’s obviously frustrating that things didn’t just work first time for you on your new machine… you probably want to avoid calling Linux garbage. It’s inflammatory and most likely won’t get you any help.

   ---

5. Re: Error: Cannot find GRLDR in all devices?
   

   Originally Posted by Servopal
   

   Hi — My first post — please don’t bite me?!

   I’ve been really impressed by a friend’s ubuntu machines, and wanted to give it a try.

   He said I could do this ‘risk free’ by installing it inside windows, and even gave me a copy of the latest ubuntu.

   It installed OK, and now I have the option to boot into either Windows or Ubuntu. But when I pick Ubuntu, I get the error message

   Cannot find GRLDR in all devices.

   I asked my friend, who told me to do a ‘defrag’ and disk check. I did, but still got the problem. Then he admitted he was clueless about it, but he told me I would ‘definitely’ get a solution here.

   I’m not sure about that, because you’ll probably need all sorts of tech info, to help me?
   And I’m a PC user, not a PC expert.

   I would LOVE to be a Ubuntu user, and would be grateful if anyone can either advise me what’s wrong or (gently) let me know that I’m not enough of an expert to ever fix this.

   But I’m hoping someone can help, since this is ‘Linux for Human Beings.’

   Thanks!

   Solotion :- Log into Windows. You might have installed Ubuntu using Wubi on either C:/ drive or any other drive. Go to «ubuntu» folder in the location where ubuntu is installed. Copy wubildr and wubildr.mbr from this location and paste it in C:/ (not inside any folder).

   Now reboot. . .and try booting into Ubuntu. . I’m sure. . it works. . .

   ---

6. Re: Error: Cannot find GRLDR in all devices?
   

   Solution :- Log into Windows. You might have installed Ubuntu using Wubi on either C:/ drive or any other drive. Go to «ubuntu» folder in the location where ubuntu is installed. Copy wubildr and wubildr.mbr from this location and paste it in C:/ (not inside any folder).

   Now reboot. . .and try booting into Ubuntu. . I’m sure. . it works. . .

   ---

7. Re: Error: Cannot find GRLDR in all devices?
   

   Old thread closed, please don’t bump old threads.

   ---