iPXE discussion forum

Full Version: 0xc000000d Win 7 x86 wim
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
The issue was described here:


I am facing exactly this, but my wim is only 140 Mb

2.52 is no go at all (is that a bug in 2.52 that makes it mostly unusable? - saying that, I have SCCM PXE ADK10 wims that ARE bootable via wimboot 2.52), if I try to use 2.52 I get

[Image: 2rdygew.jpg]

and beeping computer

With 1.06 I get Windows to start booting & then hangs on (non-descriptive) Windows Boot Manager 0xc000000d

I do DHCP undionly.0 --> PXELINUX 4.06 (for menu) & then swap to another server via

COM32 pxechn.c32

and run wimboot via

KERNEL ipxe.lkrn
initrd wim-boot-W10.ipxe
Nobody? 30+ reads & nothing?

Surely somebody that knows this stuff reads the forums?
After few more tests it only happens on machines with UEFI enabled (but legacy first). On pure BIOS machines or machines with UEFI turned off, it boots fine

Any fix?

Just to confirm, Is this a efi-capable machine running legacy with 3Gb of ram or more, trying to boot win 7 x86 based winpe?

You are trying to use wimboot 1.0.6 ?
Yes then the fix is to use the latest wimboot, or maybe remove so you only have 2GB of ram, or not use win 7 based PE (windows 8 based pe can be used to install windows 7 for example)

Have you tried chaining directly to ipxe, without using PXELINUX at all?
If you can't change from using pxelinux in your pxe setup, maybe you can test with an ipxe.usb image?
As stated in first port latest 2.52 is a NO go (hence the picture!)

I do NOT do any installs from PE (at least not by running setup.exe)
I have PE for other various tasks. Of course can redo wim to be Win 8 or whatever, just that I have this W7 based PE that I do like (for what I need) and wondered why it does not work (I assume it is W7PE limitation then?)
Secure boot off?
Reference URL's