Jump to content
CCleaner Community Forums

APMichael

Experienced Members
  • Content Count

    675
  • Joined

  • Last visited

Everything posted by APMichael

  1. Ok, thanks for your quick reply.
  2. Would "DetectFile=%CommonAppData%\CanonBJ\IJPrinter\CNMWindows" possibly work or does this path/folder also exist on your system?
  3. Thanks for the modified entries. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/7c2346239aa471742b0ee2b666d4db2b9f59e4d6 https://github.com/MoscaDotTo/Winapp2/commit/17093d77d5537bb0879f720ec5cfcebbb5e40e72
  4. Thanks for all replies and revised entries. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/b3a5205a211b579ef883751bd70e35aa0f404169
  5. I tested CCleaner with the browser Brave Beta and everything worked as expected. The browser is detected and cleaned by the Winapp2.ini entries: And if you add the CustomLocation, CCleaner cleans up with its built-in entries:
  6. Thanks for the hint! IMHO it is better to use an older version of CCleaner instead of moving the old entries back to Winapp2.ini. If Piriform fixes the problem with one of the next versions, people would think that the cookies management still doesn't work, because the old entries always remove all cookies.
  7. Same as for Chrome cookies: Does CCleaner's cookies management have any problems? CCleaner should be able to open and clean these cookies files without removing the files themselves (at least this has been possible for years). The entry [Stored HSTS Cookies *] was also moved to "Removed entries.ini": https://forum.piriform.com/topic/51568-cookies-visible-to-ccleaner-but-not-to-firefox-settings/?tab=comments#comment-299024 Please try to check the files "Removed entries.ini" and "Winapp3.ini" before posting new entries. Thank you very much.
  8. Does CCleaner have problems cleaning cookies with the latest version of Chrome? The entry [Cookies *] was moved to "Removed entries.ini" a long time ago. The entry [Extensions Databases *] was moved to "Winapp3.ini" a few weeks ago, because it causes problems with an extension.
  9. Question: I noticed that some entries use the same path for error reports: "%LocalAppData%\CrashRpt". Shouldn't we add a separate entry for this path and remove the duplicate FileKeys from the other entries? [CrashRpt Error Reports *] LangSecRef=3024 DetectFile=%LocalAppData%\CrashRpt Default=False FileKey1=%LocalAppData%\CrashRpt|*.*|RECURSE (CrashRpt is an open-source program library for sending error reports.)
  10. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/6a2bfe60ae169918a6cbcc8ee82d5cb40fa4690a
  11. Thank you for the new entry, but *.tmp files are already covered by CCleaner (Google Chrome - Internet Cache): The old entry is in the file "Removed entries.ini": During this check I also noticed that the entry [HTML5 Storage *] can also be removed, because the "File System" folder is already covered by CCleaner (Google Chrome - Internet Cache), including the removal of the folder itself.
  12. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/d75ff075de9157b3d254aff1e307a168adf918eb
  13. Based on the modification date of the folder, it looks as if my Windows Defender has never used this folder before. If all the files are just copies of the HOSTS file, I think we could add this to Winapp2.ini. (It's also just a subfolder of "Scans", so there probably won't be any really important data stored there.) FileKeyX=%CommonAppData%\Microsoft\Windows Defender\Scans\BackupStore|*.*
  14. There's also a brand-new tool for that: AppBuster
  15. The VIASAT browser seems to be based on Chromium. You can use following methods to add other browsers: https://www.ccleaner.com/docs/ccleaner/advanced-usage/ccleaner-ini-files/how-to-clean-user-data-from-non-standard-mozilla-browsers CustomLocation1=CHROME|path_to_user_profile https://forum.piriform.com/search/?q=CustomLocation1=CHROME
  16. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/988564fc44f2ac6aee6903b4894c76d28a133b36 https://github.com/MoscaDotTo/Winapp2/commit/e2a99bddbfb0102ea2bdc944d676080a1280b1df The latest version of the file "Winapp2.ini" now supports Brave Beta and Dev. You should also add the browsers to CCleaner using one of the following methods: https://www.ccleaner.com/docs/ccleaner/advanced-usage/ccleaner-ini-files/how-to-clean-user-data-from-non-standard-mozilla-browsers CustomLocation1=CHROME|path_to_user_profile: https://forum.piriform.com/search/?q=CustomLocation1=CHROME Example: CustomLocation1=CHROME|C:\Users\<your user name>\AppData\Local\BraveSoftware\Brave-Browser-Beta\User Data\Default
  17. Some time ago I asked on GitHub which category should be used for Microsoft Store Games. The answer was that we should also use Section=Games. I hope that's okay with you, too.
  18. In the latest release only the support for different variants of the Brave browser has been added. The "updates from the community" are not finished yet, I think I can update them tomorrow.
  19. Yes, you're right, the changed DetectFile should always match. Ok, then we won't be able to solve the mystery for now. I will then proceed with the compromise as in my post: https://forum.piriform.com/topic/32310-winapp2ini-additions/?page=311&tab=comments#comment-303915 Thanks again for your help.
  20. Thanks, but unfortunately, there's still an inconsistency: The original Detect used "FilmOnLiveTVFree.FilmOnLiveTVFree_zx03kxexxb716" like the RegKey1. On your image it is now "FilmOnLiveTVFree.FilmOn_zx03kxexxb716". Do we then need a Detect3?
  21. @siliconman01 I guess my last post was overlooked: https://forum.piriform.com/topic/32310-winapp2ini-additions/?page=311&tab=comments#comment-303946
  22. Thanks again, for your reply. E1: The ExcludeKey of the BleachBit entry is no longer necessary, we removed it some time ago. And it couldn't be the culprit for the issue. Even the wildcards in the directory names don't change the situation, only changes have been made to make the entry easier to read. E2: The FileKey9 of the BleachBit entry is also not necessary as it is already covered by FileKey6. They have removed the same files. So, if you really don't use the ExcludeKey you posted here, then it's very strange that your entry doesn't break Cortana anymore, because without the ExcludeKey the same files will be deleted as with the BleachBit entry. Would it be too much to ask, if you would please post your complete entry here?
  23. Thanks for your clarification. Unfortunately CCleaner does not support wildcards in registry keys. You need to add an additional Detect.
  24. This is not possible because the desktop version already uses this name. We could leave the name unchanged or use [iTunes App *]. The "App" is also used by some other apps, e.g. [ShareX App *]. Just to be safe: Is this a copy and paste error or is the path correct? Because of the double "Packages\Microsoft.MicrosoftOfficeHub_*\AC".
  25. Ok, thank you very much for your fast reply. I'm very sorry, but now I have to bother you again: If your entry is exactly like in my post, then your entry has an ExcludeKey? Or do we have a misunderstanding? (Because the main question of the current discussion is whether we need to exclude files or not.) If your entry has an ExcludeKey, we know why your entry no longer breaks Cortana. If your entry doesn't have an ExcludeKey, it's even stranger, but maybe the "SettingsCache.txt" file is only important for non-English systems. The BleachBit entry is the same as the current winapp2.ini entry, but without the correct ExcludeKey.
×
×
  • Create New...