Norton Internet Security / Norton AntiVirus

[Voyager10]

Last Summer i found this Bug in NIS 2012, this Topic is closed.

http://community.norton.com/t5/Norton-Internet-Security-Norton/Great-Bug-in-Quarantine-Restore-found...

This Bug still exist in the last Version 19.5.0.145 , NIS2012.

I check this now with a Virus-File in the Quarantäne , detected as WS.Viral.1 . I Check this Button "Restore and Exclude" on this File and Norton "only"  exclude WS.Viral.1 ... Not this File !

My Question is now , what was the incomprehensible to the error since 4 months ?

The Solution was simple , do not exclude the whole Detection-Signature if you restore a quarantined File , but Symantec fails complete... 

[elsewhere]

Hi Voyager10

In early January 2012, I raised this issue as a defect present in the Norton 360 Version 6 Public beta and I was subsequently directed to your original thread:

http://community.norton.com/t5/Norton-360-v6-Public-Beta/Quarantine-Restore-Part-2/m-p/624553/highli...

(link to a transient forum)

Apparently, the update given in your original thread reflects the current status of this issue ie it is still under discussion.

At this stage, I'm just as puzzled as you are with regards to the lack of action in terms of resolving this issue...

[Voyager10]

that was the last time that I report errors , over the years many of the messages always ignored , for example Trojan or Rootkit Submissions..

[mp3jo Super Virus Trouncer]

And the bug is fully documentated...

[ NIS 2012 vsn 19.5 on german Win 7 prof 32 Bit sp1, IE9 ]

If you restore a file a window shows "restore & exclude this file"

but the next window shows "exclude this risk..."



[mp3jo Super Virus Trouncer]

---

elsewhere wrote:

Hi Voyager10

In early January 2012, I raised this issue as a defect present in the Norton 360 Version 6 Public beta and I was subsequently directed to your original thread:

http://community.norton.com/t5/Norton-360-v6-Public-Beta/Quarantine-Restore-Part-2/m-p/624553/highli...

(link to a transient forum)

Apparently, the update given in your original thread reflects the current status of this issue ie it is still under discussion.

At this stage, I'm just as puzzled as you are with regards to the lack of action in terms of resolving this issue...

---

We could say, that no answer from Symantec is an answer as well!

[elsewhere]

Indeed. Given the insidious nature of this defect, this issue should have been resolved by now. There's really no excuse if this issue is still present in the upcoming NAV/NIS 2013 Public Betas...