[RESOLVED] Packet with SHA error (corrupt) on 1% of the network

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
User avatar
t.heroult
Messages: 307
Registration: December 8, 2020 - 10:13 AM

March 24, 2022 - 11:16

Good morning

Since I switched to v 2.2 enterprise, I have some packages that work on 99% of the network without any problems, but on a few machines, I have corruption errors.
Example using a package to copy Sysinternals binaries:

Code: Select all

EWaptCorruptedFiles: Error in package Microsoft SysInternals Suite(=2022.1.27-4) in C:\Windows\TEMP\wapthwy4c3y9, files corrupted, SHA not matching for ['sysinternals/logonsessions.exe', 'sysinternals/handle.exe', 'sysinternals/handle64.exe', 'sysinternals/logonsessions64.exe']
I recompiled the package, but it didn't help; it still doesn't work a few machines only.
And I have this problem with a small handful of packages...
Last edited by t.heroult on March 24, 2022 - 11:34, edited 1 time.
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows

Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
High
User avatar
t.heroult
Messages: 307
Registration: December 8, 2020 - 10:13 AM

March 24, 2022 - 11:34

Okay, I understand, it's the antivirus (ESET) that's interfering!
It's deleting certain sysinternals files right when WAPT is decompressing and testing them...

Why does ESET block these files on some machines and not others? It's a mystery...
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows

Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
High
Locked

Return to “WAPT Packages”


  • To go further with WAPT