I may have double-confirmed a case of CCleaner messing up a program.
My sister uses a program called Bayscribe to transcribe medical notes for hospitals from home. She has had an issue where it's audio component fails to start on two occasions after running CCleaner. Apparently it depends upon a temporary file to run which CCleaner empties. The result is it generates a message saying that a [temporary] file is no longer available to start the audio service. I saw this error message.
This is not the Registry cleaner component of CCleaner, but the Disk Cleaner. In order to miss the file one would have to deselect Temporary Files which is often the bulk of what it finds. I believe it found 4gb when when it last cleaned up her machine, just before this error occurred.
Apparently the issue has occurred twice, the second time after CCleaner was reinstalled due to forgetting about the issue. It is noteworthy to me because it represents the first time I've seen first hand a confirmed case of CCleaner removing a file that causes a program not to be able to run.
Her company tech support told her this is a known issue with CCleaner and to remove it.
I am posting this also at CCleaner Fail? - Windows 7 Forums where I have been a passionate defender of CCleaner for years.
Greg, please don't link to a thread on another forum to get support. How can we respond here if nothing has been requested? The linked thread already appears to include the problem, a workround, and the solution.
I must say that in my own personal opinion any application which stores important files in temporary locations is .... well let's just say it's not good practice.
a quote from a long time poster on Seven Forums says in that thread
Temp files can be cleaned out without any type of third-party app at all, so this sounds to me like BayScribe is just one very poorly written piece of software.
Greg, please don't link to a thread on another forum to get support. How can we respond here if nothing has been requested? The linked thread already appears to include the problem, a workround, and the solution.
I could have copied and pasted the thread I wrote out in my home forums but thought you would like to share in the discussion since it represents priceless publicity for a revered product from the top tech forum on the web.
I have passionately defended CCleaner for years, often taking much flak for this. What is discussed in SevenForums becomes the accepted wisdom on Windows 7. Having passionately debunked repeated claims of CCleaner messing up systems, it has become the accepted wisdom that CCleaner is nearly a perfect tool. Thus sharing the personal experience demonstrating otherwise is something I thought you would like to share in.
In fact I would like to think someone there is already at work on it. Your software seems to be that good.
I see no need for anyone at Piriform or on this forum to instal and presumably pay for Transcribe in order to fix its incompatibility.
There is an instant solution built into CCleaner - it is "exclusions".
Already at post #18 the Transcribe developer is refuting that his code includes
a message saying that a [temporary] file is no longer avaialble to start the audio service
and is suggesting "Windows Quartz audio component" as a possible culprit.
I am astounded at your audacity to suggest that your topic with the defamatory title "CCleaner Fail!" can be considered
priceless publicity for a revered product from the top tech forum on the web.
Alan -
I am trying to change the thread title from an exclamation to a question - just waiting for our mods to make the change as it already is in the post.
Are you a CCleaner developer?
After watching CCleaner during development I've written passionately and repeatedly that CCleaner is a "genius tool" and "perhaps the most respected single app in the tech world" until careless doubt was slowly winnowed from our forums. I feel an obligation to be intellectually honest when a case with double-confirmation happens to a member of my family..
As you can see we are digging in there to get to the bottom of the case with a cooperative Bayscribe developer. This will play out in the thread to get to the truth. The process is the publicity.
It would be a good chance for Piriform to display their stuff. Let us hope that your stuff isn't theirs.
gregrocker let's all calm down here ![:)]()
When Bayscribe post their findings in Seven Forums please be good enough to post here with the link then I shall ensure that the ccleaner devs are made aware, should they need to be.
Thank you for taking the time to post.
Greg and all,
This problem is being actively investigated with the Bayscribe developers on the Sevenforums, and the developer states that CC cleaning temp files is not the problem (post 14). Perhaps we'd better leave the investigation and resolution to that arena, as we're not getting very far here. (edit - posted before seeing H's comments.)
Believe me no one will be happier than I if this again acquits CCleaner, as I am surely one of its most ardent defenders.
and is suggesting "Windows Quartz audio component" as a possible culprit.
There's plenty of overly aggressive registry cleaners that will un-register that part of Windows.
Interesting that you mention that Captain as I am as aggressive in denouncing Registry Cleaners as in defending CCleaner when it is confused with the reg cleaner sales scams that frequently ruin Win7. I consider CCleaner to be a genius tool having put it on hundreds of installs over 15 years representing thousands of uses without a single fail. To have this experience in my own family caused me to want to vet it amongst those I trust in our Forums and share it with you here. Hopefully it will be a good demonstration case of how CCleaner can get blamed for other corruption.
Not all registry cleaning is bad though, especially the non-aggressive variety which CCleaner is deemed as being by many of us users. The aggressive variety are in my opinion not worth using, and most people won't have the amount of patience it takes to input allot of exclusions.