Subscribe to How-To Geek
We encourage you to register on our forums and post any questions you might have. The How-To Geeks monitor this forum and will respond to your question quickly.
Am unable to run the software even after having downloaded the file twice. The message that I get while trying to run it is that, set-up file may be corrupt, please try downloading again....
It's the same download that is highlighted so much in this website...
Help!
Try using CCleaner instead, from the blurb it says it does the same thing.
I use it, as do other forum members I believe.
@raphoenix
*AHEM*
http://lifehacker.com/5033518/.....king-myths
I'll also add that in order to state that it "improves overall machine and OS performance" there must be proof. Any *legit* statistics that it improves performance? Any *noticeable* performance?
I recommend that people stay out of and away from the registry. Only someone with experience should even go into it and only to resolve a serious OS inhibiting problem (OS won't respond, won't boot outside of safe mode, etc). CCleaner has other useful features though worth recommending for. It's registry cleaning options though aren't one of them.
@JonMCC33,
Everything written on Lifehacker is (NOT) "gospel" by any means.
Agree that "newbies" should not get involved with something they do not understand.
However, stand by my statement that performance can be improved by "tweaking" the Registry as Registry Settings are (NOT) optimized for every configuration but are a (one size fits all middle of the road general solution).
Kindest Regards,
Rick P.♦:)
Definitely not gospel... I do vaguely remember writing that article though =)
Registry cleaners do not improve performance unless there's an issue with your machine.
Technically speaking, raphoenix is right... if you know what you are doing you can manually wipe out a lot of stuff in the registry that isn't needed, and increase some performance. Your better bet is to use a very clean install and only install exactly what you need.
One of these days I'll get around to publishing my benchmarking proof for the myths.
@The Geek,
Thanks for Your Backup.
You are COMPLETELY CORRECT concerning a Clean Install.
There is even such a thing as an order of install and sequence of install that most folks don't know about with many steps to obtain that Very Clean Installation you speak of :) :)
Kindest Regards,
Rick P.♦:)
The Geek's part in that article was great, really shed some light on performance myths, but Ed Bott really put it best here (as The Geek even referenced): http://www.edbott.com/weblog/?p=643
"Don’t run registry cleaner programs, period. I won’t go so far as to call them snake oil, but what possible performance benefits can you get from 'cleaning up' unneeded registry entries and eliminating a few stray DLL files? Even in the best-case scenario the impact should be trivial at best. Maybe a second or two here and there, maybe a few kilobytes of freed-up RAM, and I’m being generous. How can you balance those against the risk that the utility will 'clean' (in other words, delete) something you really need, causing a program or feature to fail?"
@JonMCC33,
A good point but I remind everyone again, one does not run a registry cleaner the way you suggest in automatic mode.
That would be total folly.
One must use several Cleaners as Tools and then make human decisions as to what is needed and not needed in the registry hives and dependencies.
---------------------------------
After a (normal) Clean Install, I'll bet you a cup of your favorite beverage that I can find +600 extremely bad errors in the Registry after process completion.
---------------------------------
Don't ask me why this is because I don't know.
You will have to ask Microsoft for the explanation and I feel sure their answer will be "that they don't make mistakes :) :).
I think you and I both know different.
Kindest Regards,
Rick P.♦:)
Curious, I didn't run any registry cleaner after my clean install of Windows Vista Ultimate x64. I've ran it for nearly a year in a now without any problems and I've installed and uninstalled plenty of applications during that time. So I have had 600+ extremely bad Registry errors from the start and no telling how many more throughout a year of patches, Service Packs and application installs/uninstalls. I must be *really* suffering. ;-)
I did a scan on my Windows XP Pro SP3 VM that I run in VirtualBox - using CCleaner, one of the most recommended of all registry cleaning programs. It found a handful of "issues" and nothing close to 600+. Most were missing shared DLLs from .NET Framework 1.0 (irrelevant unless you run apps requiring .NET Framework 1.0), unused file extensions (not going to improve performance), a few keys for programs that I uninstalled (not going to improve performance), ActiveX issues (irrelevant unless you run Internet Explorer), some open with and uninstaller references.
That's going to improve performance somehow? I promptly uninstalled CCleaner off of my VM. Why? Because it works without a problem now. No need to delete anything and risk causing more harm than good. If it's not broke, then don't fix it. ;-)
This is a good conversation, but I'll just wait till Geek comes up with some benchmarks...or maybe you can provide some instead?
@JonMCC33,
These types of discussions have been on going since an O/S was invented.
They really serve NO purpose because each member is free to configure and run their own systems as they wish.
The same can be said for vehement hardware discussions.
It all boils down in the end to what works best for each member.
I could post benchmarks but it would be a waste of time as there are 100s of Thousands of such so called Proofs already on the net and one more posting would be like a "drop in a bucket".
As you said, this all makes for good discussion but let's face it; one Geek seldom convinces another Geek of anything so best move on to something else. We're both just whiling idle time away tonight :) :) :) (lol) (lol) (lol)
Kindest Regards,
Rick P.♦:)
Jon,
CCleaner was never meant to be a real Registry Cleaner. It is used to to clean Cashes out and only will catch the most gross-est of errors in the Registry. You use it and I use it about every 30 minutes to clean cashes out but it is (NOT) a Registry Cleaner my any means.
We recommend it here so newbies and folks without registry knowledge don't get themselves into trouble.
Would certainly hope your expertize goes beyond using CCleaner to fix "bugs". :) :)
Kindest Regards,
Rick P.♦:)
@raphoenix, this is not an experience comparison I hope. I don't recommend any registry cleaning programs at all - as stated above. I used CCleaner merely as an example because people always refer to it. This was the first time I ever downloaded it or used it and it was so merely for the use of this thread. If you think there's some program better that will detect all 600+ "problems" after a clean install of Windows then by all means let me know. ;-)
A true Geek lives for knowledge after all. ^_^
Jon,
By all means I'd be glad to share the program names with you.
I'd prefer to do it by E-mail as I don't want to be responsible for anyone using a program which they may not know the consequences of.
@0z,
I know you are fugal.
Ever heard of 10 High ??
Me and some old Nam Flying Buds were talking about that the other day.
For $2.50, one could buy a Quart of the best sippin' whiskey one could get over there. (LOL) (LOL) (LOL)
Don't know if they even make it anymore.
Try it because you will learn to like it in "tough times" and it still may be cheap. (LOL) (LOL) (LOL)
--------------------
Man, has this thread degenerated off-topic !!!! (LOL) (LOL)
Kindest Regards,
Rick P.♦:)
You must log in to post.
|
svchost.exe jusched.exe dwm.exe ctfmon.exe wmpnetwk.exe |
wmpnscfg.exe rundll32.exe wfcrun32.exe Ipoint.exe Itype.exe |
Wfica32.exe Mobsync.exe conhost.exe Dpupdchk.exe Adobe_Updater.exe |
