Bitdefender Compatability

[tjwoosta]

Not sure if this is the right place to post this, so sorry in advance.

 

I installed Immunet after installing Bitdefender antivirus free version. Immunet detects that Bitdefender is installed and lists it on the lower left side which leads me to believe that the two should be compatible.

 

Now the problem is that whenever Bitdefender's active protection shield scans something new it seems to create a bunch of temporary files in C:\Windows\Temp\tmp0000####\ (#### is always a different string of numbers after each restart), and Immunet always quarantines them even when the files Bitdefender is scanning are clean.

 

Some of them are successfully quarantined by Immunet with seemingly no negative consequences other than cluttering up my quarantine, and others say "quarantine failed" and upon inspecting the Immunet history I see that it says they are "Installed By" C:\Program Files\Bitdefender Antivirus Free\vsserv.exe which is how I know they belong to Bitdefender.

 

I would just make an exception, but like I said the temp folder it uses changes after every restart.

Edited March 18, 2017 by tjwoosta

[iTrendsNET]

Good day, tjwoosta:

 

I believe the recommended procedure for any time more than one security program is installed on a computer is to exclude the working folder from the scans of the other program.

 

So, set up Immunet to not scan the Bitdefender working folders and set Bitdefender to not scan the usual Immunet working folders. That should resolve any concerns.

[tjwoosta]

Thats the problem, Bitdefender generates a different temp folder after every restart.

Edited March 18, 2017 by tjwoosta

[iTrendsNET]

OK, sorry for not catching that! Personally, I would remove Bitdefender free and go with something else, but that may not be the answer you are looking for. 

[ritchie58]

Hi guys, yeah, excluding the entire Program Files folder for BitDefender should have eliminated any conflicts. I would assume you already createad an exclusion for BitDefender's entire Program Files folder with Immunet & the temp files are still being quatantined, is that correct tjwoosta?

 

I would extrapolate that Immunet is quarantining the temp files that BitDefender is using to update it's malware definition signatures, seeing them as suspicious or possibly malicious. I would not recommend that you create a generic exclusion rule for the entire Windows temp file directory however. The temp files can sometimes be used by malware as an attack vector to infiltrate your system. So it is important that these files do get scanned as soon as they are created. Something that Immunet does for you automatically. Unfortunately this feature works too good sometimes so it would seem.

 

Not a bad idea to create a exclusion/exception rule for Immunet's Program Files folder with BitDefender too. Just wanted to mention that.

Let us know if you continue to encounter this issue. I may have you send Support a Diagnostic Tool Report to alert them of this compatibility issue with BitDefender.
 

Best wishes, Ritchie...

[newyorkjet]

Bitdefender Free is a stripped down version with very few user choices. I cannot see a way to create exception/exclusion rules in Bitdefender Free.

 

Bitdefender Free does flag up Immunet tmpscan in my rig which is a nuisance.

[ritchie58]

Thanks for the input newyorkjet. Wow! You can't even create your own exclusion rules with this latest incarnation of this software anymore? That's got to be disconcerting to the folks that have used this program in the past.

Older versions of BitDefender seemed to be compatible with Immunet. Perhaps, as you say, this newest version is not since they changed it so much! Mmm.

[newyorkjet]

An update to my earlier post, but first some background.

 

I loaded the combination of Immunet and Bitdefender Free on one of my systems after reading the PC Security Channel's glowing report:

 

 

I decided to exclude windows\temp from Immunet scanning on the basis that the Bitdefender engine would still cover it. The result is a much calmer system, albeit slightly less secure.

[ritchie58]

Interesting vid newyorkjet! Glad you found a adequate workaround but, like I did mention and you pointed out, excluding the entire Windows Temp file directory does leave you a little more vulnerable. I hope you're right about BitDefender scanning those files on a regular basis instead. Also glad too see you "can create" your own custom exclusion rules with BD. Don't forget to exclude each other's Program Files folders!

 

It's also interesting that the old Immunet Plus (which is not longer available) had the TETRA module which used a licensed, highly customized, advanced version of BitDefender's detection engine. This feature is still available for Immunet's enterprise version called AMP for Endpoints (or FireAMP Connector).

Best wishes, Ritchie...

[SMV]

Tested Immunet and Bitdefender combo yesterday and the problem still hasn't been fixed.

[ritchie58]

If you read the other threads to this topic this question may be a bit redundant but... Have you created exclusion rules for the Program Files folders with both programs? Also, what build of Bitdefender are you referring to?

[SMV]

I excluded Immunet's folder in Bitdefender and Bitdefender's folder in Immunet. If I exclude the temp folder both products work fine - the same as the others reported. I was hoping there would be a solution at this point. I'm using Bitdefender total security 2019 build 23.0.24.120 but the same thing happens with Bitdefender free build 1.0.15.120.

[ritchie58]

I agree with you SMV, newyorkjet's workaround is a less than ideal solution since that does leave your system slightly more vulnerable to infection by leaving the Windows temp files not being scanned. The devs really need to look at this situation with Bitdefender in my view.

[SMV]

Bitdefender currently has a market share of about 10% according to OPSWAT and that's not a negligible amount of people. I will be grateful if you could notify the developers about the problem.