Jump to content
CCleaner Community Forums


  • Content count

  • Joined

  • Last visited

Posts posted by APMichael

  1. 9 hours ago, SMalik said:

    Revised Entry

    Changed [Updates *] to [Google Update *]
    Changed LangSecRef=3029 to LangSecRef=3021 ...

    Thanks for the revised entry, but did you see that the entry [Updates *] also contains FileKeys for other Chromium-based browsers? I think you just want to separate Google Update because it also updates other Google software, right? Then I suggest that we use the following entries:

    [Updates *]
    [Google Update *]

    Google Update can also be found at %LocalAppData%\Google\Update\, e.g. if you install Google Chrome Canary.


  2. On 9.5.2019 at 02:43, CSGalloway said:

    New Entry

    [OE Classic*] ..

    Not sure of the ocorrect value for LanSecRef = can't find it documents on here...

    I guess it should be LangSecRef=3022 (= Internet).

    For the readme simply click on the GitHub link in the first post.

    Edit: Sorry, LangSecRef for the category Internet is 3022. :lol:

  3. 16 hours ago, Winapp2.ini said:

    Would all subkeys of \Profiles\Outlook\*****  necessarily be a profile folder? If so this wouldn't be too difficult to create support for, I don't think.

    As far as I know, every subkey of \Profiles\ is a profile. The default profile name is Outlook, but you can also add additional profiles, e.g.:


  4. Winapp2.ini updates:


    On 5.5.2019 at 07:53, ricktendo64 said:
    [Outlook Recent Searches *] ...

    I post the default profile name Outlook but this may vary, is there a way for winapp2ool to query the registry for the profile name and replace "Outlook"?

    I have added your entry to Winapp2.ini. I guess it will work for most Outlook users. Maybe @Winapp2.ini can add this feature in a future version of Winapp2ool.

  5. 2 hours ago, siliconman01 said:

    Thanks for incorporating the MS Edge Insider cleaning modules.  This new browser is working great on my systems.  B)

    Thank you very much for providing most of the them! :) I think MS will certainly be more successful with the new Edge.

  6. 12 hours ago, don_dolarson said:

    I don't think you sent me the right link because everything in there is about Mozilla based browsers, not Chromium. Not even "CustomLocation" exist in ccleaner.ini

    Do you mean that the "Chrome" section in CCleaner (both for app cleaning in the main cleaning section and in settings for saving cookies) is responsible for both Chrome and Brave at the same time and I can't clean each of them, separately? Does it work out of the box CCleaner + winapp2.ini then or do I need to make some changes?

    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.

  7. 2 hours ago, don_dolarson said:

    How to get cookies and all clean up stuff visible for Brave browser? Brave lines exists in winapp2 file, but can't see anything about Brave inside CCleaner.

    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:


    Example: CustomLocation1=CHROME|C:\Users\<your user name>\AppData\Local\BraveSoftware\Brave-Browser\User Data\Default

  8. 14 hours ago, Andavari said:
    On 13.4.2019 at 22:36, SMalik said:

    [Permissions *] ...
    FileKey2=%AppData%\Mozilla\Firefox\Profiles\*|permissions.sqlite ...

    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.

  9. 13 hours ago, SMalik said:

    ... [Sessionstore Backups *] ...
    FileKey2=%AppData%\Mozilla\Firefox\Profiles\*\sessionstore-backups|*.*|RECURSE ...

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


  10. 3 hours ago, 212eta said:

    ... The last release of winapp2.ini STILL includes entries Logs*  and Session which BOTH damage the respective Chrome Extension.

    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!

  11. 2 hours ago, 212eta said:

    ... When selecting the Winapp2.ini entries: Extensions State*, History*, and Logs*, the above Chrome Extension becomes neutralized (i.e. it becomes no longer available via the Right-Click). ...

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

  12. 17 hours ago, Andavari said:

    Didn't know that, I only used it to create a USB Flash Drive installer...

    Thanks for your reply.


    12 hours ago, CSGalloway said:

    I see an entry for [Auslogics Registry Defrag*] is in the winapp2.ini but not showing up on my system. I am using windows 7 x64...

    This should work (Detect does not require "Wow6432Node"):

    [Auslogics Registry Defrag *]
    Detect1=HKCU\Software\Auslogics\Registry Defrag
    Detect2=HKLM\Software\Auslogics\Registry Defrag
    FileKey1=%AppData%\Auslogics\Registry Defrag\Logs|*.*
    FileKey2=%AppData%\Auslogics\Registry Defrag\Reports|*.*
    FileKey3=%CommonAppData%\Auslogics\Registry Defrag\*.x\Reports|*.*

  13. Quote

    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 *].