Could somebody who works for Symantec contact the developers of NIS 2013 and ask them if they have THOROUGHLY tested the upgrade process going from NIS 2012 to NIS 2013 when it is done one WinXP SP3 computers?
I have tried EVERYTHING that other people on this message board have suggested doing to make NIS 2013 work and I am convinced that the problem has nothing to do with my computer. I have done reinstall, Norton Removal Tool, run chkdsk, did Diskeeper defrag, etc.
NOTHING WORKS !!
I can do the upgrade or clean install of NIS 2013 but as soon as you do a few Live Updates, either Live Update crashes or NIS 2013 starts crashing with the system tray icon disappears, etc.
I did a previous post about this issue last week here:
http://community.norton.com/t5/Norton-Internet-Security-Norton/Live-Update-fails-crashes-after-upgrade-from-NIS-2012-to-NIS/td-p/801224
I have been a subscriber to Norton Internet Security for over 5 years now. I had to give up on NIS 2013 (for now) and I re-install NIS 2012 again. I sure am glad I backed up those NIS 2012 install files now. NIS 2012 has always run without ANY problems on my WinXP computer. After installing it again, NIS 2012 is running great again.
Since I am PAYING for NIS 2013 with my subscription it would sure be nice if developers THOROUGHLY tested and de-bugged NIS 2013 on Windows XP SP3 machines. NIS 2013 works great on my Windows 7 PC but I still need to use the Windows XP SP3 machine.
Somebody who works for Symantec needs to work overtime trying to fix these problems! I'm sure I'm not the only one in the world who is very annoyed with these issues. I bet thousands of NIS 2013 customers are super irritated about this too.
Upgrading from NIS 2012 to NIS 2013 should be A VERY SIMPLE PROCESS. A customer should just download the new NIS 2013 software, reboot, run Live Update and you are done until NIS 2014 comes out. Customers shouldn't have to be uninstalling NIS 2012, running Norton Removal Tool, chkdsk, defrag and all that just to upgrade Norton Internet Security!
Please just FIX IT as soon as possible. Some replies to this post coming from high level NIS 2013 software developers would be great.