Hello,
I'm following up on the incorrect flagging of waptagent.exe.
I assume it's normal that waptexit.exe, which originates from waptagent.exe 2.6.1.17787, also has its signature tagged as a threat, and that it can be safely whitelisted?
Check
waptexit.exe using VirusTotal:
Avast
FileRepMalware [Misc]
AVG ...
The search returned 4 results
- May 21, 2026 - 09:53
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: [SOLVED] Waptagent deployment issue
- Answers: 20
- Views : 17667
- March 6, 2026 - 2:53 PM
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: [SOLVED] Waptagent deployment issue
- Answers: 20
- Views : 17667
Re: Waptagent deployment problem
Hello,
I'm having the same issue with GPO deployment (startup script type) using waptdeploy.exe since this version.
The latest version, 2.6.1.17765, doesn't seem to resolve the problem either.
When I manually run waptdeploy directly on the client, the installation works. ;)
Best regards...
I'm having the same issue with GPO deployment (startup script type) using waptdeploy.exe since this version.
The latest version, 2.6.1.17765, doesn't seem to resolve the problem either.
When I manually run waptdeploy directly on the client, the installation works. ;)
Best regards...
- May 22, 2018 - 11:01
- Forum: WAPT Server
- Subject: [RESOLVED] Upgrade 1.3 -> 1.5 Community Code signing not found
- Answers: 3
- Views : 3490
Re: Upgrade 1.3 ->1.5 Community option Code signing not found
Okay, indeed, I continued and everything worked correctly. Thank you!
However, with the renaming of the machine packages, I have the new package with its UID for each machine, for example:
"Package UID number" host package for pc-124.mydomain...
The old package is simply named with its FQDN n...
However, with the renaming of the machine packages, I have the new package with its UID for each machine, for example:
"Package UID number" host package for pc-124.mydomain...
The old package is simply named with its FQDN n...
- May 18, 2018 - 4:11 PM
- Forum: WAPT Server
- Subject: [RESOLVED] Upgrade 1.3 -> 1.5 Community Code signing not found
- Answers: 3
- Views : 3490
[SOLVED]Upgrade 1.3 ->1.5 Community Code signing not found
Hello,
I just upgraded from version 1.3 to 1.5 Community on Debian 9.
After installing it on the Linux side, I proceeded to the WAPT console on Windows.
When I start the console, a message appears saying that the WAPT agent version is 1.3.13 and the console version is 1.5...
I just upgraded from version 1.3 to 1.5 Community on Debian 9.
After installing it on the Linux side, I proceeded to the WAPT console on Windows.
When I start the console, a message appears saying that the WAPT agent version is 1.3.13 and the console version is 1.5...
