Registry restore problem

  • Thread starter Thread starter George Newton
  • Start date Start date
G

George Newton

I have a desktop system, with myself as the only user.

An install of Norton SystemWorks was interrupted by an
error, resulting in a cessation, and a lack of uninstall.

I deleted the Norton files manually.

However hundreds of entries were placed in the registry.

Running Norton's WinDoctor from the CD failed to recognize
any of it's "own" invalid/unconnected entries. (VCOM next??)

I then resorted to restoring a recent System State, made prior
to the Norton install.

I selected "When restoring...always replace the file..."

However, when searching on the Norton keyword (just as one
example), I found that the registry state had not actually
been restored, since the references to Norton were still
there in the hives.

This prompts two questions for me:

Are there some "Windows" reasons why a complete and authorized
replacement of the System State would be ignored without warning?

I am the only user. I am the administrator and named user who
is automatically logged on at boot.

Is it reasonable (assuming anything's possible) that some security
in the partial Norton install (only registry settings left, AFAIK)
would interfere with the System Stae replacement?
 
At this point how you remove Norton SystemWorks will depend on the
version that you tried to install. Some of the earlier versions have
removal tools available (SymClean) while the latest version entails a
lot of manual work. See here or search the Symantec site for more
information:

http://search.symantec.com/custom/u...y&ex=&rq=0&oq=&qm=0&ql=&st=11&nh=10&lk=1&rf=0

As to why the registry restore didn't work as anticipated I don't know.
Usually for "non Domain Controllers" the registry is restored from the
Repair Console. No saying what damages may have been done to your
Windows 2000 installation with that restore manoeuvre, other problems
may arise further down the road.

John
 
....................................Some of the earlier versions have
removal tools available (SymClean) while the latest version entails a
lot of manual work.
...
Click to expand...

Thanks for the ref. I'll look into that.
As to why the registry restore didn't work as anticipated I don't know.
Usually for "non Domain Controllers" the registry is restored from the
Repair Console. No saying what damages may have been done to your
Windows 2000 installation with that restore manoeuvre, other problems
may arise further down the road.
Click to expand...

I have no clue what a "non Domain Controller" is.

I work with desktop, unnetworked systems.

As for Repair Console, you may view some unique unhealthy phenomena
that that utility provided me (not) (on another system) in the
general ng.

It's not likely that will risk it again - at least not until I find
out why it did (didn't) do what it did.

As for "damages done:"

1. I've nuked the W2K install.
I'm not going to mess around with that kind of messed up registry.
2. You imply that my "Restore" was an unorthodox "manoeuvre."
If it is not recommended, then why does BackUp specifically offer
that type of specific service: System State BackUp and Restore?

Any elaboration will be appreciated.
 
George said:
I have no clue what a "non Domain Controller" is.
Click to expand...

It's a computer that is not a Domain Controller, registry restores on
DC's are different.
As for Repair Console, you may view some unique unhealthy phenomena
that that utility provided me (not) (on another system) in the
general ng.
Click to expand...

I didn't see or read your other post. The Repair Console doesn't harm
systems, what one does with it may cause "unhealthy phenomena".
It's not likely that will risk it again - at least not until I find
out why it did (didn't) do what it did.
Click to expand...

Good idea!
As for "damages done:"

1. I've nuked the W2K install.
I'm not going to mess around with that kind of messed up registry.
Click to expand...

Probably the best thing to do but sometimes a very labour intensive
solution. Rebuilding a box that has been up for 3 or 4 years is no fun!
2. You imply that my "Restore" was an unorthodox "manoeuvre."
If it is not recommended, then why does BackUp specifically offer
that type of specific service: System State BackUp and Restore?
Click to expand...

My understanding from reading your post is that you tried to restore the
whole System State Data with the Backup utility (while Windows was up
and running). You would have only needed to replace the software hive.
You cannot perform selective Registry restores with ntbackup.exe.
System State involves more than just the registry. Your method should
have worked but for some reason or other it didn't, regardless, I would
have opted for selective hive restore instead of System State.
 
Back
Top