Even though it didn’t sound like I needed the update; if there is an update to my Internet Security/AntiVirus software I’ll update. With that said, I updated last night when I saw it was available. While the process was a little different than normal, it was easy to follow, but the aftermath was unexpected.
I updated my main system first and when the installation was complete and it indicated that it was starting NIS I got the dreaded “Blue Screen” and Windows was dumping error reports. This system has never “Blue Screened” before. My system restarted and the Norton screen came up with a button to validate the product or finish. I clicked finish. IE11 was sluggish, so I rebooted and things seemed to be okay and they are working fine today. Clicking on Support and “Get Support” shows that the installation is okay.
Throwing caution to the wind, I decided to see if my laptop would install correctly. No “Blue Screen”, but after the installation, and this time I saw a “Successful Installation” screen, NIS kept trying to activate the product with an error message(8505,129) that it couldn’t communicate with the Symantec Server. After a couple of minutes of this, I rebooted and that seemed to fix that issue. I never saw it trying to activate the product again.
I should have known better, but despite my previous problems I decided to update my wife’s computer today. I thought things had gone well with hers, Once it started NIS, I got the attempting to activate the product and then the “8505,129” error message; just like on my laptop. I went through two iterations of this and performed a restart, which resulted in the dreaded “Blue Screen – unexpected shutdown”. The computer restarted and as with the laptop it didn’t continue trying to activate the product. Clicking on Support and “Get Support” shows that the installation is okay.
The installation encountered problems when trying to start the new version on 3 out of 3 of my Windows 7 computers; you’re mileage might vary!!!!! Hopefully it will go smoother for others!!!!
Sorry you had such a poor experience. Did you verify that all computers are now running the latest version and have been properly activated?
I did my two last night and did not experience any of the problems you saw. Must be the difference in our configurations. Do you have a second security program active? that might explain much of the problem.
I assume all three are properly activated; all appear so and show 226 days remaining. They all show 21.1.1.7. And, after the installion was complete and I'd gotten past the problems, I ran Liveupdate and there was a 15.78MB, 12 file update.
NIS is the only active security program on my three systems. All have the run-on-demand free version of Malwarebytes.
I'm glad your installations went smoothly; I have no idea why I experienced the problems I did; I've never experienced anything like this before with an NIS update.
I assume all three are properly activated; all appear so and show 226 days remaining. They all show 21.1.1.7. And, after the installion was complete and I'd gotten past the problems, I ran Liveupdate and there was a 15.78, 12 file update.
NIS is the only active security program on my three systems. All have the run-on-demand free version of Malwarebytes.
I'm glad your installations went smoothly; I have no idea why I experienced the problems I did; I've never experienced anything like this before with an NIS update.
Hi,
We may have to write this one off to the phase of the moon or some other random event.
It does sound like it's probably something unique to my systems. I don't run anything out of the ordinary on any of them and all are a little bit different in the programs that are installed, but something sure reacted to this particular NIS update process.
Everything appears fine now, so I guess all is well that ends well, no matter how rocky the road to get there.
I did notice that after the download and during the installation process, something in the process caused internet connectivity to be lost, but not my connection to my Router. This probably influenced the repetitive attempts and failures of the activation process, although at that time I did have internet connectivity.
I followed the instructions and got the downloader. It removed the old and installed the new. No issues to report but I am not on Windows 7. I did notice the people having issues are all on Windows 7.
The only annoying thing that has happened with any major patch that required a reboot or restart of services is that the systray icons don't reappear like they should. Awhile back I was told it wasn't Norton's fault and I should contact the manufacturer of the software for the missing systray icons to address this issue. A bit miffed I replied "like they'd listen to me". So I generally reboot on a reboot-less patch
"that the systray icons don't reappear like they should."
Hi SGFC,
Poorly written apps do not use properly the Windows Restart Manager, so it's normal for the systray icons not to appear after a NIS rebootless patch which uses the Windows Restart Manager.
It doesn't mean though that these apps are not reloaded. ( you van verify in taskmgr.).
I had this issue myself too on W7 x64 but it's harmless, although annoying.
One question, is the NIS systray icon behavior addressed with this new version, when you are using other settings that the Agressive Boot Time Protection or not??
Keeping to a single user logged on to the desk PC it worked this time It still rebooted, so maybe that’s as a result of having 3 user accounts on the PC? So it looks as if this form of update doesn’t cope with multi user setups well.
One question, is the NIS systray icon behavior addressed with this new version, when you are using other settings that the Agressive Boot Time Protection or not??
If you are referring to the double NIS Icon; two Icons are still present on my systems.
This update didn't fix that issue, nor did it fix Safe Search losing focus when the drop down menu appears, nor does it fix the errant removal of IE10/IE11 cookies that contain login information for banking, etc.
yank; you are correct, and I did read the "Improvements & Fixes" annotation, but I think some of us were living with hope that Norton would finally fix some of these long standing problems in what, on the surface, looked like a major "new" update.
