Re: PAR::Packer generated EXE that was detected as a trojan...

It's not corruption. Think of pp as creating a self extracting executable. For a while pp installation failed for me on windows at the test phase, because rapidly creating exes which self extract and ran elsewhere on the system (a temp directory) triggered some rule within the AV product as something malicious. You could try specifying the target temp directory and maybe whitelist this within the product. This sort of thing has come up a few times (Sophos hates PAR::Packer!,Super Search for more). Do both systems use the same av version and definition file?

Comment on Re: PAR::Packer generated EXE that was detected as a trojan...

Replies are listed 'Best First'.
Re^2: PAR::Packer generated EXE that was detected as a trojan... by swl (Prior) on Sep 15, 2018 at 07:35 UTC
I get the same issues with Symantec Endpoint Protection. I added an exception for it in my system so it does not pester me now. Or possibly it is whitelisted in the upgrade I ran recently. Regardless, I installed PAR::Packer under Strawberry Perl 5.28.0 a few hours ago and there were no issues flagged by the AV system.	[reply]
Re^3: PAR::Packer generated EXE that was detected as a trojan... by vitoco (Hermit) on Sep 15, 2018 at 18:46 UTC
I installed a new Win7 x86 in VMWare with Strawberry Perl 5.28.0.1 and built my EXE using pp. Guess what? It was also detected as a trojan in my Win10 x64 machine by Windows Defender!!! As my real box has the same version of Strawberry Perl and can generate EXE files OK, without being detected as trojan by the same machine, I think that it is something to do with x86 versions of generated executables... I'll try the notification to Windows Defender team road.	[reply]