Fortunantly, Firefox and Chrome weren't affected. I used Firefox for a couple of hours Sat morning (U.S. CT) until the issue was fixed.
The problem began when Symantec issued a routine LiveUpdate definitions download, apparently sometime during the evening of Fri 02/20 U.S. time.
The update affected the main AV suites, N360, NIS, and NS, and affected most IE versions (if not all).
For many users, the problem began to be fixed yesterday 02/21 around 6am U.S. CT when Symantec begin distributing a repair update. That's when I download their update fix for the issue.
There may be a few Norton customers that either haven't received (or downloaded) the repair update or perhaps the rollout hasn't yet reached their geographical locations.
My take on this issue is that the communication issue is important when things like this happen. There were a lot of members that uninstalled/installed their AV, used Restore Points, etc. I was thinking about restoring from an Image but decided to run Firefox until they fixed the problem.
I have to admit that my AV wasn't the first suspect when my IE11 became inaccessible. "It's never too late to learn something"
I posted this in the Norton Forum thread that quietman7 linked:
Communication is important. In the aftermath of the IE issue, that would be my #1 item to place in Symantec's Suggestion Box
- When an issue is known that affects a significant percentage of its customer base, deploy a blanket e-mail in addition to a message that will display either in the Dashboard or the customer's System Tray area. This notifies the customer base to avoid PC resets, Restore Points, Uninstalls, Image-restorations, etc.
- The other excellent suggestion was mentioned several times by other members in the original thread: Look into a LiveUpdate "rollback" option, if it's possible to integrate that into the current products. This can be significant in assisting members in the future where Restore Points, Image-restorations may not point the customer in the right direction of the problem.
I thought about posting a "poll" thread over there to see what the regular members thought about grading now Norton handled the issue. My own take on it:
- Recovery Speed/Repair of issue
I give them a "B+" for this one since it did occur on a Fri evening (U.S. time) heading into a weekend and that, I'd guess, affected the repair time.
"C-" This is where I think they may have been able to handle things better but I know nothing about what's involved in deploying some kind of a Dashboard/Sys Tray message. That may not be practical.
Where I don't cut them as much slack is the e-mail tool where they could have sent a blanket e-mail to the customer base. Having said that, I also know nothing about what's entailed since I imagine Norton's worldwide customer base is rather large.
Norton did post a notification on their product site but from what I've read about it, the notice appeared there several hours after the problem appeared. I admit I didn't think to check Norton's home site for any information about the issue at that time.
My take on my N3360's performance on 2 Win 7x64 PC's and my Mom's XP PC still rates high. I've had no issues (or malicious intrusions) with Norton until this occurrence since I switched to N360 in November '12.
Human nature being what it is , I probably graded Norton too tough but this one affected a lot of their customer base.