I think the simplest solution is to update the client configuration on each machine so that it points to the server's new port. Otherwise, they remain disconnected because they're trying to connect to the old port. If you have a lot of machines, this can be done via a script or...

Hi Clément,

For secondary repositories, there's no equivalent setting to `cleanup_kbs` on the main server. The only official way to purge packages is to manually delete the files or use a custom script that removes older versions.

Otherwise...

I think your solution with the scheduled task was simpler in the end. It avoids the problems with PsExec and ServiceUI, especially with antivirus software or EDR that can block it.

It looks like a signature or auto-matching issue in WinPE.
The driver is fine since it works manually, but WinPE doesn't load it automatically at boot, often because it's not properly signed for Windows 11 or isn't recognized as a boot-critical driver.
Also check that...

There was indeed a regression with WADS in version 2.6.0.17177. The next nightly build fixes this issue (WAPT-2.6.0.17198) by correctly adding the SecureStartup and EnhancedStorage packages to WinPE and fixing other deployment-related bugs. You can contact support to...

Hi Jean-Charles,
If the WAPT client displays a win32process error after updating to Windows 11 23H2, it's often due to an incomplete or interrupted installation. As you've noticed, manually reinstalling the agent usually fixes the problem.
The issue could stem from...

Yeah, Windows loves to play housekeeper in the Installer folder, especially with a disk cleanup or a third-party tool that goes haywire. It has nothing to do with WAPT; it's often a GPO or a maintenance script that's overzealous and deletes the MSI files without warning.
Personally, when I go through...