-
|
Hi, guys, I have an issue with a Windows installation that is working correctly for BIOS but not for UEFI. As you can see in the screenshots, everything related to UEFI seems to be loading fine, but towards the end, I get the message: "A required device isn't connected or can't be accessed."
boot.ipxe set server_ip 192.168.0.180 kernel tftp://${server_ip}/images/win2019/wimboot/wimboot |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
You do not need BCD or boot.sdi with latest versions of wimboot. Reading more carefully, your .wim is loaded as WinPE.wim (see your screenshot) the reason for this is that in efi mode you need the -n argument, while for pcbios the name is given after. Would probably work, however your screenshot is using http while your script says tftp, something is of here ;) |
Beta Was this translation helpful? Give feedback.
-
|
You are a genius NiKiZe, you saved my day. That worked fine. Good catch about http and ftp, one is my local and the other production (sorry). I will try without BCD and boot.sdi, thanks a lot! |
Beta Was this translation helpful? Give feedback.
You do not need BCD or boot.sdi with latest versions of wimboot.
Also try using a default boot.wim from Windows installation media.
Reading more carefully, your .wim is loaded as WinPE.wim (see your screenshot) the reason for this is that in efi mode you need the -n argument, while for pcbios the name is given after.
Would probably work, however your screenshot is using http while your script says tftp, something is of here ;)