Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I use Debian Wheezy on EFI motherboard and need ntldr module in GRUB2 to load bootmgr of Windows 7 installer, because the way it starts on its own (apparently, using the boot sector of the USB flash drive the installer is on) it only installs Windows on MBR-formatted disk. When I install GRUB using grub-install it won't add ntldr.mod to the GRUB modules folder and can't insmod it.

  1. Why? When i only download GRUB package without installation (apt-get download..), the module can be found there. If I add the .mod file from the downloaded package to the installed GRUB's modules folder and then "insmod ntldr" from the GRUB command line, it says sth about wrong "ELF magic" (?).
  2. How to do it forcibly?
  3. Is there another way to boot the Windows installer in the "GPT-mode", as I don't want to format the whole disk into MBR.
share|improve this question

You downloaded the grub-pc package, which is for bios booting machines, so the module will not load in the efi version of grub. That module does not exist in the EFI version of grub because it relies on the bios.

If you want to boot the windows installer from a usb stick, then you shouldn't be doing anything with grub; just tell your firmware to boot that drive instead of your hd with grub on it.

share|improve this answer

Alexey, this issue is frequently seen in grub2. I came across this one, while browsing through the ubuntu forums, where it is marked as solved. Have a look at there : http://ubuntuforums.org/showthread.php?t=1343362 . Hopefully this will help you .

share|improve this answer
as I understood, they talk about the Windows ntldr, which is the OS losder itself; I talk about ntldr.mod of GRUB, which is used to load the ntldr of Windows from GRUB – alexey Sep 28 '12 at 10:55
up vote 0 down vote accepted

I figured out the correct bootloader of Windows is hidden somewhere in the large packed files that come on the installation image. It can be unpacked, put into right boot directory and then loaded with GRUB2 chainloader as usually. I don't get why despite having right loader Microsoft hides it somewhere deep and places the strange one into default boot dir. It worked for me (though, I downloaded the file provided on the instructions page I found because it was quite some pain to unpack it). Unfortunately, I don't remember details, I found manual somewhere on the web, but the general idea is described.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.