Registry - if it is broke, fix it

[Guest]

After scanning through the posts about registry cleaners many people seem to
take the point of view that the extra code isn't causing any problems. I beg
to differ, although this will be an unusual situation. My copy of XP Pro had
been connected four cases, three motherboards and about has many drives.
There is stuff in registry referencing items which haven't part of the system
in two or three years. Now I could just say that it goes against my grain to
have God only knows how many useless lines in the registry but I have another
reason and that is driver updates. I have one of those programs which scans
your computer and informs you of newer drivers. What a cool idea.

Problem: the scan is picking up entries from devices which bit the dust long
ago and in places I am starting to see problems. The first thing I noticed
was that downloaded driver would be unable to fully install. Hmm, wonder what
that is about and if it didn't fully install, what did it do? Then I realized
that I was getting upgrades for nonexistent chipsets and every once in a
while something would go a little crazy.

Back in the olden days (before XP) there was a "blank" registry file and the
slick trick was to over write the current registry file with that one. Next
time it came up it found only the devices really on your machine. There was
the little matter of having to re-install all your software but sometimes it
seemed worth the effort.

So does anyone have any suggestions on a registry cleaner which will take
the devices list down to what is really there and also has a fair chance of
not blowing up the machine?

 

[Sharon Franks]

I like and use this one http://www.ccleaner.com/


--

Sharon Franks
MCC group
Microsoft Certified Solutions Developer (MCSD)
Microsoft Certified Trainer (MCT).

 

[RonK]

Have a look at CCleaner.
http://www.ccleaner.com/

 

[Guest]

Hi Richard:

With all those pieces of pteradactyl bones and mastadon fur in the stew,
why not just do a clean install? Probably very few registry errors then.
Probably faster than picking up the pieces of a shattered registry too.

Mark

 

[cheyenne]

After scanning through the posts about registry cleaners many people seem
to
take the point of view that the extra code isn't causing any problems. I
beg
to differ, ...

I agree with Richard. Why would a person want unused, old, previously
deleted, removed, etc software/applications/code left in the registry? I
use my favorite registry cleaner, Registry Mechanic, once a month or so and,
as yet , have suffered no ill effects. In fact, Microsoft---way back in the
Windows 95 days---had a small utility called RegClean (I believe that was
the name) that worked quit well. And they would probably have one today if
it weren't for some litigation-happy 3rd party software suppliers.
BTW, I have no connection with the makers of RM---I'm just a satisfied user.

 

[Kelly]

Hi Richard:

<unusual situation....

Says it all.

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool
http://www.kellys-korner-xp.com/taskbarplus!.htm

 

[Kelly]

Thank you!

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool
http://www.kellys-korner-xp.com/taskbarplus!.htm

 

[Curt Christianson]

I too used to use MS RegClean, with no problems on W98SE.
It is my understanding that even when MS was offering it, it was still an
un-supported product (kinda like TweakUI). I believe MS pulled RegClean
because of what it *could* do in the wrong hands.

I don't use Registry cleaners any longer, and agree with Kelly and
Callmark--a clean install would be the way to go. Besides, I've always
liked watching how a machine seems to really "kick a**" after a fresh
install of the OS!

--
Curt BD-MVBT

http://dundats.mvps.org/
http://dundats.proboards27.com/index.cgi
http://www.aumha.org/

 

[Bob I]

FWIW, Regclean was pulled by Microsoft for exactly the reasons stated by
those opposed to the indiscriminate use of "registry cleaners". It broke
things.

 

[Guest]

Actually you make a good point but there is a small bureaucratic issue that I
just don't like to fuss with. According to MS, I've installed my copy of XP
enough times to supply a small country. So anytime I get to the point where I
have to install, it is call the number on the other side of the planet and be
asked the question of the day, "Why have you installed it on so many
machines?" I can't tell them the truth; that there is this small dark cloud
called murphy over me which causes the most insane things to happen. So I
tell them that I'm having to restore from a clone and the clone was not right
and so forth.

And remember besides the prehistoric stew, I also have a slew of software to
re-install and tweak and play with until I get it just so. Do I restore the
office before or after the systemworks or is that NIS which is suppose to go
then. And does it matter when I configure outlook, yada, yada, yada. Besides
I want a machine that "notices" the the chipset has been changed and it
doesn't use the other settings after six months or whatever. Is it really
asking too much for the system to clean up after itself?

 

[Kerry Brown]

After scanning through the posts about registry cleaners many people
seem to take the point of view that the extra code isn't causing any
problems. I beg to differ, although this will be an unusual
situation. My copy of XP Pro had been connected four cases, three
motherboards and about has many drives. There is stuff in registry
referencing items which haven't part of the system in two or three
years. Now I could just say that it goes against my grain to have God
only knows how many useless lines in the registry but I have another
reason and that is driver updates. I have one of those programs which
scans your computer and informs you of newer drivers. What a cool
idea.

Problem: the scan is picking up entries from devices which bit the
dust long ago and in places I am starting to see problems. The first
thing I noticed was that downloaded driver would be unable to fully
install. Hmm, wonder what that is about and if it didn't fully
install, what did it do? Then I realized that I was getting upgrades
for nonexistent chipsets and every once in a while something would go
a little crazy.

Back in the olden days (before XP) there was a "blank" registry file
and the slick trick was to over write the current registry file with
that one. Next time it came up it found only the devices really on
your machine. There was the little matter of having to re-install all
your software but sometimes it seemed worth the effort.

So does anyone have any suggestions on a registry cleaner which will
take the devices list down to what is really there and also has a
fair chance of not blowing up the machine?

I am one of the people who are opposed to using registry repair programs as
part of regular maintenance. There are times when a good registry repair
tool can speed up repairing the registry. Your case is one of those times.
Pick your favourite registry cleaner and run it in manual mode. Work through
the entries it flags removing the outdated ones. Make sure you have a good
backup of the registry and know how to restore it before starting.

 

[Malke]

Actually you make a good point but there is a small bureaucratic issue

(snippage)

Hey, if you want to use a registry cleaner - go for it! The rest of us techs
stand behind what we've previously said about using registry cleaners. But
it's all about choice, eh? If you want to use one, no one's stopping you.
We don't need a discussion about your motivation; it's your computer and
I'm sure you can handle the consequences. I'm sure you've done your
backups.

Malke