WADS failed - wgetwads64.exe could not be launched
Published: July 8, 2022 - 2:42 PM
Good morning,
I have almost the same problem as @t.heroult, in the following ticket: viewtopic.php?t=3098
I am using WAPT Enterprise version 2.2.1.11957.
The server is running Debian 11 and the console is running Windows Server 2016.
I carried out a WADS deployment test, following the documentation, and it was successful.
A first Dell Latitude 5290 PC was successfully deployed (including an original Windows 10 version 21H2 image, a WAPT auto-configuration file provided by default for offline Djoin + addition of a local account with autologon).
Today I tried, in the same configuration, to deploy a Dell Latitude 5530 but the deployment is stopped at the WinPE stage, with no possibility of continuing.
As you can see in the photo, following the ping, the executable wgetwads64.exe is called and normally launches a new terminal and continues the installation.
In this case, a terminal appears briefly, but it closes immediately.
It's impossible to restart it manually; the same result occurs.
I end up with the following result if I restart without the "start"from the beginning:
I have already regenerated the WinPE version and it didn't help.
It's a shame, I have a small fleet of machines with Latitude 5530s that I can't deploy via WAPT, do you have a solution?
I have almost the same problem as @t.heroult, in the following ticket: viewtopic.php?t=3098
I am using WAPT Enterprise version 2.2.1.11957.
The server is running Debian 11 and the console is running Windows Server 2016.
I carried out a WADS deployment test, following the documentation, and it was successful.
A first Dell Latitude 5290 PC was successfully deployed (including an original Windows 10 version 21H2 image, a WAPT auto-configuration file provided by default for offline Djoin + addition of a local account with autologon).
Today I tried, in the same configuration, to deploy a Dell Latitude 5530 but the deployment is stopped at the WinPE stage, with no possibility of continuing.
- Error launching wgetwads64.exe
- q_wads_1.jpeg (247.64 KB) Viewed 1995 times
As you can see in the photo, following the ping, the executable wgetwads64.exe is called and normally launches a new terminal and continues the installation.
In this case, a terminal appears briefly, but it closes immediately.
It's impossible to restart it manually; the same result occurs.
I end up with the following result if I restart without the "start"from the beginning:
Code: Select all
VerifyCert: 0
An unhandled exception occurred at $0000000100002D02:
EAccessViolation: Access violation
$0000000100002D02
It's a shame, I have a small fleet of machines with Latitude 5530s that I can't deploy via WAPT, do you have a solution?