I finally bypassed the problem by using the run command rather than install_msi_if_needed.

Hello,

I'm having the same problem creating a package. Have you found a solution? It would help us a lot.

Regards,

Manuel.

Hello,

I finally managed to resolve this issue simply by uninstalling and reinstalling the agent on the affected machines.

After further consideration, I think the problem stems from the presence of the hash in the command used to create the scheduled task. Perhaps the agent was installed...

Hello,

my problem persists and only affects 4 workstations out of almost 200. It seems these 4 workstations are also refusing the deployment of the new agent in version 1.8, which has to be installed manually. I'm giving up for now, but if anyone has any ideas or is facing the same problem, I would be very grateful...

Hello,

I just upgraded our WAPT server to version 1.8.2 (Community / Debian 4.19.0-6-amd64). The agent and waptupgrade update went smoothly on several dozen machines in our network (mostly Windows 10), but four of them (Windows 10 Pro) are stuck on the update...