Adding Prevx to AV exclusions

[BoerenkoolMetWorst]

I want to add Prevx to the exclusion list from the realtime scanning of my AV. What files do I need to add?
(I presume it is not just prevx.exe as with MBAM it was not just mbam.exe but this whole list:
C:\Program Files\Malwarebytes' Anti-Malware\mbam.exe
C:\Program Files\Malwarebytes' Anti-Malware\mbamgui.exe
C:\Program Files\Malwarebytes' Anti-Malware\mbamservice.exe
C:\Program Files\Malwarebytes' Anti-Malware\zlib.dll
C:\Program Files\Malwarebytes' Anti-Malware\mbam.dll
C:\Program Files\Malwarebytes' Anti-Malware\mbamext.dll
C:\ProgramData\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref
C:\Windows\System32\drivers\mbam.sys
C:\Windows\System32\drivers\mbamswissarmy.sys)

[Triple Helix]

Is there any reason why you would want to? I don't with NOD32 as they compliment each other very well and I don't find any slow down! Just curious. ;)

TH

[vonvon]

It can be usefull for exemple with Dr. Web : it killed Prevx in one second. I had to put in exclusion of spider guard (realtime monitoring):

c:\program files\prevx\prevx.exe
c:\windows\system32\PxSecure.dll
pvxinst*


and the same for scan unit.

This information from Dr.Web support.

Best regards, Vonvon

[Triple Helix]

-{ Quote: "It can be usefull for exemple with Dr. Web : it killed Prevx in one second. I had to put in exclusion of spider guard (realtime monitoring):

c:\program files\prevx\prevx.exe
c:\windows\system32\PxSecure.dll
pvxinst*


and the same for scan unit.

This information from Dr.Web support.

Best regards, Vonvon" }-

Really why would it delete a legit security program NOD32 doesn't do that on my system or VIPRE AV on my VM's with Prevx also?

TH

[vonvon]

I don't know why ...

I never had a problem with Kaspersky or Rising working with Prevx.

But now, Dr.Web works perfectly with Prevx.

Vonvon

[Triple Helix]

-{ Quote: "I don't know why ...

I never had a problem with Kaspersky or Rising working with Prevx.

But now, Dr.Web works perfectly with Prevx.

Vonvon" }-

They mussed of detected the RC's changes as NOD32 did at one time but now all new versions not a peep from NOD32 anymore! You can send the Prevx.exe file to the respective AV's that you use to stop detection as advised by PrevxHelp awhile back!

TH

[vonvon]

I will make that, thank you.

[Triple Helix]

-{ Quote: "I will make that, thank you." }-

Your welcome and I hope it works for you! If there any new RC's you will probably will have to send the setup file again!

Just to let you know that few of us complained on the ESET forum to get them to stop detecting every new version that came out and it finally worked! :thumb:

TH

[vonvon]

-{ Quote: "Just to let you know that few of us complained on the ESET forum to get them to stop detecting every new version that came out and it finally worked! " }-

Why not ?

Interesting

[Triple Helix]

-{ Quote: "Why not ?

Interesting" }-

Sorry was that a Question for me?

TH

[BoerenkoolMetWorst]

-{ Quote: "Is there any reason why you would want to? I don't with NOD32 as they compliment each other very well and I don't find any slow down! Just curious. ;)

TH" }-

Just to be on the safe side, and keep my security as light as possible. Not noticing issue's doesn't necessarily mean they don't exist, and double scanning happens a lot with complementary security or on demand scanners. Try a full scan with MBAM, SAS or any other product while watching Eset's last scanned item from the real-time shield and you'll see that it scans every file the on demand scanner accesses, so your actually also running a system scan with Eset, and thus the time necessary to complete it will be a lot longer. Of course Prevx doesn't scan that many files and works differently, but still, even minimal improvements are nice :)

[Triple Helix]

-{ Quote: "Just to be on the safe side, and keep my security as light as possible. Not noticing issue's doesn't necessarily mean they don't exist, and double scanning happens a lot with complementary security or on demand scanners. Try a full scan with MBAM, SAS or any other product while watching Eset's last scanned item from the real-time shield and you'll see that it scans every file the on demand scanner accesses, so your actually also running a system scan with Eset, and thus the time necessary to complete it will be a lot longer. Of course Prevx doesn't scan that many files and works differently, but still, even minimal improvements are nice :)" }-

Very true each user likes to use there system there way and I agree with you 100%! :thumb: To tell you the truth with NOD32 & Prevx running realtime I only do monthly Quick scans with MBAM & SAS and SAS only finds cookies for me! LOL

If you still need every file to exclude I will leave that up to the people that know! ;)

TH

[vonvon]

-{ Quote: "Why not ?

Interesting

Sorry was that a Question for me?
" }-
Sorry, the "why not" was why not nod 32 in the future ? It looks fine. I don't know this product but I will try it.
Best regards, Vonvon

[Triple Helix]

-{ Quote: "Sorry, the "why not" was why not nod 32 in the future ? It looks fine. I don't know this product but I will try it.
Best regards, Vonvon" }-

OK great sounds good to try different things at times :thumb:

Regards,

TH

[BoerenkoolMetWorst]

PrevxHelp, do you know what files I need to put on the exclusion list?

[MeFer]

I put OA and other securities to Detection Overrides,but every boot time Prevx scanning OA's all drivers and datas:(

[PrevxHelp]

-{ Quote: "I put OA and other securities to Detection Overrides,but every boot time Prevx scanning OA's all drivers and datas:(" }-

Could you please create a scan log by clicking Tools - Save Scan Results and send this to report@prevxresearch.com? We will centrally add OAs files to the overrides to provide faster scanning :)

[PrevxHelp]

-{ Quote: "PrevxHelp, do you know what files I need to put on the exclusion list?" }-

You shouldn't really be required to add any files to their override lists unless they have some false positive against us, however, the complete list of binary files within Prevx is:

C:\Program Files\Prevx\prevx.exe
C:\Windows\System32\pxsecure.dll
C:\Windows\System32\Drivers\pxscan.sys
C:\Windows\System32\Drivers\pxrts.sys
C:\Windows\System32\Drivers\pxkbf.sys

In the event that another AV is finding our quarantine cache, you may want to add qc.csi from our appdata folder (C:\Documents and Settings\All Users\Application Data\PrevxCSI\qc.csi on XP or C:\ProgramData\PrevxCSI\qc.csi on Vista/7)

Let me know if you have any other questions! :)

[papillonn]

When you update prevx or when you install it, my dr.web block pvxins* files so we can add pvxins* files to your list PrevxHelp.

[MeFer]

-{ Quote: "Could you please create a scan log by clicking Tools - Save Scan Results and send this to report@prevxresearch.com? We will centrally add OAs files to the overrides to provide faster scanning :)" }-

Thanks,i sent and adding here may be help other users.