When I have installations that crash due to error 1603, in 99.99% of cases, the problem is solved like this:
- Go to HKEY_CLASSES_ROOT\Installer\Products (or HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products, it's the same)
- Find the key that corresponds to the software
- Delete the key...

Thanks, I'll check it out.
But if a fix is ​​planned, I think I won't waste time and will just wait.

We have withsecure across the entire network.
It's the same agent version on all workstations, regardless of whether the packet gets through or not.

Hello,
I have the same problem with Edge and Chrome.
In short:
The package fails on some machines.
I recompile the package, and then it works on some machines where it didn't before, and fails on others where it worked fine.
Basically, it's completely random!

Great, it worked!
Thank you so much

Good morning
After the console asked me to recreate WinPE, I get this message when starting the deployment. Any idea what's wrong?

Thanks, Gwenaël helped me with a ticket and it works

Hello,
following the update to the latest version, it's no longer possible to deploy via WADS. The PXE boot waits and then fails.
We've tested it with several PCs.
There's an error message, but it's too short to read.
On the server, the wapttftpserver service is running correctly.

Thank you...

For several weeks now (even with the latest version), I've occasionally been getting "Invalid Variant Type" errors after installing WUA on Windows 11 24h2 machines.

Any idea what could be causing this?

The previous version of waptdeploy.exe gives the same result.
Modifying the GPO using cmd /C works.