1. Frank Heeg
  2. PowerBuilder
  3. Thursday, 8 July 2021 12:09 PM UTC

We just recently upgraded to PB 2019 R2 and have begun rolling out our application to customers this last month and of the first 40 sites, 2 had runtime issues with TX13.dll because of Malwarebytes? Has anyone else had this issue and is there a better solution then dealing with each customer to change their Malwarebytes to ignore our installed code directory?  At this rate we'll have another 100 calls to our help center by the time we're done rolling out to all customers and really want to avoid this. 

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 8 July 2021 15:50 PM UTC
  2. PowerBuilder
  3. # 1

Hi Frank;

  I am not sure if this would appease the MalwareBites god's but the PB2019 R3 release can now use either version TX15 or version TX28 (32 & 64 bit) of this internal control to support RTE and RT DWO rich text based operations. Maybe Malwarebytes likes those newer TXxxxx.dll(s) better. Just a thought.

Regards ... Chris

There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 8 July 2021 17:04 PM UTC
  2. PowerBuilder
  3. # 2

Adding to what Chris said, until you are able to upgrade to PB 2019 R3 I would suggest you contact Malware Bytes and report this false positive.  At Appeon, we test PB runtime files against the top 20 Anti-Virus software and if we see their software reports false positive we report to them so the fix it.  Anti-Virus software are notorious for false positives when run in heuristics mode, which is when it's not looking for a known virus but rather guessing.

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.