Tranquil IT Forum

WAPT Version: 2.6.0.16937 - Enterprise Edition
Server OS: Debian 12
Target Machines: Windows
OS Administration Machine: Windows Server 2022

Hello,

we have just upgraded our WAPT version to 2.6.0.16937. It appears that the drivers we added to the WinPE of the previous version (2.6.0.16881) were not retained, which is quite problematic. Is this normal behavior?

Thank you.

Hello,

Currently there isn't really a "lightweight" way to do this, since the drivers are injected into the WinPE using the DISM command, which is then sent to the server.

However, there's a little "extra" to make it a bit easier.
If you create a new driver bundle and name it "winpe" (as long as the bundle name contains "winpe"),
and then add drivers from the deployment section when creating the WinPE, it will automatically filter the available bundles containing the term "winpe".
Then, following the usual procedure, you confirm your selection, which will download the drivers locally for insertion with DISM when the WinPE is validated.

We'll look into this to see how we can further simplify and improve this part.

Yes, we were using the "+" button, but it came at a bad time: we were upgrading our computer equipment (new PC, new model, new brand, which requires adding drivers to WinPE) and upgrading Wapt.

We just wanted to know if we had missed a step (like the ability to export WinPE, for example).
Thanks for the feedback

Hi Cédric,

thanks for the feedback. I'm closing this thread, and we'll look into how to simplify driver re-injection during upgrades internally.

Regards,

Denis