iPXE discussion forum

Full Version: Error Code 0x0000005c during WinPE load
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi,

I'm using a first generation Hyper-V VM running on a Windows 2012R2 server and booting off of ipxe.iso (with ipxe.krn). I'm using wimboot v.2.5.2 to try and load WinPE. Here is the contents of the script I'm running using the chain command...

Code:
kernel http://x.x.x.x/winpe/wimboot  gui
initrd http://x.x.x.x/winpe/bcd        bcd
initrd http://x.x.x.x/winpe/boot.sdi        boot.sdi
initrd http://x.x.x.x/winpe/boot.wim       boot.wim
boot

I see each of these lines process o.k., then I see WinPE start to load with the blue windows logo in the middle of the screen. Next I get this error message...

Your PC needs to restart.
Please hold down the power button.
Error Code: 0x0000005C
Parameters:
<4 lines of parameters that I don't think will help troubleshoot so I'm not typing them>

I've tried with both WinPE 4.0 and WinPE 5.0 without luck.

If I boot from the WinPE .iso then it loads just fine.

If I don't add the gui parameter after wimboot in my script then I get this message:

Get parameters: C/H/S = 1024/255/63, drives = 1
Get disk type: sectors = 0xfff80040, type = 3
Extensions installation check
<and 2 more lines>

Any ideas why it's failing?
So apparently the Error Code: 0x0000005C is a HAL issue. I tried using the boot.wim from WinPE v3.1 and it worked. Anything newer failed. Go figure. I would definitely like to use a newer version of WinPE so if anyone has any ideas on how to get a newer version of WinPE to boot on a Microsoft Hyper-V virtual machine, please do tell.
(2016-08-22 22:15)mojomatt Wrote: [ -> ]So apparently the Error Code: 0x0000005C is a HAL issue. I tried using the boot.wim from WinPE v3.1 and it worked. Anything newer failed. Go figure. I would definitely like to use a newer version of WinPE so if anyone has any ideas on how to get a newer version of WinPE to boot on a Microsoft Hyper-V virtual machine, please do tell.

same problem here Sad

same setup is ok with KVM or bare metal server, but failed with hyper-v.

thank to send it s work with winpe 3.1.

i test with many realease od wimboot and ipxe, and it wasn t good.

i need (like you i supose) new wim image, hope we can have it soon.
Reference URL's