OS Deployment - Freeze

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
clafon
Messages: 109
Registration: Nov 06, 2024 - 10:56

January 20, 2026 - 11:09

WAPT Version: 2.6.1.17654
Server OS: Debian 12
Administration Machine OS: Windows Server 2019
Target Machine OS: Windows 11

Hello,

We just received new workstations (HP ProBook 4 G1IR 16) and we are unable to deploy Windows 11 with WAPT.
We have correctly added the network drivers to WinPE.
The workstations freeze once WinPE is selected (Register Host WinPE x64), when it is on:
media/EFI/Microsoft/Boot/BCD...ok
media/Boot/boot.sdi... ok
media/sources/boot.wim... 3%

Have you encountered this problem? Thank you
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 20, 2026 - 1:26 PM

Hello,

are you using ipxe.efi or snponly.efi?
clafon
Messages: 109
Registration: Nov 06, 2024 - 10:56

January 20, 2026 - 1:44 PM

I would say ipxe
Screenshot 2026-01-20 134348.png
Screenshot 2026-01-20 134348.png (23.07 KB) Viewed 13166 times
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 20, 2026 - 2:55 PM

No, you're currently using "snponly.efi"

, so it's using the HP firmware's UEFI (SNP) network stack.

You can try switching to "ipxe.efi" as the value instead of "snponly.efi";

this will use the native iPXE driver.

Normally, the opposite is often better, but anyway...
clafon
Messages: 109
Registration: Nov 06, 2024 - 10:56

January 20, 2026 - 5:18 PM

Tested with IPXE but same problem...
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 21, 2026 - 09:35

I don't have much to test here because I don't have your model

Another idea to try:

You can run this command on your Wapt server:

Code: Select all

/opt/wapt/waptserver/scripts/compile_ipxe.sh
This will retrieve the latest commit from the IPXE GitHub repository https://github.com/ipxe/ipxe then compile the latest version (this may take a while)

This will compile custom IPXE files for you:

Code: Select all

ls -l /var/www/wads/pxe/*custom*
-rw------- 1 wapt www-data 1042944 Oct 30 12:24 /var/www/wads/pxe/ipxe_custom.efi
-rw------- 1 wapt www-data  209920 Oct 30 12:24 /var/www/wads/pxe/snponly_custom.efi
-rw------- 1 wapt www-data   71685 Oct 30 12:24 /var/www/wads/pxe/undionly_custom.kpxe
In your DHCP settings, you can try using ipxe_custom.efi or snponly_custom.efi

If it doesn't work, then it would seem to be a problem in IPXE.

In that case, consider switching to a pure TFTP Windows configuration:

https://www.wapt.fr/fr/doc/wapt-wads.ht ... figuration

This mode no longer uses IPXE
clafon
Messages: 109
Registration: Nov 06, 2024 - 10:56

January 22, 2026 - 11:04

Hello Simon,

So I followed the given procedure:
  • /opt/wapt/waptserver/scripts/compile_ipxe.sh
  • In DHCP, modify the PXE option to snponly_custom.efi
The PXE is no longer working at all. The workstations can no longer "connect" to the PXE
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 22, 2026 - 11:24

clafon wrote: Jan 22, 2026 - 11:04 AM The PXE is no longer working at all. The workstations can no longer "connect" to the PXE.
On no PC?
clafon
Messages: 109
Registration: Nov 06, 2024 - 10:56

January 22, 2026 - 11:41

none
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 22, 2026 - 1:46 PM

Does the file actually exist?

Code: Select all

ls -l /var/www/wads/pxe/*custom*
Answer