Jump to content
CCleaner Community Forums

APMichael

Experienced Members
  • Content count

    604
  • Joined

  • Last visited

Everything posted by APMichael

  1. Winapp2.ini additions

    Thanks! Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/c8c6096cc27fa9e79360f2ac07cc8ef3b69c3dc5
  2. Winapp2.ini additions

    Thanks! IMHO we should continue to use [Xbox *], as the other apps are actually only hidden "sub-apps" of the Xbox app. (And if we add more "sub-apps" in the future, the name will be far too long.) https://forum.piriform.com/topic/32310-winapp2ini-additions/?page=302&tab=comments#comment-302515
  3. Winapp2.ini additions

    Thanks for your reply. This should work (Detect does not require "Wow6432Node"): [Auslogics Registry Defrag *] LangSecRef=3024 Detect1=HKCU\Software\Auslogics\Registry Defrag Detect2=HKLM\Software\Auslogics\Registry Defrag Default=False FileKey1=%AppData%\Auslogics\Registry Defrag\Logs|*.* FileKey2=%AppData%\Auslogics\Registry Defrag\Reports|*.* FileKey3=%CommonAppData%\Auslogics\Registry Defrag\*.x\Reports|*.*
  4. Winapp2.ini additions

    Thank you, but is this entry really safe? I guess you're only using the MCT to create an ISO file, right? Because if you read the many articles about these folders, it seems you also need these folders for a Windows rollback if you have used the MCT for a Windows upgrade (or if Windows has upgraded itself). For example: https://www.howtogeek.com/268667/what-is-the-windows.bt-folder-and-can-you-delete-it/. There is also an entry in the Winapp3.ini: [Old Windows Installation *].
  5. Winapp2.ini additions

    Ok, thanks for your quick reply.
  6. Winapp2.ini additions

    Would "DetectFile=%CommonAppData%\CanonBJ\IJPrinter\CNMWindows" possibly work or does this path/folder also exist on your system?
  7. Winapp2.ini additions

    Thanks for the modified entries. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/7c2346239aa471742b0ee2b666d4db2b9f59e4d6 https://github.com/MoscaDotTo/Winapp2/commit/17093d77d5537bb0879f720ec5cfcebbb5e40e72
  8. Winapp2.ini additions

    Thanks for all replies and revised entries. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/b3a5205a211b579ef883751bd70e35aa0f404169
  9. Winapp2.ini additions

    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:
  10. Winapp2.ini additions

    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.
  11. Winapp2.ini additions

    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.
  12. Winapp2.ini additions

    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.
  13. Winapp2.ini additions

    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.)
  14. Winapp2.ini additions

    Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/6a2bfe60ae169918a6cbcc8ee82d5cb40fa4690a
  15. Winapp2.ini additions

    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.
  16. Winapp2.ini additions

    Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/d75ff075de9157b3d254aff1e307a168adf918eb
  17. Winapp2.ini additions

    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|*.*
  18. Windows Store App Maintenance

    There's also a brand-new tool for that: AppBuster
  19. VIASAT Browser

    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
  20. Winapp2.ini additions

    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
  21. Winapp2.ini additions

    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.
  22. Winapp2.ini additions

    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.
  23. Winapp2.ini additions

    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.
  24. Winapp2.ini additions

    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?
  25. Winapp2.ini additions

    @siliconman01 I guess my last post was overlooked: https://forum.piriform.com/topic/32310-winapp2ini-additions/?page=311&tab=comments#comment-303946
×