Submit a contribution
Original post : No g2ldr: Fix for Windows XP, Vista, 7, 8, 8.1.
Name
Email
Description
Information about known causes and solutions for the boot-time error message "
No g2ldr
" and other g2ldr errors affecting the boot-up sequence for
Windows XP or Windows Vista, Windows 7, and Windows 8 or 8.1
About "No g2ldr"
[kbintro]
Description and Symptoms
The error messages, alerts, warnings, and symptoms below are tied to this error.
Symptom 1: "No g2ldr" seen on reboot
When attempting to start up a PC, an error stating "No g2ldr" is shown on the screen. It may or may not be accompanied with other error details or warning texts:
The full text:
No g2ldr
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
G2LDR, short for "GRUB2 Loader," is a variation/fork of the GRUB2 and Grub4Dos bootloaders. In particular, it is an updated version of Grub4Dos (aka GRLDR) compatible with/designed around the GNU GRUB 2 bootloader (instead of legacy GRUB). Some Linux distributions use the g2ldr bootloader to load the GRUB 2 bootloader from a "Windows" partition — basically, NTFS or FAT32. A failed such Linux installation can result in the "no g2ldr" error upon boot. It is also possible for g2ldr to be correctly installed and used for some time, before the error presents itself as a result of a Windows Update or Automatic Update that involved and update or upgrade of one or more of the core boot components (in this case, BOOTMGR or the bootsector).
Case 2: Failed recovery of the bootsector
Certain Windows recovery utilities employ G2LDR (the GRUB2 loader for Windows) to load BOOTMGR from the disk. Normally, this is attempted when the "regular" bootsector used by Windows Vista, Windows 7, and Windows 8 to locate and load BOOTMGR from the boot partition has failed. In these cases, the G2LDR loader is sometimes used as a proxy to attempt a round-about fashion of locating and loading BOOTMGR.
Fix no g2ldr in Windows XP
[setupcd]
Fix #1: Manually attempt recreation of boot.ini
For Windows XP machines seeing the "no G2LDR" error at boot, the following instructions detailing the correct (re)installation of the bootsector and Windows XP NTLDR bootloader as well as the recreation of the BOOT.INI boot entry configuration file can repair the issue: [partial name="partial_bootini"]
Fix no g2ldr in Windows Vista, 7, 8 or 8.1
[setupcd]
Fix #1: Manual recreation of the BCD
As the "no g2ldr" startup error is normally associated with the presence of a non-standard bootsector, the following instructions on fully reinitializing the MBR and bootsector with the default BOOTMGR-loading code can usually resolve the issue: [partial name="partial_rebuild_bcd"]
Fix #2: Use EasyBCD to configure Linux entries
If this g2ldr error is encountered in the process of installing a Linux distribution that attempts to use a "DOS-based" ((While GRLDR and G2LDR are originally from a project known as "GRUB 4 Dos" or "GRUB for DOS," in reality, DOS has nothing to do with it. The GRLDR/G2LDR projects focus on loading GRUB or GRUB2 from Windows-based partitions, namely FAT32 and NTFS.)) version of GRUB2, then it may be possible to set up the existing, standard BOOTMGR bootloader for Windows Vista, Windows 7, and Windows 8 to "chainload" the Linux installation and its copy of GRUB2. 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 Knowledgebase Entries
The errors below have been verified as being associated with or related to this problem:
Cannot find GRLDR
, a similar error but for the legacy GNU GRUB version of g2ldr
bootcfg
bootrec
[partial name="partial_moreinfo" versions="xp,vista,7,8,server2003,server2008,server2012"]