Page 1 of 1
[SOLVED]PXE error: Nothing to boot: no such file or directory
Published: June 9, 2022 - 2:41 PM
by Erman
Hello,
I'm trying to set up a deployment using WAPT 2.2. However, I'm encountering an error when my client PCs boot via PXE in BIOS:
And here's the error message when the clients are in EFI mode:
I'm using Windows Server for my DHCP (for DHCP settings, EFI: ipxe.efi / BIOS: undionly.kpxe).
I consulted the 2.2 documentation and this answer:
viewtopic.php?p=9879#p9879
Thank you.
Re: PXE error: Nothing to boot: no such file or directory
Published: June 13, 2022 - 11:31
by sfonteneau
For me, it's a DHCP configuration issue.
I've published the PowerShell commands directly if you'd like them:
https://www.wapt.fr/fr/doc/wapt-wads-tf ... hcp-server
You can delete the manually created configurations and then run the PowerShell commands on your DHCP server.
Re: PXE error: Nothing to boot: no such file or directory
Published: June 14, 2022 - 11:07 AM
by Erman
Hello,
Version: WAPT 2.2.1.11957
Server OS: Windows 2012 server
ISO distributed: Windows 10
You were right, it was a DHCP server issue. Now I'm facing another problem. I correctly register my PC with the WAPT server, the deployment starts, the CMD window displays this command, and then does absolutely nothing afterward. Do you have any suggestions?
I found this forum post
viewtopic.php?t=2989 which corresponds to my problem, but I still haven't found a solution.
Regards,
Erman
Re: PXE error: Nothing to boot: no such file or directory
Published: June 14, 2022 - 11:15
by sfonteneau
You can rerun the last command that appeared (without the start button).
The start button actually allows you to use the French keyboard layout, but it also hides errors.
Re: PXE error: Nothing to boot: no such file or directory
Published: June 14, 2022 - 11:22
by Erman
Hello,
I've encountered yet another error message. I think it's a problem with the ISO image...

(open the image in a new tab to see it more clearly)
Regards,
Erman
Re: PXE error: Nothing to boot: no such file or directory
Published: June 14, 2022 - 12:31
by sfonteneau
Yes, indeed.
The hash of the downloaded ISO doesn't match the advertised hash.
Your Windows 10 ISO is only 3.1 GB? There might have been a problem during the ISO upload?
The filename, and therefore the URL, corresponds to the SHA256 hash, so clearly the file's hash doesn't match.
Therefore, either there was a problem during the upload, or there was a problem during the download via WADs.