Problem Running with Eset NOD32

[Dartagnan]

Problem Running with Eset NOD32.   When I reboot - I cant start NOD32.   Eset told me I must turn of Malwarebytes Premium Web protection / Exploit protection / Malware protection / Ransomware protection.  Eset said I cant use any Live protection in order to run their antivirus program.

They said Malwarebytes is blocking Nod32 from running.  Is there a compatibility problem?

[Malwarebytes]

***This is an automated reply***

Hi,

Thanks for posting in the Malwarebytes 3 Help forum.

 

If you are having technical issues with our Windows product, please do the following: 

Spoiler

If you haven’t already done so, please run the Malwarebytes Support Tool and then attach the logs in your next reply:

NOTE: The tools and the information obtained is safe and not harmful to your privacy or your computer, please allow the programs to run if blocked by your system.

1. Download Malwarebytes Support Tool
2. Once the file is downloaded, open your Downloads folder/location of the downloaded file
3. Double-click mb-support-X.X.X.XXXX.exe to run the program
   • You may be prompted by User Account Control (UAC) to allow changes to be made to your computer. Click Yes to consent.
4. Place a checkmark next to Accept License Agreement and click Next
5. You will be presented with a page stating, "Get Started!"
6. Click the Advanced tab
   
    
7. Click the Gather Logs button
   
    
8. A progress bar will appear and the program will proceed with getting logs from your computer
   
    
9. Upon completion, click a file named mbst-grab-results.zip will be saved to your Desktop. Click OK
   
    
10. Please attach the file in your next reply. Before submitting your reply, be sure to enable "Notify me of replies" like so:
       

Click "Reveal Hidden Contents" below for details on how to attach a file:
 

Spoiler

To save attachments, please click the link as shown below. You can click and drag the files to this bar or you can click the choose files, then browse to where your files are located, select them and click the Open button.

 

One of our experts will be able to assist you shortly.

 

If you are having licensing issues, please do the following: 

Spoiler

For any of these issues:

• Renewals
• Refunds (including double billing)
• Cancellations
• Update Billing Info
• Multiple Transactions
• Consumer Purchases
• Transaction Receipt

Please contact our support team at https://support.malwarebytes.com/community/consumer/pages/contact-us to get help

If you need help looking up your license details, please head here: https://support.malwarebytes.com/docs/DOC-1264 

 

Thanks in advance for your patience.

-The Malwarebytes Forum Team

[Dartagnan]

Can you tell if MB is blocking Eset from starting?  Eset Nod32 is working now that I reinstalled it with MB protection turned off.

mbst-grab-results.zip

[1PW]

Hello @Dartagnan and

Malwarebytes 3 for Windows (MB3) is designed to run correctly with the AV applications of others.  This definitely includes the current release of ESET's NOD32.

Since that is a W7 x64 system, you may wish to do a temporary test and make the following folder exclusion in MB3: C:\Program Files\ESET\ESET Security

Continuing the test, the following files may be excluded from ESET NOD32:

1. C:\Program Files\Malwarebytes\Anti-Malware\assistant.exe
2. C:\Program Files\Malwarebytes\Anti-Malware\malwarebytes_assistant.exe
3. C:\Program Files\Malwarebytes\Anti-Malware\mbam.exe
4. C:\Program Files\Malwarebytes\Anti-Malware\MbamPt.exe
5. C:\Program Files\Malwarebytes\Anti-Malware\MBAMService.exe
6. C:\Program Files\Malwarebytes\Anti-Malware\mbamtray.exe
7. C:\Program Files\Malwarebytes\Anti-Malware\MBAMWsc.exe
8. C:\Windows\system32\Drivers\farflt.sys
9. C:\Windows\System32\drivers\mbae64.sys
10. C:\Windows\System32\drivers\mbam.sys
11. C:\Windows\System32\drivers\MBAMChameleon.sys
12. C:\Windows\System32\drivers\MBAMSwissArmy.sys
13. C:\Windows\System32\drivers\mwac.sys

