Tranquil IT Forum

It's a Dell Precision 3640 desktop PC. When the computer boots and starts PXE, as you can see in my first screenshot, the PC retrieves the 10.xxx IP address that I reserved in my DHCP server on the net0 interface.

Once it starts the Windows installation environment, almost 90% of the time its IP address becomes an APIPA address. What I find surprising is that 10% of the time it keeps the correct IP address and the Windows installation continues normally.

Another problem: I don't know if it's related to WAPT or to my test machine, but I seem to get a BSOD randomly when starting the Windows installation environment with the error: DRIVER VERIFIER DMA VIOLATION

Hello florian777,

could you test with another PC model or another PC altogether, to better isolate the source of the problem?

I just tested it on another model and I'm not having any problems so far. I'll need to test it on another PC to see if the problem is with the computer itself or with the 3640 series

Hello Florian,
The problem may stem from missing drivers on the WinPE side.

Dell provides a specific driver package: https://www.dell.com/support/kbdoc/fr-f ...otes-winpe

It is possible to test this by adding them manually: https://docs.microsoft.com/en-us/window ... -customize

Hello,

I added the drivers, tried again, and it worked four times in a row, but now I'm having the problem again (I think it's a problem with the PC itself) because I tested it on another PC of the same model and it works fine.

While we're on the subject of deployment problems, I've encountered a few issues that appear randomly:
- When downloading the Windows ISO, when it reaches 100%, it keeps saying "Progress 100 of 100," and after 2 or 3 minutes, the window closes and nothing happens.

- When launching the command: "start x:\dlls\wgetwads64.exe --verify-cert=0 --server-url=https://ip_srv_wapt," the wgetwads64.exe window opens and closes immediately.

Hello,

regarding:
- when launching the command: "start x:\dlls\wgetwads64.exe --verify-cert=0 --server-url=https://ip_srv_wapt" the wgetwads64.exe window opens and closes immediately.

----------

I have the same problem. What I do is copy and paste

x:\dlls\wgetwads64.exe --verify-cert=0 --server-url=https://ip_srv_wapt

and the rest starts...
it's not ideal but it works

. Regards

Yeah, afterwards I have the impression that restarting the Wapt server is enough

x-davidl wrote: ↑Apr 26, 2022 - 2:52 PM I have the same problem. What I do is copy and paste

and the rest starts...
it's not ideal but it works well

Are you on version 2.2.1.11899?

We implemented a loop in wgetwads64.exe so that if the request to the server fails, we wait and then retry 10 times

If it continues to happen AND it doesn't crash just by restarting the command, then it might be something else.

In WinPE's start.cmd file, before launching wgetwads64.exe, we might need to add a timeout /t 5 just to give WinPE time to start properly

florian777 wrote: ↑Apr 26, 2022 - 3:25 PM Yeah, after that I have the impression that restarting the Wapt server is enough

I had a major problem at a client's the other day with a Windows server; the nginx for Windows (embedded in the wapt server for Windows) had a lot of trouble managing distributions in terms of throughput, no such problem with a Linux nginx server.

But the problem is not systematic on all Windows servers, so I wonder if there is an antivirus that is interfering with the Windows nginx server.

In the case of the previous client, the problem appeared overnight (cab on the Windows server?)

You may be in the same situation

I'll take a look

I wanted to know if there's a limit on the size of ISO files. With wgetwads64, I can download 6GB ISOs, but when I try with a 16GB ISO, the window closes as soon as it starts downloading