Latest Avast update causes a problem with Norton System Works 2003.
Avast identifies Nprotect.exe as a problem. Have added Nprotect.exe to exceptions list in Avast Standard Shield but the problem still occurs.
Any ideas would be much appreciated.
Steve
isn’t that like having 2 antivirus programs on your computer at the same time and they are conflicting ??? :
Norton SystemWorks 2003 comes with Norton AntiVirus 2003, excellent antivirus software which now scans files downloaded through instant messages, as well as from the Web and POP3 e-mail. It also blocks viruses that try to spread through your e-mail, keeps your virus definitions up-to-date, and looks for virus-like behavior.
i know i probably didn’t answer your question-but having 2 on your computer as real-time programs-they will work against each other
There is another topic on this (forum search for nprotect) that you should monitor also.
What exactly did you type ?
Do you know you can copy the full path from the alert window and use that ?
You could also check the offending/suspect file at: VirusTotal - Multi engine on-line virus scanner and report the findings here. You can’t do this with the file securely in the chest, you need to extract it to a temporary (not original) location first, see below.
Create a folder called Suspect in the C:\ drive, e.g. C:\Suspect. Now exclude that folder in the Standard Shield, Customize, Advanced, Add, type (or copy and paste) C:\Suspect* That will stop the standard shield scanning any file you put in that folder. You should now be able to export any file in the chest to this folder and upload it to VirusTotal without avast alerting.
If it is indeed a false positive, see http://forum.avast.com/index.php?topic=34950.msg293451#msg293451, how to report it to avast! and what to do to exclude them until the problem is corrected.
The other topic is mine. :-[ http://forum.avast.com/index.php?topic=37461.0
In this case NPROTECT.EXE is the ‘Protected Recycle Bin’ of ‘Norton Utilities 2000’ which contains no AV component.
Hi,
Problem seems now to have been resolved by Avast. Thanks to everyone for their comments.
You’re welcome.
Thanks for the feedback, Alwil are usually quick to correct the VPS when an FP is confirmed.