This may also have the effect of future proofing both applications.  Also, please consider updating MB3 to the release version 3.7.1.2839.

Please let the forum know how the test went.  Thank you.

Edited February 20, 2019 by 1PW

[LiquidTension]

Hi Dartagnan,

There's no indication of Malwarebytes directly blocking ESET.

With ESET now correctly functioning, what happens if you enable all Real-Time Protection modules in Malwarebytes? Do you encounter any issues?

[Dartagnan]

1.  What do you mean exclude  the following folder exclusion in MB3: C:\Program Files\ESET\ESET Security ?  Do I pasted your file list in advanced setup exclusions???

2. I can start MB protection after I load the desktop.  But on reboot Eset won't start again without reinstalling.

 

 

[Dartagnan]

Do I just do the folder at first and then exclude the files later?   And there are 3 exclusion choices....Which one?

[1PW]

Hello @Dartagnan:

Please ignore my post and follow @LiquidTension's request in post #5 above.  Thank you.

[Dartagnan]

I can start MB protection after I load the desktop.  But on reboot Eset won't start again without reinstalling.

[LiquidTension]

Thanks for confirming.

Please start by getting the latest version of Malwarebytes installed (version 3.7.1). The installer can be downloaded using the following link:
https://downloads.malwarebytes.com/file/mb3

If you still encounter the same issue, please configure exclusions for ESET Security in Malwarebytes.

• Open Malwarebytes.
• Click Settings.
• Click Exclusions.
• Click Add Exclusion.
• Ensure Exclude a File or Folder is selected and click Next.
• Click Select Folder.
• Navigate to the C:\Program Files\ESET folder. Select the ESET Security folder and click Select Folder.
• Ensure the first option under How to Exclude is selected. Click OK.

 

Reboot the computer afterwards and check if the issue still occurs. If it does, please let us know.

[Dartagnan]

I can start MB protection after I load the desktop.  But on reboot Eset won't start again without reinstalling.

[Dartagnan]

Yesterday I went and excluded everything 

1. C:\Program Files\Malwarebytes\Anti-Malware\assistant.exe
2. C:\Program Files\Malwarebytes\Anti-Malware\malwarebytes_assistant.exe
3. C:\Program Files\Malwarebytes\Anti-Malware\mbam.exe
4. C:\Program Files\Malwarebytes\Anti-Malware\MbamPt.exe
5. C:\Program Files\Malwarebytes\Anti-Malware\MBAMService.exe
6. C:\Program Files\Malwarebytes\Anti-Malware\mbamtray.exe
7. C:\Program Files\Malwarebytes\Anti-Malware\MBAMWsc.exe
8. C:\Windows\system32\Drivers\farflt.sys
9. C:\Windows\System32\drivers\mbae64.sys
10. C:\Windows\System32\drivers\mbam.sys
11. C:\Windows\System32\drivers\MBAMChameleon.sys
12. C:\Windows\System32\drivers\MBAMSwissArmy.sys
13. C:\Windows\System32\drivers\mwac.sys

I will know in a couple of days if that fixes the problem.

[Dartagnan]

That didnt work.   I turned of ACTIVE protection in MB and rebooted.  Now Eset works

[exile360]

Hello,

Did you also exclude ESET's drivers in Malwarebytes along with its data folder(s) (likely located under C:\Windows\System32\drivers and C:\ProgramData respectively, and possibly under C:\Users\<your user name>\Application Data as well if ESET stores any local user data)?  If not, then I'd suggest giving that a try to see if it helps.

If that fails to resolve the issue then I would suggest trying the Delay Real-Time Protection when Malwarebytes starts option under Settings>Protection and configuring it at first to the default/lowest 15 seconds value, then rebooting to see if it helped, and if not, then try 30, 45 and so on until you find a value that works and hopefully putting it on a delay will resolve the issue and allow both products to function together.

[Dartagnan]

I will double check the exclusions and try the Delay also..............thanks

[exile360]

You're welcome.  Hopefully it helps, but I'll be reporting this issues to the Product team/Developers either way just in case there is an underlying issue there that requires further investigation.

