Windows Forum

Ask something
Discussion Locked

Norton Systemworks 2001&Registry Problem

0 helpful
12 replies

by markspencer

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Running Norton Systemworks on a HP Celeron 466Mhz machine. When I start Windoctor and run all tests, it says there is a registry error, drops to next test and then Windoctor closes automatically without finishing. There is no way to tell what the problem really is. If I run Scanreg, it says there is not a problem. The main problem is that the computer hangs on shutdown and will not power off.

12 replies

by cg it

Question: When you open Windoctor, is the "run all tests" box marked? Does this happen when you use one button checkup? If so, open Norton Utilities and run Windoctor from there[making sure "run all tests" box is marked.

by cg it

you might also want to try scandisk and/or checkdisk[chkdsk] from a command prompt. Thought these two programs are really Norton's Disk Doctor[or vice versa].

by zlitocook

After you try the other answers try downloading windows washer it will remove a ton of stuff you dont need. Not shutting down correctly is one of MS big problems. It can be as simple as a corrupt temp file to an invalid registry entry while using anoffice program. Try regclean from MS and clean your drive of temp, cookies and IE temp files. Have you looked at the FAQs section on nortons web site?

by choppit

I'd ditch systemworks. In fact I wouldn't use any kind of registry cleaning utility. Sooner or later it will cause you problems. Best (and safest) bet is to investigate shutdown problems manually. Try these;

Run Windows Update - Theres a patch for shutdown issues under W98 although it rarely cures the problem in my experience.

You might want to consider some of the following;

Remove programs selectively from the Startup folder to see if they cause the problem.

Disable fast shutdown.

Turn of windows shutdown sound.

Reduce hardware acceleration settings.

Another possibility - I've seen problems with NSW2001 which were caused by "iffy" system memory.

This discussion is closed to new replies.