Jump to content
Piriform Community Forums


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About APMichael

  • Rank
    Power Member

Profile Information

  • Gender
  • Location

Recent Profile Visitors

1,891 profile views
  1. Winapp2.ini additions

    Thanks for the new and modified entries. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/6c134ef7668f627b24bbfcc95e32fdbc4b4680a8
  2. Winapp2.ini additions

    Unfortunately, Piriform never updated the manual, so the manual still only mentions Mozilla-based browsers. But it also works for Chromium-based browsers. Correct, the section "Google Chrome" in CCleaner is responsible for all Chromium-based browsers at the same time. It is not possible to clean each of them individually. If you put only the file Winapp2.ini in CCleaner's program folder, only the entries of the file Winapp2.ini will clean the Brave browser. However, if you want a complete cleaning, with the built-in entries of CCleaner, you have to add the "CustomLocation1" in your ccleaner.ini.
  3. There are already some threads on this issue: https://forum.piriform.com/topic/53697-cookies/ https://forum.piriform.com/topic/53571-ccleaner-does-not-see-or-delete-cookies-anymore/ Maybe this will help: https://forum.piriform.com/topic/53697-cookies/?tab=comments#comment-305366
  4. Winapp2.ini additions

    The entries are listed under the section "Google Chrome", there is no separate section "Brave Browser". The entries always clean up all installed Chromium-based browsers at once. You should also add the browser 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\User Data\Default
  5. Winapp2.ini additions

    CCleaner's already built-in Site Preferences already cleans that exact file, at least in Firefox ESR Portable v60.6.1esr. That's right, thanks. After using the build-in entry, the date (and size) of the file changes. Unfortunately, the file will not be deleted. Question to all: Should we rename the entry to [Site Preferences *] and still add it for those who want to make sure that all traces are really removed? Your opinions are welcome.
  6. Winapp2.ini additions

    Thanks for the entries. In my tests the built-in entry "Firefox - Session" already cleans this folder completely.
  7. Winapp2.ini additions

    Thanks for the revised entry. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/3cde3abef95e59a5dbbf193e8c7c7e7d01f0cef3 https://github.com/MoscaDotTo/Winapp2/commit/30f6dc2c3e544c384887c09d87f17ea622140a75 https://github.com/MoscaDotTo/Winapp2/commit/a82bfb3616910b685514ec439ece079b225fb999
  8. Winapp2.ini additions

    Thanks for the update. I tested the extension and the Winapp2.ini entries [Logs *] and [Internet History *], formerly [History *], do not damage it. We fixed the entry [Logs *] some time ago and it now only removes usual logfiles. But I can confirm that the built-in entry of CCleaner [Google Chrome - Session] damages the extension. As a workaround, you can exclude the following folder in the CCleaner options: C:\Users\<your username>\AppData\Local\Google\Chrome\User Data\Default\Extension State\ Please report this bug under "CCleaner Bug Reporting": https://forum.piriform.com/forum/8-ccleaner-bug-reporting/. Thank you!
  9. Winapp2.ini additions

    Referring to the entry names you are using an old version of Winapp2.ini. Please update to the latest version.
  10. Winapp2.ini additions

    Thanks! Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/c8c6096cc27fa9e79360f2ac07cc8ef3b69c3dc5
  11. 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
  12. 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|*.*
  13. 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 *].
  14. Winapp2.ini additions

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

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