[Dartagnan]

I turned of ACTIVE protection in MB and rebooted.  Now Eset works.

I also noticed I lost all the exclusions I made for the following:

1. C:\Program Files\Malwarebytes\Anti-Malware\assistant.exe
2. C:\Program Files\Malwarebytes\Anti-Malware\malwarebytes_assistant.exe
3. C:\Program Files\Malwarebytes\Anti-Malware\mbam.exe
4. C:\Program Files\Malwarebytes\Anti-Malware\MbamPt.exe
5. C:\Program Files\Malwarebytes\Anti-Malware\MBAMService.exe
6. C:\Program Files\Malwarebytes\Anti-Malware\mbamtray.exe
7. C:\Program Files\Malwarebytes\Anti-Malware\MBAMWsc.exe
8. C:\Windows\system32\Drivers\farflt.sys
9. C:\Windows\System32\drivers\mbae64.sys
10. C:\Windows\System32\drivers\mbam.sys
11. C:\Windows\System32\drivers\MBAMChameleon.sys
12. C:\Windows\System32\drivers\MBAMSwissArmy.sys
13. C:\Windows\System32\drivers\mwac.sys

The only exclusion I have now is C:/program files/eset/eset security   the folder.

NOTE: ESET told me to uninstall Malwarebytes because if causes conflicts and they insisted Eset won't work with Malwarebytes.  That was the end of the support I got from them. 

 

[Dartagnan]

These are the new exclusions I have set and also using a 120 second start delay.   I will know more tomorrow.

[exile360]

Excellent, there are also likely some drivers stored under C:\Windows\System32\drivers.  You can locate them by using a tool such as Microsoft Sysinternals Autoruns:

Locate drivers with Autoruns:

Please download Sysinternals Autoruns from here and save it to your desktop.

Note: If using Windows Vista, Windows 7, Windows 8/8.1 or Windows 10 then you also need to do the following:

Right-click on Autoruns.exe and select Properties
Click on the Compatibility tab
Under Privilege Level check the box next to Run this program as an administrator
Click on Apply then click OK

• Double-click Autoruns.exe to run it.
• Once it starts, please press the Esc key on your keyboard.
• Now that scanning is stopped, click on the Options button at the top of the program and verify that the following are checked, if they are unchecked, check them:

Hide empty locations
Hide Microsoft entries

• Optionally (mostly for future use if you ever decide to use it to hunt any possible infections or PUPs on your system), you may also click on the Options button at the top of the program and select Scan Options... then in the Autoruns Scan Options dialog enable/check the following two options:

Verify code signatures
Check VirusTotal.com

• Once that's done click the Rescan button at the bottom of the Autoruns Scan Options dialog and this will start the scan again, this time let it finish.
• When it's finished and says Ready. on the lower left of the program window, please click on the Drivers tab at the top of the program and scroll through the list to locate any drivers that show ESET for the Description and/or Publisher columns and then exclude each of those in Malwarebytes as well.

[Dartagnan]

Thanks.........I will try it sunday.

[exile360]

Sounds like a plan, I look forward to hearing back from you, hopefully with good news.

[IdefixPC]

Hello,

I don't know if my experience can help but I'm using MBAM premium real time alongside with ESET Internet Security without ant problem.

[Dartagnan]

These are the new exclusions I have set and also using a 120 second start delay.   

But the only way I can get Eset to load at boot up is to have MB Active Protection turned off before I shutdown.

If it is off Eset loads on bootup.  Then I can turn Active Protection on while working.  But I must turn it off before shutdown each time.

[exile360]

Well that's disappointing, but thank you for letting us know.  I will be certain to document this for the team so that they may begin trying to replicate this issue, and hopefully the Developers will be able to work out a fix for it.

[Dartagnan]

These are the new exclusions I have set and also using a 180 second start delay.   

But the only way I can get Eset to load at boot up is to have MB not load at startup.

If it is off Eset loads on bootup.  Then I can turn Active Protection on while working. 

I tried 3 reboots today.........and when I turned MB off during startup---Eset loaded.