AumHa Forums

I was using regedit to rid my computer of some leftover pieces of uninstalled programs probably (two years worth). I notice going down through the trees there is a ton of empty CLSID files (the ones with the long numbers. EEAB7790 -C514 -11D1 -B42B- 00805FC1270E

Ran my Registry Mechanic 6.0 and it removed a lot of stuff, and also CCleaner and it took out some more that Mechanic didn't touch. Went back and there is still a bunch to put it mildly of empty CLSID files still left.

Question: Is there any known program that will scan a registry and pick out the empty usseless taking up space for nothing CLSID files?

Thanks,
ultra_classic

Hi Ultra,

Microsoft has a freebie online program at http://onecare.live.com/site/en-us/default.htm. The first time I used it, it found and removed 300 and some odd registry entries. You might want to give it a try. Being the Godfather's program it should be safe....theoretically. It didn't do me any harm.

Keithc

I strongly recommend that you, or anyone else, avoid using the onecare registry cleaner

Here's why:

The onecare cleaner offers no chance to backup what is removed and whatever it removes is gone, forever. [1] Should it mistakenly remove a key or value needed by your operating system or software it's gone along with your program or operating system. I've seen onecare's registry cleaner completely hose systems.

IMHO (and many others), XP does a fine job maintaining the registry and cleaners are not needed. If you insist on using a registry cleaner, I insist that you use one that allows you to backup what it removes.

Also, IMHO, you'll get more bang for the buck performance wise by simply using disk cleanup to remove the clutter from your system and defragmenting the hard drive.

Disk Cleanup

• Click Start.
• Click All Programs | Accessories | System Tools | Disk Cleanup.
• Disk cleanup will calculate the free space on your computer, which may take a few minutes.
• After the calculation is complete, confirm that only the following checkboxes are checked:
  Temporary Internet Files
  Recycle Bin
  Temporary Files
• Click OK and Yes when prompted to delete files.

Disk cleanup will delete the files and close automatically when finished.

Defrag the drive
Start-All Programs-Accessories-System Tools-Disk Defragmenter. Have it defragment your local disk.

==========================
[1] Restoring Registry Keys after Cleanup
http://boards.live.com/safetyboards/thr ... eadID=4868

Best of luck
KB
Malware

Hi ultra,

Most every MVP I've run into does not advocate the use of any Registry cleaners. I've tried a couple of popularly toted ones, and was amazed at the entries they wanted to get rid of.
I did use one occasionally when I ran W98SE, as "Registry bloat" was more of an issue back then. I'm told that XP does not suffer from this like 98 did. I tried to find the articles to refer you, but I can't locate them right now.
You may want to see Jim E.'s reference here:
http://www.aumha.org/win5/a/regpak.php

Curt Christianson
(Not the MVP)

Thank you all for your input on this matter. I shall take the advice given and leave well enough alone! I must add, I have been using PC Tools products for years without a problem. For instance Registry Mechanic that I have used since ver. 3 and now ver. 6, always makes a restore point prior to 'repair' although I've never had to use it. Lucky I guess.

ultra_classic

Hi KB,

You are no doubt right that it is best to not try to clean the registry and I usually follow that rule. However, the onecare cleaner does establish a restore point so is that not a good enough backup? Too, one could use erunt or some other method of backing up the registry before he goes into onecare, couldn't he?

Just wondering.
Keithc

It creates a restore point or a backup of the registry?

Possibly MS has cleaned up their act and modified the tool (that I would never use myself and won't use to answer my question above) to allow backups to be created. [1] A system restore point will backup the registry if the OP has SR enabled. Keep in mind that the SR point goes by by in time at a rate that depends upon how much space the OP has allocated to it.
Yes, backing up the registry could and should be done before ever attempting to clean it, but you didn't mention that in your earlier post which is why I felt compelled to chime in here. Then again, why do we need to clean the XP registry?

=======================================
[1] Restoring Registry Keys after Cleanup
http://boards.live.com/safetyboards/thr ... eadID=4868

KB
Malware

You can, of course, back up the Registry yourself before running the cleaner. See ERUNT on http://aumha.org/freeware/freeware.htm and other notes on Registry backups on http://aumha.org/regfiles.htm

On the first reboot after hosing a system, one also can use Last Known Good to recover.

OTOH, I'm no more eager to recommend this cleaner (or cleaners in general, at this point in time) than KB is.
_________________
Jim Eshelman, MS-MVP (Windows Shell/User - Windows Security)
"Another flaw in the human character is that everybody wants to build and nobody wants to do maintenance." - Kurt Vonnegut
Your gifts to this site are much appreciated. http://aumha.org/donate.htm

KB,

Yes, it definitely does create a restore point. I can't remember for sure if it is an option or whether it just goes ahead and does it but I think it is the latter. Maybe they have cleaned it up since an earlier version.

I would have attached a screen shot but couldn't figure out how to do it. I wasn't even very clever with the quote thing, either.
Kiethc

And a System Restore point (which includes a backup of the registry as I noted earler) will only be available if SR is enabled on the system in question and will be lost, eventually, as SR is limited by the space allocated to it and works in a FIFO manner removing the old when creating the new.

Please consider yourself lucky to have gotten away with running the onecare registry cleaner without problems. And please let XP manage the registry in the future.

Best of luck
KB
Malware

Mark Russinovich (Author of the "Bible", Windows Internals, co-founder of Winternals and Sysinternals, and since both companies were bought by Microsoft, now a senior Microsoft employee) was asked:
His reply fairly captures my own view:

To which you can add the additional problems: Applications installed on a machine that is used by more than one person can creates entries for each user in their private registry store: HKEY_CURRENT_USER. Because registry cleaners (and REGEDIT.EXE) operate under SYSTEM permissions with the logged-in user security token, they cannot access these other registry entries.



So you have these issues with a registry cleaner:

• If an application is installed and used only by one user, a registry cleaner run by another user will remove "invalid" entries in HKEY_LOCAL_MACHINE and disable the application from working by the other user(s);
• If an application is installed by User #1, and used as well by User#2, the registry cleaner operation run by User#1 cannot remove the instances of the application created by User#2.
• On top of these technical issues that should scare you away, there is the central argument made by Mr. Russinovich: only if the registry cleaner has a sophisticated database of all application software installation registry changes would it have a chance of being safe to use. There is to my knowledge no such animal out there.

Though the Microsoft Knowledge Base has a lot of articles on how to repair the damage created by using these utilities.

Summary:

Will using Registry Cleaners speed-up my system and make it more reliable?
It will have no effect on system speed. There is an excellent chance it will make your system less reliable.

So what should I do about the registry?

The best thing you can do is to enable System Restore and add to your Autostart applications a registry backup. Strongly recommended for this is ERUNT (freeware):

[ERUNT] Registry Backup and Restore for Windows
http://www.larshederer.homepage.t-online.de/erunt/

[ERUNT Download URLs]
http://www.aumha.org/downloads/erunt.zip
http://www.aumha.org/downloads/erunt-setup.exe

[Installing & Using ERUNT]
http://www.winxptutor.com/regback.htm
http://www.silentrunners.org/sr_eruntuse.html
http://www.larshederer.homepage.t-on...runt/erunt.txt

But I backup my registry reqularly using REGEDIT.EXE

You might as well not have bothered, the backups created by Regedit are of no use to you.

Neither does it export the whole registry (for example, no information from the "SECURITY" hive is saved), nor can the exported file be used later to replace the current registry with the old one. Instead, if you re-import the file, it is merged with the current registry without deleting anything that has been added since the export, leaving you with an absolute mess of old and new entries.

References:
http://blogs.technet.com/markrussinovic ... -life.aspx
http://mywebpages.comcast.net/SupportCD/XPMyths.html
http://www.larshederer.homepage.t-onlin ... /erunt.txt

Are software registry cleaners of any use?

Fred Langa started with a standard PC, imaged it, and ran 10 registry cleaners. He ran each three times on an image:

Highest number of items that needed to be "fixed": 800
Lowest number of items found to be "fixed": 59

Does not this suggest that what needs to be fixed is not at all certain?

The other question it invites is it not possible that those generating a large number of entries are trying to sell snake oil? See this small discussion that prompted Langa to test:



Mr. Langa answers: There are several reasons for the disparity in those error counts. First there's the matter of simple semantics: At one end of the spectrum, there are Registry errors that -- if not corrected -- may make a system unbootable or unstable, or that may cause some of your software to crash or to malfunction. But at the other end of the spectrum, there are trivial, transient Registry items that are intended for short-term use, that harm nothing when they go out of date, and that are ultimately self-correcting via normal Windows housecleaning. Naturally, counting these latter as "errors" drives up the count and lets a given piece of software generate impressive-looking stats; but removing those "errors" doesn't mean much in terms of a real benefit.

I cite the article so that you can read it in full: http://www.informationweek.com/LP/showA ... queryText=

But back to Mr. Langa's testing. One reason for testing each cleaner three times was as a credibility check. If you run the same cleaner three times consecutively, it would be a fair assumption that the results should be nearly identical each time. It would be hard to make a credible case for using a product that changed its mind about what was a registry entry to be cleaned if run three times as a test. As Fred explains:

Doing immediate second and third runs with each cleaning tool was to see if any of the programs under test were fudging their numbers by over-reporting errors. For example, if a tool was really doing what it said it was, it would find and fix all the errors it could on the first run. Immediate subsequent runs should show essentially zero errors, because they all were fixed on the first run, right?

But if a tool still reports a significant number of errors on the second and third runs, you might wonder what was going on: Why couldn't the tool find and fix all the errors the first time? Is the tool introducing new errors as it runs? Is it fudging the numbers to make you think it's doing more than it really is? Is it reporting as "errors" some things that really aren't errors after all?

At the least, it seems to me that a good Registry cleaning tool should report a stable, repeatable, and very low number of errors on back-to-back repeated runs. To me, a tool that can't get the number of reported errors down to a stable, low minimum number on repeated runs either isn't fixing things right, or isn't analyzing them right in the first place. Your mileage may vary, but I tend to stay away from tools that act this way.

With apologies to Fred Langa, my summary of his test results:

• JV16 PowerTools 1.3.0.195: I included the last free version of this highly regarded tool -- from 2003 -- because so many of you will be familiar with it. As such, it can be a kind of touchstone you can use for context in comparing newer tools. When run on my test system, it identified 307 problematic items in the Registry, 122 of which it deemed "safe to remove."
• JV16 Powertools 2005: On our test system the PowerTools 2005 Registry Cleaner's "aggressive" setting dug far deeper than its simpler, earlier cousin (above), finding and removing a total of 800 problem items, including 53 "highest" level problems, 691 "moderate" problems, and 56 "low-level" problems. This one proved a Fred Langa favorite. The results were repeatable after three runs.
• Easy Cleaner: EasyCleaner found and removed 99 entries on its first pass -- on rough par with the old version of JV16 PowerTools. The second and third runs found zero additional items, meaning that the tool found and removed everything it could the first time, just as it should have, with no artificial number-pumping going on to try to impress you. EasyCleaner is a very nice little tool, and you sure can't beat the price! (freeware) A Langa favorite.
• Registry Mechanic: found and removed 39 errors while informing me that the $30 paid/registered full version would remove an additional 58. ...Repeated runs turned up 19 problems each time. I have no way of knowing if these were 19 new problems, or 19 of the initial 39 that weren't really fixed, or 19 that came back after reboot, or what. But the combination of a low initial error count results and relatively high repeated count puts this tool on my "don't bother" list.
• Registry Repair: its first run when it reported it found and fixed an impressive 691 problems. But my interest faded quickly when the second run reported 124 items, and the third run reported 200 items. To me, that's a sign of something very wrong going on: either the program is introducing new errors as it runs; or is failing to correct some errors it reports; or is falsely reporting as "errors" things that are not really errors at all.
• Registry First Aid: found 59 problems on first run, less than what the old JV16 version could do. ...Alas, the second and third runs showed a real problem, reporting 123 and 109 problems, respectively; higher than the number found in the original run!
• Registry Medic: The initial scan on my test system turned up an even 100 problems, with the second and third scans turning up 80 and 68, respectively. The initial "100" didn't alarm me, as it's close to the number of "safe to fix" items reported by the old JV16 version, but if your initial scan starts at 100, how on earth can an immediate rescan still show 80 problems? That's a big red flag for me, and so I set aside this software, as well.
• The Registry Drill: In my tests, the Registry Drill found 134 items in its first pass, 110 in the second, and 109 in the third. These lackluster repeat performances, plus an antiquated-looking interface, and a setup that makes it clear that XP support was bolted on to a much older product, all help convince me that this is not a top-tier tool.
• RegistryFix: In my tests, the software flagged 105 problems on the first run, 66 on the second, and 55 on the third. The program's interface is nice enough, but the results weren't anything special. I see no particular reason to select and use this software.
• CleanMyPC: In my tests, the software found 130 problems on the first run, 114 on the second run, and 112 on the third; another lackluster performance that doesn't seem to warrant a deeper look.

The fact that your own results will likely vary is even more cause of concern. There simply is not a reliable way to test if a registry entry is valid or not. This requires a trained eye and not an automated tool. Langa cites the worst possible case for registry trash: a computer upgraded from Win98 to XP. The computer received regular scans from Norton's "WinDoctor" and ToniArts "EasyCleaner." When given to a group of XP experts, they manually removed over 3,000 entries.

Summary of Registry Cleaner Software:
Do not bother with this. It it unlikely to help, it can cause harm.
There are no end-user benefits from running registry cleaners. Unecessary entries in the registry do no harm. This should not be a regular maintenance chore. It most certainly if done should not be automated.

I hold to the singular distinction I made in the beginning: there are times that a fast registry editor with search is needed to fix a single issue under Expert hands. There is no justification for the regular use of automated registry cleaning tools; and as the results above show, they are of dubious merit as the "fix" for even one-off problems that need solving.

Bill Castner
MS-MVP, Aumha VSOP & Moderator

A long time ago, I was fortunate to receive the advice to avoid automated registry cleaners from a much-repected member of another forum. I have no doubt this saved me much grief over the years.

When I first started monitoring aumha, I was gratified to see this advice repeated from time to time (usually as a side issue), as well as to learn about the useful utilities ntregopt and erunt.

All of which is to say, I'm glad to see this thread- many thanks! There's nothing like having one's practices reconfirmed with informed opinion, cogent arguments and good references.

joe53

Good morning,
It is a satisfaction to read the posts of persons with knowledge and experience. What I can affirm is that, every time I access AumHA, I learn more a little.
Very much thank you!
_________________
Best regards!
Alex M de Souza [aka] Night Goose
"The wasting of time is an abomination to the spirit". Ptahhotpe (~2350 BC)

:roll: Why has no one cited the First Law of Computing in this thread?

........ If it ain't broke, don't fix it.
==============================================================

IN RE (Windows Live) OneCare Cleanup Scan:

Several MVPs had a private discussion last fall about Windows Live OneCare's Cleanup Scan, AKA Registry Cleaner. What follows is from my saved notes from our conversation:

=> Complaints, etc., (44 in all, dating from Mar-Aug 2006) about the Cleanup scan (horking the install of Office, NAV, etc.) can be found in the Comments section here: http://safetycenter.spaces.live.com/blo ... !706.entry

=> How to rollback the registry settings after Windows OneCare Safety Scanner Cleanup
by MVP & AumHa VSOP Ramesh Srinivasan:
Source: http://www.winhelponline.com/articles/73/1/

=> From erunt.txt, essentially the ReadMe for Lars Hederer's ERUNT:Source: http://www.larshederer.homepage.t-onlin ... /erunt.txt

MVP Jim Byrd points out that Lars' comment above would apply to importing one of OneCare's Undo REG file, too.

My Personal Conclusion:

Steer well-clear of Windows Live OneCare's Cleanup scan (which BTW is included in OneCare's Full Service Scan), as well as all other "Registry cleaners".
...... If it ain't broke, don't fix it.
_________________
~Robear Dyer (PA Bear)
AumHa VSOP, Admin & Moderator; MS MVP-Windows (IE, OE, Security & Shell/User) since 2002
Steely-eyed Missile Man, Sensei, Mule Skinner & Smart Alex
Errabundi Saepe, Semper Certi
Your donations to help keep this site going are very much appreciated: http://aumha.org/donate.htm

People reading this thread should realize the trouble it took to make it happen. It seemed that the original thread was lost but was reconstructed from what was available in the Google cache...Thanks Bill.

So what should I do about the registry?
The best thing you can do is to enable System Restore and add to your Autostart applications a registry backup. Strongly recommended for this is ERUNT (freeware):

(Technical information: ERUNT saves only registry files which are in
use by the system. It obtains information about these files from
registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\
hivelist. Registry hives not listed there, for example those
of other users of the computer, cannot be saved by ERUNT.)