iPXE discussion forum
WinPE 7f048283 - Printable Version

+- iPXE discussion forum (https://forum.ipxe.org)
+-- Forum: iPXE user forums (/forumdisplay.php?fid=1)
+--- Forum: General (/forumdisplay.php?fid=2)
+--- Thread: WinPE 7f048283 (/showthread.php?tid=12877)



WinPE 7f048283 - kovacsadam07 - 2018-08-22 16:38

Hi,

I have a working ipxe environment, I can boot Live Debian, WinPE, iSCSI boot Win10 etc. Currently I have problems with an Acer Iconia W4 820 tablet. I boot iPXE from a pendrive and give network through ecm (cause it has no ethernet interface). It can boot my menu but I can't successfully boot WinPE. It loads all the WinPE files as usual but at the end it gives error code 7f048283.
At the beginning the tablet could not even load iPXE (sudo make bin-x86_64-efi/ipxe--acm--ecm--ncm--axge.efi) although it has a 64bit Z3740 processor. Finnaly I managed to work with bin-i386-efi/ipxe--acm--ecm--ncm--axge.efi
Because of this I created a 32bit version WinPE. It does boot as a usb flash drive but when I start with ipxe it gives me
Could not boot: Error 0x7f048283
Could not boot image: Error 0x7f048283


RE: WinPE 7f048283 - NiKiZe - 2018-08-22 21:16

Is that an error from iPXE? if it is what is the full error message (it always includes an url to ipxe.org)

Have you made sure Secure Boot is disabled?
I'm assuming you are using wimboot, have you made sure that your wimboot is 32bit? (en efi all stages must match)


RE: WinPE 7f048283 - kovacsadam07 - 2018-08-22 21:37

(2018-08-22 21:16)NiKiZe Wrote:  Is that an error from iPXE? if it is what is the full error message (it always includes an url to ipxe.org)

Have you made sure Secure Boot is disabled?
I'm assuming you are using wimboot, have you made sure that your wimboot is 32bit? (en efi all stages must match)

Thank you for your answer! The url is http://ipxe.org/err/7f048283

You must be right! I use wimboot and it is 64bit... Unfortunately I can only test it after tomorrow. I will write back as soon I tried it.


RE: WinPE 7f048283 - kovacsadam07 - 2018-08-24 11:03

The problem was indeed the 64bit wimboot, 32bit wimboot solved the problem. Thank you NiKiZe for you help!