1. Cory Johnson
  2. PowerBuilder
  3. Wednesday, 3 March 2021 21:58 PM UTC

I've started migrating my PB 2019 R2 applications to R3, and the majority of them (but not all) are getting flagged and quarantined by McAfee.  I am in the process of getting exceptions setup for them all, but why is this a problem all of a sudden? I had no issues with R2, and the R2 exes are still working fine.

 

Cory

 

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 3 March 2021 22:27 PM UTC
  2. PowerBuilder
  3. # 1

Hi Cory;

  Appeon tests with the McAfee AV during our GA QA testing. So this is surprising. Try updating your AV definitions.

Regards ... Chris

Comment
There are no comments made yet.
Cory Johnson Accepted Answer Pending Moderation
  1. Wednesday, 3 March 2021 22:34 PM UTC
  2. PowerBuilder
  3. # 2

I did, and after a couple iterations of updating McAfee, trying to run the exe, it getting quarantined, putting the exe back, etc. it finally lets it go, but I don't expect my end users to understand or have to do that kind of process.

Comment
  1. Chris Pollach @Appeon
  2. Wednesday, 3 March 2021 22:37 PM UTC
When you compile the EXE - do you include a "Manifest" in the EXE (via the Project Painter)?
  1. Helpful
There are no comments made yet.
Cory Johnson Accepted Answer Pending Moderation
  1. Thursday, 4 March 2021 01:08 AM UTC
  2. PowerBuilder
  3. # 3

No I don't include a manifest

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 4 March 2021 01:42 AM UTC
Try the "built in" manifest option. I've been using that as my standard W10 EXE target compile option for over 6 years now.
  1. Helpful
There are no comments made yet.
Julie Jiang @Appeon Accepted Answer Pending Moderation
  1. Thursday, 4 March 2021 05:40 AM UTC
  2. PowerBuilder
  3. # 4

Hi Cory,

Our team further checked today but still found that the app .exe compiled in 2019 R3 won't be quarantined by McAfee. The attached screenshots show the McAfee version information used by our engineering team. 

If the problem persists at your side, please kindly send to product@appeon.com the following information: your McAfee version information and VirusScan information (similar to the attached screenshots); the error screenshot; the log files from McAfee.

Best regards, Julie

 

 

Attachments (5)
Comment
There are no comments made yet.
Cory Johnson Accepted Answer Pending Moderation
  1. Thursday, 4 March 2021 14:44 PM UTC
  2. PowerBuilder
  3. # 5

No change with the manifest compiled in.  I've attached a couple examples of the errors I'm getting, with the most recent one from this morning being the exe with the manifest compiled in.  In the meantime I've asked the security team to add exceptions for all our PowerBuilder executables

Attachments (1)
Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 4 March 2021 17:17 PM UTC
  2. PowerBuilder
  3. # 6

Like this ...

Comment
There are no comments made yet.
Cory Johnson Accepted Answer Pending Moderation
  1. Thursday, 4 March 2021 18:31 PM UTC
  2. PowerBuilder
  3. # 7

@Chris, that is how I had the manifest properties set, and I also tried 'Highest Available' for giggles, with the same result.  I'm in the process of gathering the information Julie asked for and will send it to her probably tomorrow

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 4 March 2021 19:29 PM UTC
Thanks for trying that Cory!

Have you tried using the W10 "Troubleshoot Compatibility" mode feature (RHMB the PB App's EXE)?
  1. Helpful
There are no comments made yet.
Cory Johnson Accepted Answer Pending Moderation
  1. Thursday, 4 March 2021 20:15 PM UTC
  2. PowerBuilder
  3. # 8

When I do the 'test the program...' McAfee eats the exe

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 4 March 2021 20:52 PM UTC
Ahhh ... I see! Please follow Julie's response suggestion OR open a Support Ticket for this issue.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.