10-03-2009 10:43 AM - edited 10-03-2009 11:08 AM
Thanks for your post.
Maybe I should have worded my two original posts differently.
I am not reinstalling NIS 2009, other than the fact that it is included on the backup image that I am attempting to restore.
Actually, I probably should have been a bit more clear. I understand that you have not uninstalled NIS 2009, but uninstalling was one suggested corrective step. I think it's worth trying.
I'd first try uninstalling via Add or Remove Programs. It may not be perfect, but it avoids the problems inherent in running the NRT. Get a copy of the full NIS 2010 installer and run it. It should automatically pick up your existing product key. If not, just enter your NIS 2009 key.
If that doesn't resolve the problem, you won't have lost anything but a bit of time.
10-03-2009 12:11 PM - edited 10-03-2009 12:21 PM
I experimented a little with the notebook computer, thinking that it may not be NIS updates that caused the problem.
I started Win XP in Safe Mode. I went into Add/Remove Programs and uninstalled MS IE 8 and attempted to restart Windows normally. The splash screen hung and continued the action of the scroll bar.
I did a hard reboot, and went back to Safe Mode. I then uninstalled Google Toolbar. (Another recently installed program.) (No system restart at this time.) I then uninstalled NIS 2009. I chose the Custom Uninstall option. At the conclusion of the uninstall I was asked to restart Windows, which I did.
I attemped to start Windows XP normally on this Gateway notebook computer. This time it worked. Win XP was now functioning.
I decided to uninstall only NIS 2009 on the desktop system that was down. I started Windows XP in Safe Mode (because I could not start it normally). I went to Add/Remove Programs and uninstalled only NIS 2009. Again, I chose the Custom Uninstall option. I was asked to restart Windows, which I did.
I attempted to start Win XP normally on this Compaq desktop computer. This time it worked... XP is functioning.
The conclusion that I have drawn is that NIS' update was the sole reason for this problem. Maybe it's because NIS detected something that it's designed to detect. I don't know why NIS causes Win XP to fail when starting normally... all I know is that the following has occured during the last 3 weeks.
1. The notebook computer that I use in another area of the house was rendered inoperable. I spent a great deal of time and effort on my own, and on forums online attempting to solve the problem. In the end, the computer hardware became suspect, and I quit trying to diagnose software issues. (Specifically, the system would not always boot to the CD even though BIOS was configured in that way.)
2. I purchased a new HP computer because of work that I had bid on an out of town project. (Just under $2,000.)
3. After experiencing similar issues with the desktop system, I again began to question software. The one common thread between the two systems was that both system failed to start normally after updating several programs (Win XP, IE, and NIS 2009).
4. I had purchased a new 2-1/2" hard drive that I installed in the notebook computer and to which the image was restored from a fairly recent backup. After running the NIS update yesterday, this system was unable to start Win XP normally. This is what really raised my suspicions about NIS.
Now both of the systems which were down yesterday are running normally... without Norton Internet Security.
I am still angry at Symantec, even as I have both of these systems running. The $2,000 was essentially a waste. I have spent so much time and energy on this problem... Maybe I should have been smarter, or done something different; but, honestly, the only thing I did was install updates from one of the largest security software companies in the world. And once I did, I could no longer use my systems.
So... I would like for someone to explain to me why I should trust Symantec/NIS 2010 any more than I did 2009.
I find it incredibly difficult to believe that I am the only one running Windows XP that has had this type of problem. I am even more surprised to think that Symantec didn't work through these kinds of bugs before pushing their updates into the public domain. Sarcastically speaking, I think Symantec owes me a lot more than free updates after all that I have gone through with this whole experience. Had it just been one system, I could understand a fluke; but, two independent systems produced by different manufacturers using different hardware platforms.... There is no excuse for this.
I know you guys post on this forum to help others who have problems. This outrage isn't directed at you. I appreciate your help. I do, however, believe Symantec is liable for something because of their negligence (in spite of all the disclaimers we, as the licensing public, must agree to before using software).
Is it just me, or is a real problem?
10-03-2009 03:04 PM
I think I read some place in the Norton Forum that in order to get updates correctly that your computers have to be hard wired. By any chance are your computers running wireless? Just a thought.......
Success always occurs in private and failure in full view.
10-03-2009 03:41 PM
Initially (when this problem first occurred three weeks ago), the notebook computer was on a wireless connection and the desktop was on a wired connection.
Yesterday, with a new hard drive in the notebook, the NIS updates were downloaded via a network connection.
It really didn't appear to have made any difference regardless of which method was used.