Tranquil IT Forum

In fact, the BIOS itself can sometimes retrieve an IP address...

Yes, we are using IPXe; here is the configuration that has worked until now.

However, I can confirm that with the latest version of WinPE, certain types of hardware are no longer supported. To test this, I used a very old version of WinPE:

C:\Users\username\Downloads\tis-wads-requirement-minimal-x64_10.1.25398.1-36_windows_PROD\amd64\en-us
https://wapt.tranquil.it/store/fr/wapt/ ... _PROD.wapt

But I can confirm that ipconfig must display an IP address (it's mandatory).

I'm sorry, but I'll need some explanation on how it works.
We launched an OS deployment on one machine, on a second machine we did a ping -t to the machine being deployed (sorry for the image quality). During these phases, the ping is OK.

I suppose we're still in the PXE phase; everything is OK for the moment.

Then, at this stage, the ping fails and the ipconfig command returns nothing. At this stage the machine attempts to download the network drivers from the WAPT server, is that correct?

One more piece of information: when you create a WinPE key with Wapt, the deployment works fine.

I'm adding information as I discover more...

Affected machines:
HP PROBOOK 650-G5 (hardware purchased in 2020)
LENOVO THINKPAD P16v GEN3 ( hardware purchased in December 2025)

With the package:
- tis-wads-requirement-minimal-x64 in v10.1.25398.1-36 - OS deployment: OK
- tis-wads-requirement-minimal-x64 in v10.1.26100.2454-40 - OS deployment: OK
- tis-wads-requirement-minimal-x64 in v10.1.28000.1-40 - OS deployment: NOK

The latest version of wads-requirement seems to be the source of all the problems.

Hi Cédric,

WinPE must have started initially because spnonly.efi is downloaded using the network driver integrated into the UEFI layer. WimBoot, which is downloaded afterward, along with the bootloader and the WIM image, must also go through this same UEFI driver.

It seems that in your case, the driver isn't recognized in the WinPE image, which is why there's no address in ipconfig even though the machine booted over the network.

The Wapt version update includes an update for IPXE and WimBoot, but it shouldn't affect the WinPE drivers. However, if you've updated wads-requirement-minimal, there was a recent update from Microsoft that we've integrated, and that might help get things working.

However, the latest version of Microsoft WinPE has dropped support for a lot of older hardware, so we'll probably have to allow both to be used simultaneously.

Regards,

Denis

clafon wrote: ↑Dec 16, 2025 - 4:43 PM - tis-wads-requirement-minimal-x64 in v10.1.25398.1-36 - OS deployment: OK
- tis-wads-requirement-minimal-x64 in v10.1.28000.1-40 - OS deployment: Nok

I simply think that version 10.1.28000 no longer includes certain drivers and that they need to be added when generating WinPE.

sfonteneau wrote: ↑Dec 16, 2025 - 4:52 PM

clafon wrote: ↑Dec 16, 2025 - 4:43 PM - tis-wads-requirement-minimal-x64 in v10.1.25398.1-36 - OS deployment: OK
- tis-wads-requirement-minimal-x64 in v10.1.28000.1-40 - OS deployment: Nok

I simply think that version 10.1.28000 no longer includes certain drivers and that they need to be added when generating WinPE.

This is the same procedure we have been using from the beginning; as mentioned, we manually added the LOS drivers from the WinPE generation.

@sfonteneau @dcardon

I understand your feedback, but we tested with both older equipment (purchased in 2020) and newer equipment (purchased in December 2025).
We also manually added the network drivers for the equipment when we created the WinPE installation.
The latest version of the WADS package seems to be causing the problem.