Jump to content
CCleaner Community Forums


Experienced Members
  • Content Count

  • Joined

  • Last visited

Everything posted by APMichael

  1. I do not think so, because this is a special case only for this one extension. (The extension possibly does not comply with the specifications for Chrome extensions?) CCleaner's built-in entry has been removing these folders (HTML5 Storage) for a very long time now, without any issue reports.
  2. Great! I'm glad I could help. 😃
  3. Ok, I think I found the responsible CCleaner entry: [Google Chrome - Internet Cache]. So it is not caused by the Winapp2.ini. To protect the icons of your extension, you should exclude these two folders: C:\Users\<your username>\AppData\Local\Google\Chrome\User Data\Default\File System\000\ C:\Users\<your username>\AppData\Local\Google\Chrome\User Data\Default\File System\Origins\ Note: The "000" folder may have a different number. But right after cleaning up all temporary files and importing the extension settings, it should be "000".
  4. Some months ago, an issue with another extension was reported. The responsible entry was [Google Chrome - Session]. You can try excluding the following folder and see if it helps: C:\Users\<your username>\AppData\Local\Google\Chrome\User Data\Default\Extension State\
  5. Please make sure that you are using the latest version of Winapp2.ini. The responsible CCleaner entry must then be found: Right-click on the first Google Chrome entry and select "Clean <entry name>". Then check to see if the issue occurs. If not, continue with the next Google Chrome entry until the responsible CCleaner entry is found.
  6. Thanks for the modified entry. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/01a2ad4cef959173e49e3a0e9ce02a2ccfbed4ba
  7. Yes, because there is no default policy for Edge. You must add the registry keys and values yourself. Or you could do it like this: https://forum.piriform.com/topic/53177-how-to-disable-pre-launching-and-pre-loading-so-ccleaner-can-fully-clean-edge/?tab=comments#comment-302353
  8. I can confirm this behavior. If the entry uses "Detect=HKLM\Software\Foxit Software\Foxit Reader", Trim does not detect it (and trims it out). If the entry uses "Detect=HKLM\Software\Foxit Software", Trim detects it.
  9. Thanks for the modified/revised entries. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/0922652a38f306e05876e86bfbad6ba45e8bb006
  10. That is correct, because there is no default policy for Edge. You must add the registry keys and values yourself. Please read the following post:
  11. That is correct, because there is no default policy for Edge. You must add the registry keys and values yourself. Please read the following post:
  12. Just for your information: It's strange and sad that some bugs are consistently ignored...
  13. Thanks for the modified entry. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/70ab0fd9a66cef5c7f63ec2951d586d998004860 https://github.com/MoscaDotTo/Winapp2/commit/0b95a1decf1c1d53390d238e73487a37b2ea4897 Winapp3.ini update: https://github.com/MoscaDotTo/Winapp2/commit/a717947ac5cbdf6943f175e7ec4cd43aed5a57a4
  14. Thanks for the revised entry. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/029072306e5deb8472565cd1f9e1dce06a91c5e6 https://github.com/MoscaDotTo/Winapp2/commit/af810289b3a2159b51873654aee935ab44456874 Winapp3.ini update: https://github.com/MoscaDotTo/Winapp2/commit/e87753c5981a03ca67699ccdefa6a879ed8e780b
  15. Please read the "How to fix it" post from nukecad:
  16. Thanks for the new and revised entries. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/ce538a6925542a8dd72e1685861aecf0a8e85b4d
  17. Thank you for your quick reply and corrections.
  18. Thank you very much for all the revised entries. The entry [LocalSystem *] has some typos: FileKey9+11+15 need a pattern. I guess |*.*|RECURSE. FileKey9+10+11 have a doubled backslash after %WinDir%. And please do not rearrange the FileKeys. Please use the alphabetical order we need for WinappDebug/Winapp2ool. Thank you!
  19. Unfortunately you clicked too fast and installed the additional CCleaner Browser. Please read the "How to fix it" post from nukecad:
  20. Thanks for the modified/revised/updated and new entries. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/b8e44c1ab2acae6d955688a566b63217db97b8d0
  21. Very strange! Unfortunately, I don't have any ideas anymore. Then only Piriform can help...
  22. Ok, all shortcuts are corrupted and that only happens with CC Pro. So it seems that it should be related to one of the Pro features. What is your setting for "Users" (Options > Users): Current user only, All users, or Selected users? If it is one of the last two, can you please try "Current user only"? This would be the only Pro feature that would come to my mind about the problem.
  23. I'm not from Piriform, but I checked your log.txt. CC doesn't actually remove anything that could cause this problem. Only log files and temporary files are removed. But I have noticed that it removes shortcuts from your desktop ("C:\Users\XXX\Desktop\XXX.url"), so it seems that you have not unchecked the "Desktop Shortcuts" rule. Please make sure that you have unchecked this rule and also the "Start Menu Shortcuts" rule (as Dave CCleaner already mentioned). The error message shows that only the shortcut in the taskbar is corrupted, not Office itself. Doesn't it work to start Office using one of the shortcuts in the start menu? Edit: You can ignore what I wrote about the desktop shortcuts. They were in the recycle bin. Sorry!
  • Create New...