It appears that someone at CCleaner has figured this one out and it no longer shows as an error. (Either that or Microsoft has fixed it!)
Basic question: If were not supposed to run registry cleaners on Windows 10 installation, why is CCleaner selling us a utility that does just that????
1 hour ago, latimers said:<div class="ipsQuote_contents ipsClearfix" data-gramm="false"> <p> Basic question: If were not supposed to run registry cleaners on Windows 10 installation, why is CCleaner selling us a utility that does just that???? </p> </div>
Because Registry Cleaners do have a valid use - for helping to fix a computer that has problems (ie. following a malware infection or if something goes wrong uninstalling an app).
It's using them for the wrong purpose (to try and speed up a healthy machine, which it won't do) and using them indiscriminately that can cause problems rather than fixing problems.
CCleaner also has a Disc Analyzer, a Duplicate Finder, and a Drive Wiper - you don't use them everyday, you only use them when you need to - Reg cleaners are the same, only use a registry cleaner when you need to.
And yes, before someone says it - We all agree that the reg cleaner in CCleaner should be with those tools and not as prominient as it is now.
Even Piriform agree, it's just taking them time to change that:
If it was beneficial to run a routine/regular registry clean in CCleaner then it would have been included as a part of Health Check.
It wasn’t included in Health Check because it is NOT beneficial to do a registry clean if you don’t need to.
It can be unhealthy to run a registry clean that isn't needed.</strong>
I use the portable CCleaner and just started to notice the issue reported in this thread, exactly as shown by melxpress February 6. This started to happen after I uninstalled MinGW manually by removing all libraries of this manager and then ist shortcut and folder, because it did not appear in the apps list for doing the uninstall. This may have left some hanging issues in the register.
The PC is working normally, so I hope this will not be serious and leave it as it stands (though I would prefer to get no register issue reports as I before).
I don't know why some apps cannot be uninstalled normally and leave these register problems.
If someone more experienced has some advice other than doing nothing, I would be grateful.
Again -
That registry entry "SpeechRuntimetime.exe" is new to Windows and is needed by Windows, which is why Windows keeps putting it back if you remove it.
It is nothing to do with anything that you may have uninstalled, it is a part of Windows.
See this for more info on what it is, (and why you shouldn't be using the registry cleaner with Windows 10 unless you have a problem to fix).
See also the post by Dave CCleaner which follows that one and explains CCleaner's current policy on using the Registry Cleaner.
I wonder why this one LITTLE thing is so blown out like it's a huge issue. It's allot of nothing really!
I have the same problem on my 2 computers.
Problem: ActiveX/COM Issue
Data: LocalServer32\C:\Windows\SysWOW64\Speech_OneCore\Common\SpeechRuntime.exe -ToastNotifier
Registry Key: HKCR\CLSID\{265b1075-d22b-41eb-bc97-87568f3e6dab}
35 minutes ago, Gilles Beauvisage said:<div class="ipsQuote_contents ipsClearfix" data-gramm="false"> <p> I have the same problem on my 2 computers. </p> <p> <strong>Problem:</strong> ActiveX/COM Issue </p> <p> <strong>Data:</strong> LocalServer32\C:\Windows\SysWOW64\Speech_OneCore\Common\SpeechRuntime.exe -ToastNotifier </p> <p> <strong>Registry Key:</strong> HKCR\CLSID\{265b1075-d22b-41eb-bc97-87568f3e6dab} </p> </div>
It is NOT a problem.
Please read here, it is needed by Windows.
https://community.ccleaner.com/topic/59965-speechruntimeexe/?tab=comments#comment-327606
I, too, have noticed that Ccleaner has recently been flagging the above registry error on my system the past few days...
I understand and agree with the warnings about registry cleaning in Windows 10...
BUT, I've found some REALLY WEIRD behavior in Ccleaner in this instance!
First of all, on my computer the file in question (SpeechRuntime.exe) exists in the C:\Windows\System32\Speech_OneCore\Common\ folder.
It is NOT present in the C:\Windows\SysWOW64\Speech_OneCore\Common\ folder.
I understand why Ccleaner will flag the error if a registry entry points to the non-existent SysWOW64 location.
NOW. if I open Ccleaner, and run the Registry Cleaner, I see the entry for
LocalServer32\C:\Windows\SysWOW64\Speech_OneCore\Common\SpeechRuntime.exe -ToastNotifier .
If I right-click that entry, and select "Open in RegEdit...", Regedit opens to the expected key, showing the value
LocalServer32\C:\Windows\SysWOW64\Speech_OneCore\Common\SpeechRuntime.exe -ToastNotifier , as expected.
BUT, if I simply close RegEdit, and reopen it to the same key, the value NOW shows the "correct" location
LocalServer32\C:\Windows\System32\Speech_OneCore\Common\SpeechRuntime.exe -ToastNotifier .
WHY is Ccleaner finding an erroneous registry value that apparently doesn't actually exist?
And how can the value seem to change with simply closing regedit, and reopening to the same key?
As said above this particular registry entry is for future use by Windows version 21H1.
(Although some things are using it now).
Some components of 21H1 are already on your computer, but not all of them will be there yet.
Some are already there but are hidden from you by Windows itself.
They will only be fully activated when the update to version 21H1 is 'Enabled' by Microsoft.
It's simply the way that Microsoft are doing updates by downloading things in a gradual fashion and then 'Enabling' them when the time is right.
They are doing it that way so that the 'Enablement' is quicker than downloading a new version all at once.
I guess what I'm interested to know is, how is Ccleaner's registry cleaner "finding" and displaying an "erroneous" registry key that doesn't seem to actually exist?
If I just simply open RegEdit, and navigate to the key HKCR\CLSID\{265b1075-d22b-41eb-bc97-87568f3e6dab}\LocalServer32
the (default) value shown is C:\Windows\System32\Speech_OneCore\Common\SpeechRuntime.exe -ToastNotifier
But if I open Ccleaner and run the registry cleaner it displays the entry
LocalServer32\C:\Windows\SysWOW64\Speech_OneCore\Common\SpeechRuntime.exe -ToastNotifier
If I then right-click that entry, and select "Open in RegEdit...", RegEdit opens to the VERY SAME key, but the (default) value NOW shows
C:\Windows\SysWOW64\Speech_OneCore\Common\SpeechRuntime.exe -ToastNotifier
If I then close RegEdit (and Ccleaner, WITHOUT actually running the cleaner), reopen RegEdit, and navigate back to the same key, the (default) value has reverted back to showing
C:\Windows\System32\Speech_OneCore\Common\SpeechRuntime.exe -ToastNotifier
How is this possible? I've never seen a registry value change back and forth like that.
How can Ccleaner appear to change a registry value without actually selecting the entry and running the cleaner?
Have a read here
Quote<div class="ipsQuote_contents ipsClearfix" data-gramm="false"> <p> I don't understand how Ccleaner can be detecting a registry key/value that doesn't seem to exist <strong>if I search RegEdit for that same key</strong>. </p> </div>
Again:
Quote<div class="ipsQuote_contents ipsClearfix" data-gramm="false"> <p> Some components of 21H1 are already on your computer, but not all of them will be there yet.Some are already there but are hidden from you by Windows itself.
Reply from Nukecad:
Quote<div class="ipsQuote_contents ipsClearfix" data-gramm="false"> <p> </p> <p> So Windows itself is hiding it from you in RegEdit; CCleaner is seeing past that block though. </p> <p> If you are asking how CCleaner is seeing past that block then it's a whole different question. And you probably won't get an answer, why should the CCleaner developers give others/rivals a clue to how it looks for things? </p> <p> Yes, it's all a bit strange from how we are all used to Windows working in the past - and we are all having to work out the changes. </p> <p> </p> </div>
Many thanks nukecad and Andavari for your replies!
Cheers,
Carlos M. Lemos
1 hour ago, tzdvl said:<div class="ipsQuote_contents"> <p> So Windows itself is hiding it from you in RegEdit; CCleaner is seeing past that block though. </p> <p> If you are asking how CCleaner is seeing past that block then it's a whole different question. And you probably won't get an answer, why should the CCleaner developers give others/rivals a clue to how it looks for things? </p> </div>
(Except the above quote wasn't me replying...)
Ah, Thanks! That makes sense.
It appears Ccleaner is able to detect registry entries that are hidden from us mere mortals, but also is "wise" enough to not mess with those hidden entries.
Ccleaner just TEASES us, by repeatedly showing an entry as an error, even though it can't (shouldn't) actually be fixed!
Glad I'm not the one sorting all this out!
And thanks to you moderators for the excellent advice!
1 hour ago, tzdvl said:<div class="ipsQuote_contents ipsClearfix" data-gramm="false"> <p> (Except the above quote wasn't me replying...) </p> </div>
A thousand apologies.
I seem to have edited your post instead of quoting it.
I could blame technical reasons from the forum moderator options, I could blame my disability causing lack of concentration - But no excuses - I made an error, sorry about that.
4 hours ago, tzdvl said:<div class="ipsQuote_contents ipsClearfix" data-gramm="false"> <p> Ccleaner just TEASES us, by repeatedly showing an entry as an error, even though it can't (shouldn't) actually be fixed! </p> <p> </p> </div>
That's one of the issues with registry cleaners as smart as they may seem they're dumb as bricks and require a human to make the decision - possibly one of the reasons why CCleaner's registry cleaner never got an auto-cleaning feature even though it's been a requested feature umpteen times.
Some registry data points to what appears to be nothing but isn't necessarily safe to remove, it's been that way in every version of Windows I've used since the Win98 era. The problem here is with Windows 10 being an actively updated operating system messing around with it and references pointing to the OS folder "C:\Windows" is possibly a recipe for disaster, and I'd personally think that the AppData and ProgramData folders should be off limits too.
It has been claimed by the moderators in earlier comments that CCleaner should not be used on Windows 10 and certainly not on a regular basis but that statement is confusing because in CCleaner's settings it offers to start CCleaner with Windows.
And further down the Options headings under the "Schedule" tab it allows CCleaner to be run at a regular interval as chosen by the operator. If, as advised here, CCleaner should not be used as a regular tool on Windows 10 why are these options available?
Beerless
2 minutes ago, Beerless said:<div class="ipsQuote_contents ipsClearfix" data-gramm="false"> <p> It has been claimed by the moderators in earlier comments that <em>CCleaner</em> should not be used on Windows 10 and certainly not on a regular basis but that statement is confusing because in <em>CCleaner's</em> settings it offers to start <em>CCleaner</em> with Windows. </p> <p> And further down the Options headings under the "Schedule" tab it allows <em>CCleaner</em> to be run at a regular interval as chosen by the operator. If, as advised here, <em>CCleaner</em> should not be used as a regular tool on Windows 10 why are these options available? </p> <p> Beerless </p> <p> </p> </div>
It's just the registry cleaner part of CCleaner which should not be run on Windows 10.
The 'normal' part of CCleaner is perfectly safe to run.
Thanks for the clarification Hazelnut, my cynicism was about to get into 2nd gear. ?
Beerless
"Reserved for future use" meets the Windows 10 registry LOL. One of my OCD friends who likes to "run a tight clean ship", did not like that he just excludes the entry, instead of [a] understanding it and [b] fixing it. Yes, I'm talking about the famous Speech Toast Notifier, interesting name...
The ironic thing is that I do definitely believe in registry cleaners, once a program [The 25th anniversary edition of Paragon's Hard Disk Manager] installed, and it was supposed to run at boot time (when Windows starts), but it did not - because the registry entry for it (in the RunOnce startup) had a mistake in it! Proof that we do need things like CCleaner, even if they trip up from time to time.
And thank you, whoever it was, for mentioning using a chainsaw when cutting the Sunday roast - wonderful image there LOL!