conflict with window defender?

Hello , just installed NOD32 in a new built gaming system with Win 7 . I tried to disable the Win defend updates because I figured I would get a possible conflict with the NOD32 & the Windows Antivirus, but the definitions for Win defend downloaded and I missed it. Problem is once installed, the definitions cannot be removed. It doesnt appear on the uninstall list for antivirus , but I was worried I may still have conflict issues in the future. Could this be a prob or are my worries unfounded? any suggestions? Thanks in advanced!!

 

See: Are ESET Smart Security and ESET NOD32 Antivirus compatible with Windows Defender?

 

Hey there,

Well, from my own experience, ESET NOD32 4.0.474 has been running alongside with MS Windows Defender on my Windows Vista Business SP-2 box [similar OS to Windows 7]with no conflicts observed so far.

There is no option to remove WD on Windows Vista/windows 7 because it's integrated into the OS. On Win XP however, you can remove it since it's a file you download and install on that OS like any other program.

But, again, no conflicts between NOD32 and WD. They complement each other nicely. Some threats [specially Rogue AVs], undetected by NOD32 get caught by WD.

Regards,

Carlos

 

If you're worried about conflicts, just disable Windows Defender in the Services section of Administrative Tools. If I remember correctly, this will also disable the Windows Defender updates from Microsoft.

 

Just didnt want any future prbs, especially since this is a gaming syst. So I will let things unfold and leave them as is. Thanks all for your quick response and helpfull advice!!

 

I would not recommend going to this extent in disabling WD, since it is a component of the operating system.

 

I always do without problems on Vista and Win 7 and it does not affect the OS!

TH

 

Perhaps, Triple Helix, ESET does not support Windows Defender, compatability issues have been posted to this thread.

Tweaks in modifying Windows Defender are the sole responsibilty of the user as are the consequenses of doing such.

 

They always are! That is why I gave my own opinion with my own experience behind disabling WD and using any other security product including NOD32! He has a choice to keep WD or not so it is best to give him advice on both sides of the coin then he can make his own decision on all the info given here not just one sided. Some people use WD but I do not, again it's my preference and my choice!

TH

 

See previous reply

 

No thanks I think the OP has enough info to make his own decision!

Regards,

TH

 

The OP may seek support for Windows Defender here, not here!

 

The MS link doesn't seem to address the OP's actual question about possible conflicts between Windows Defender and NOD32. Or am I missing something?

 

All concerns were posted in this thread as far as ESET Support is concerned.

The MS link points to where to seek support for Windows Defender.

 

Hopefully I didnt start a war here, just looking for some good advice. I was just concerned of any future problems having both systems operating side by side. Again thanks for all the help and opinions. But I do notice that even after I disable WD , it shows up on next boot up. Any way to completely disable it and future definitions?

 

Just uncheck this box and that's it! But if you do make sure you have some other Anti-Malware scanners to do weekly scans such as MBAM, SAS, A2 Free! Also NOD32 is very good at Spyware and Adware and other threats! All the best!

TH

 

How to deal with security center alerts once Windows Defender is disabled, if you choose to do so, the Security Center may flag at preceeding link.

 

You will not get any because NOD32 covers AV and AS in Action Center as he has Windows 7 not Xp with the link you provided.

TH

 

How does the Win 7 Action Center check for problems

As noted further up this thread, within the constaints of ESET Support, this is all that should be offered, in my opinion.

The OP has been given all the support options for Windows Defender including it's interaction with said third party program.