pegas

Thanks. It indeed works.

This bug isn't solved in v5.07 yet.

This bug isn't solved in v5.07 yet.

Even though you have native support for cleaning of the sessions, it doesn't work. I have temporarily created this custom rule to clean it. "C:\Users\xxx\AppData\Roaming\Opera Software\Opera Stable\Current Session"

Opera stable 30.0.1835.59 CCleaner 5.06.5219 Win 8.1 Pro x64 The subject says all.

It's a nice advice but not solution of this CC bug. When I started this thread I was alone reporting this bug but now look at this thread and the second, this bug starts to be identified by more users. One thing you need to keep in mind, only a small fraction of CC users comes to this forum. So you can be sure that this bug plagues many more users.

@MrT Any news in relation to my above two posts of May 29?

I forgot to give you also these entries. Please checkt what happens if deleted. HKCR\CLSID\{98D9A6F1-4696-4B5E-A2E8-36B3F9C1E12C} HKCR\CLSID\{D38406DA-E8AA-484b-B80D-3D3DBDCC2FB2}

I tend to think it has something to do with the Czech localized version of Adobe Acrobat Reader DC. Please test it (v2015.007.20033).

Thanks for the info but it means that we will have to wait a month or so until next routine monthly update in June is released. :-(

It's a shame that the new version doesn't include a fix for this issue and Adobe Acrobat Reader DC isn't included in the cleaning module. I'm disappointed, heavily.

Hopefully. Any feedback is welcome.

Piriform staff, it's a bug and you need to address it. Furthermore, as this new version of Adobe reader supersedes all previous and becomes Adobe's prime (cross platform) reader application, it needs to be included in the cleaner module. Hmm, it looks like a lack of communication ...

Hello! I have upgraded to the latest Reader (v2015.007.20033) today and have found out that if the below items are deleted (found by registry cleaner) the Reader needs to itself reconfigure during the first start up upon deletion of the said registry entries. I have put these entries into exceptions as a temporary workaround. Also please include this new version of Adobe Reader among applications which are cleaned. Thanks & regards!

It seems that the issue has been resolved by ticking (associating) all file types in Picasa settings. Anyway thanks to all for valuable inputs.

Many thanks folks for all your hints. Yes, I use Picasa and the said registry entries were starting to show up only after the latest Picasa update. It's worth noting that deleting these entries makes no problem whatsoever and they are recreated automatically (and found by CCleaner). I have tried it more than twice and no problem observed. So I will keep them in the Exclude List until Google issues another Picasa update which hopefully will resolve this issue because as I said this problem started only after the last update.

Thanks login123 for information. However I meant if there is something I can do to prevent reoccurrence of the entries. I know how to hide (exclude) them and I already have done it. I want to solve this issue for good.

Thank you both. Does it mean that I can do nothing than exclude them?

Hi, Have anyone noticed the following reoccurring registry entries (unused files)? They're reappearing in every registry scan. HKCR\.3fr HKCR\.arw HKCR\.cr2 HKCR\.crw HKCR\.dng HKCR\.kdc HKCR\.mrw HKCR\.nef HKCR\.nrw HKCR\.orf HKCR\.pef HKCR\.raf HKCR\.raw HKCR\.rw2 HKCR\.sr2 HKCR\.tga HKCR\.webp HKCR\.x3f I am not sure but it somehow could relate to Picasa update. I know that I can exclude them but I rather want to resolve this issue. Any help? Thanks & regards.

Steve, don't be so hasty next time and take your time to look around. There is exactly the same thread a few lines below

Thanks for the clarification. It convinced me that I can live without Pro version.

I wonder what the New System and Browser Monitoring in Pro Version does ...

OK. So following my good experience with the said cleaner I vote for a task killer being incorporated in CCleaner for Android.

No, I don't have ROOT on my device and because you named another competitor, I won't hesitate to say that I meant Clean Master (Cleaner).

I beg to slightly differ ... I also thought that task killers are pointless in Android environment exactly due to the reasons described in the how-to-geek article linked in this thread. Moreover I had assured myself about this fact because I have used a few task killers in the past and honestly all were causing me troubles until I installed a one cleaner recently (I don't state its name purposely because I don't want to breach forum rules). This cleaner is a very smart as far as task killer is concerned because it has included a whitelist where all the tasks/services important for the smooth and uninterrupted run of Android are excluded. The whitelist, though, is compiled by developers and you cannot add or remove an item. However to their credit, the task killer indeed doesn't cause any problems like crashes, mysterious reboots etc. You can set the auto kill function when screen goes off what I did and to my big surprise it greatly extended battery life, almost doubled time. I don't want to pay a tribute to this cleaner because I love CCleaner and believe that its Android version will be superior. I just wanted to say that now I am not completely rejecting opinion that task killers are nonsense. It seems that if task killers are gentle/smart and correctly built they can have in certain degree some pros.