Unsolved

This post is more than 5 years old

3 Posts

5906

January 29th, 2005 22:00

Norton Systemworks Premier 2005 Problem

I installed Norton premier 2005 on my Dimension XTP.  After the installation I rebooted and when I tried to get into Norton to do the next step of activation I could not open Norton.  I got a message that stated "another instance of the configuration wizard is already running".  My only choice was to check OK and when I did that that message disappeared and I still could not open Norton.  The big problem is that I can't open any application on my desktop.  The machine has slowed to a crawl and checking in the task manager the CPU useage is very low to 0.  I cannot get into system restore to restore to an earlier date.  I am locked up on everything!!  Anybody got a solution!

January 30th, 2005 15:00

I have a post on this site on 01/29/05 with New Norton SystemWorks Premier and Ghost 9.0 recovery process.
 
I did encounter problems on initial installation. It appeared that Norton live-update was updating during the activation process and my machine seized during the patch process of norton ghost 9.0. After serveal reboots and live update runs (which kept applying the same fixes over and over again) I decided to:
 
1) uninstall (using the CD) the system works 2005
2) reinstall everything except anti-virus (which I believe kicked-off the update process)
3) turn off live update
4) product activated no problem
5) ran live update (an it correctly patched everything except virus stuff)
6) rebooted
7) installed anti-virus
8) rebooted
11) ran live update again and ran full system scan
12) if you have system suite 5.0 or some other good registery cleaner, now is a good time to run it but probably not necessary. It found alot of stuff from the first install.
 
I'm running fine right now and am able to Ghost image and restore after much pain and suffering. I am getting a messages from Norton anti-virus (after re-boot) saying " Norton anti-virus does not support the repair feature--please uninstall and reinstall" I think this is because of the backwards assignments of HDs during the recovery process (see my post, 01/29/05)...investigating

0 events found

No Events found!

Top