Do "Registry Fixers" hurt more than they help?

[foodfightr]

Ok, when I get a new system I like to isntall everything and set all of my settings maticulously and then use acronis true image to back up the system before I start surfing, downloading, etc. I keep all of my files on my D:\ partition so that at any time I can revert to my fresh installation, which I do about every 90 days. (A little much? Maybe, but I like my OS running smooth.)

On my most recent system, I made an image that included this strange problem. The built in windows "ZIP" function would not work. I could open .zip files and execute them, but not cut, copy or drag the files out of the zip archive. I like the "passive" feel of the zip folders in windows xp, but I use winrar for every other file type.

I read a long thread on this problem and many people were finding that running RegSeeker, a free utility to find and correct registry errors was solving the problem. I ran the program from my fresh copy of windows and it fixed 452 registry errors! That sounds like an awful lot for a clean installation of XP SP2 w/ all updates and no extra junk outside of office, winamp, trillian, etc. (The "necessary" apps!)

I've never really believed in these registry fixer programs before, do you think it is doing more harm than good? Changing 452 keys in the registry sounds like it is going to come back to bite me in the @$$ on ATLEAST one occasion. (For example, maybe an application will crach because it can't find a key- even if it didn't point to a file that existed.)

 

[foodfightr]

Forgot link to app:
http://www.hoverdesk.net/freeware.htm

 

[scottws]

I used Regseeker once. It messed up Norton System Works and Office so bad I ended up reformatting.

I have an old verison of a program called RegCleaner, and I've never had a problem with the automatic cleanups with that thing. It was bought out and is now part of jv16 PowerTools or something, and I've used that and broke things.

Anymore I can't recommend using a registry cleaner. I feel like they break things more than they fix.

 

[foodfightr]

I figured as much, I'm going to spend a few hours and just re-do the image I guess.

 

[DaiShan]

Originally posted by: scottws
I used Regseeker once. It messed up Norton System Works and Office so bad I ended up reformatting.

I have an old verison of a program called RegCleaner, and I've never had a problem with the automatic cleanups with that thing. It was bought out and is now part of jv16 PowerTools or something, and I've used that and broke things.

Anymore I can't recommend using a registry cleaner. I feel like they break things more than they fix.

Yeah RegCLeaner never gave me any problems either, but I don't really see any reason to risk it and I never use one on a client machine, basically if you are having registry problems, a clean install is the easiest fix.

 

[Smilin]

My standard statement about such matters:

Know how to backup and restore your registry even in the event that the machine is unable to boot due to an incorrect change and you can regedit or regclean to your heart's content. If you don't know how to restore to get yourself booting again then you shouldn't fool with such things.

 

[vanvock]

I've been using RegSeeker for quite some time & don't have problems with it. As far as I know it doesn't repair anything it removes broken links, dead ends etc. Make sure to check the backup before delete box, so if some program doesn't like it you can restore it. I think finding that many on initial scan is not unusual but subsequently it will be much less depending on how much installing-uninstalling you do. If you click on the select all tab you can separate the red & green items which is a nice feature they added.

 

[scottws]

Originally posted by: Smilin
My standard statement about such matters:

Know how to backup and restore your registry even in the event that the machine is unable to boot due to an incorrect change and you can regedit or regclean to your heart's content. If you don't know how to restore to get yourself booting again then you shouldn't fool with such things.

I had turned off System Restore and had no backups. Otherwise I would have restored.

I still don't use System Restore, but I use ntbackup to save the system configuration periodically.

Admitedly though, I couldn't, right now, restore the registry of a PC that won't boot.

 

[KoolDrew]

Yes, they do more harm then good. I have seen more then one occasion where a registry cleaner messed something up.

 

[drwngflies]

I use CCleaner two to three times a day and RegSeeker once a week, for the last 2 years with not one issue.
Seems that if you know what it's cleaning and can recognize an entry that may be needed helps.
Both of these also have backup capabilities, so I don't see why everyone hates 'em so much.

 

[Smilin]

Originally posted by: scottws

Originally posted by: Smilin
My standard statement about such matters:

Know how to backup and restore your registry even in the event that the machine is unable to boot due to an incorrect change and you can regedit or regclean to your heart's content. If you don't know how to restore to get yourself booting again then you shouldn't fool with such things.

I had turned off System Restore and had no backups. Otherwise I would have restored.

I still don't use System Restore, but I use ntbackup to save the system configuration periodically.

Admitedly though, I couldn't, right now, restore the registry of a PC that won't boot.

A system state backup will also update your windows\repair registry hives.
So although you don't have the restore point down, you're at least getting the backup part done!

I would highly recommend turning system restore on though. If you have to limit the disk space it consumes that's fine, but don't turn it off. Save your butt it will.

 

[scottws]

Well, I've got a 210GB Windows partition, so space isn't really a huge issue. I just found that I never, ever used System Restore, so I thought I'd go ahead and save on the space.

(I guess I would have used it after running RegSeeker and finding out about all the things it broke, but alas, I had turned it off before that).

 

[Smilin]

I've never used the smoke detectors at my house either. Doesn't mean I'm going to throw them away to save electricity.

Turn it back on now. There will be more crashes someday and it will pay off.

:thumbsup:

 

[scottws]

The thing is I never really know what System Restore is going to do. I make a lot of configuration changes on my system several times a week. Installing programs, uninstalling programs, installing patches, creating new files, deleting files, encrypting files, decrypting files, various system configuration changes, etc.

So I have no idea what would happen if I restored to an earlier point.

 

[Smilin]

Have faith

You monkeybreak something, pick yesterdays restore point and see if the issue clears up. If not, go to the day before. If you can't boot due to a registry problem you snag a previous version from the system restore point while in recovery console.

It has tons of uses but they all start with it running before the problem happens. The only negative is drive space. It can be configured as needed, but even with defaults will be tiny on a drive like yours.

Give it a chance to help you. It doesn't hurt.