Jump to content
CCleaner Community Forums

APMichael

Experienced Members
  • Content Count

    679
  • Joined

  • Last visited

Posts posted by APMichael


  1. Thanks for the replies.

    11 hours ago, SMalik said:

    ... but [Omnibox Shortcuts *], [Quota Manager Data *] and [Web Data *] are not in CCleaner's built-in entries.

    ... but [DOM Store *] entry is not in CCleaner's built-in entries.

    I'm not sure we've misunderstood each other. Therefore a little more detailed: Please use the built-in entries I mentioned and check the modification date of the files before and after cleaning. You will see that the modification date changes, so that CCleaner at least opens these files and accesses the content/database. There are some other built-in entries that just clean the content/database instead of deleting the file itself. That's why I ask the community for their experiences with these entries. If we don't get enough information, we'll leave it as it is.


  2. Question to all:

    The files of the following entries are also cleaned by CCleaner. Since I don't have Chrome in my daily use, I can't tell if CCleaner deletes the contents completely or only partially. It would be great if you could share your experiences and recommend which entries possibly could be removed. Many thanks in advance.

     

    Chrome/Chromium:

    [FlashPlayer SharedObjects *] ...
    FileKey13=%LocalAppData%\Google\Chrome*\User Data\*\Pepper Data\Shockwave Flash\WritableRoot\#SharedObjects|*.*|RECURSE ...

    The built-in entry "Cookies" cleans this location.

    [Local Storage *] ...
    FileKey13=%LocalAppData%\Google\Chrome*\User Data\*\Local Storage|http*.*|RECURSE ...

    In my tests, this entry never deletes a single file. It seems that "Local Storage" has been switched to Level-DB and the entry is outdated.
    Edit: The built-in entry "Cookies" cleans the "http*.*" files.

    [Omnibox Shortcuts *] ...
    FileKey13=%LocalAppData%\Google\Chrome*\User Data\*|Shortcuts ...

    The built-in entry "Internet History" cleans this file.

    [Quota Manager Data *] ...
    FileKey13=%LocalAppData%\Google\Chrome*\User Data\*|QuotaManager ...

    The built-in entry "Cookies" cleans this file.

    [Web Data *] ...
    FileKey13=%LocalAppData%\Google\Chrome*\User Data\*|Web Data ...

    The built-in entries "Internet History" and "Saved Form Information" clean this file.

     

    Firefox:

    [Anti-Phishing Data *] ...
    FileKey2=%LocalAppData%\Mozilla\Firefox\Profiles\*|urlclassifier3.sqlite ...

    Mozilla stopped using and supporting this file a long time ago. It seems that the entry is outdated.

    [DOM Store *] ...
    FileKey2=%AppData%\Mozilla\Firefox\Profiles\*|webappsstore.sqlite ...

    The built-in entry "Cookies" cleans this file.


  3. Thank you for your quick reply and clarification. Okay, then we will split the entry.

    13 hours ago, SMalik said:

    %LocalAppData%\Google\Chrome*\User Data|*-journal ...
    Safe Browsing Cookies-journal file is already in CCleaner's Internet Cache entry. ...

    Unfortunately, CCleaner only deletes this file for the few Chromium-based browsers that CCleaner directly supports. If you need to use "CustomLocation", CCleaner does not delete the file. Therefore, we should keep these FileKeys.


  4. 13 hours ago, SMalik said:

    Changed name from [Internet Cache *] to [Network Persistence Statistics *] ...

    IMHO, the current name of the entry fits better because the *-journal files are typical cache and the *.ldb/*.log files caches download links, for example.

    13 hours ago, SMalik said:

    I have CCleaner v5.57. Looks like the cookies cleaning issue has been fixed. So I think the [Cookies *] entry should be removed from Google Chrome.

    Also, [Internet History *] should be removed from Google Chrome. CCleaner does the job now.

    CCleaner has been cleaning these files for a long time. But such entries have been added because CCleaner does not delete the files itself, so traces may be left. There are also some other such entries under Chrome and Firefox.

    11 hours ago, SMalik said:

    [Stored Explorer View *] ...

    This is already covered by the entry [Windows ShellBags *]. Is a separate entry necessary?


  5. 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 *]
    LangSecRef=3029
    Detect1=HKCU\Software\BraveSoftware
    Detect2=HKCU\Software\CocCoc\Browser
    Detect3=HKCU\Software\Torch
    Default=False
    FileKey1=%LocalAppData%\CocCoc\Update\Download|*.*|RECURSE
    FileKey2=%LocalAppData%\CocCoc\Update\Install|*.*|RECURSE
    FileKey3=%LocalAppData%\CocCoc\Update\Offline|*.*|RECURSE
    FileKey4=%LocalAppData%\Torch\Update\Download|*.*|RECURSE
    FileKey5=%LocalAppData%\Torch\Update\Install|*.*|RECURSE
    FileKey6=%LocalAppData%\Torch\Update\Offline|*.*|RECURSE
    FileKey7=%ProgramFiles%\BraveSoftware\Update\Download|*.*|RECURSE
    FileKey8=%ProgramFiles%\BraveSoftware\Update\Install|*.*|RECURSE
    FileKey9=%ProgramFiles%\BraveSoftware\Update\Offline|*.*|RECURSE
    
    [Google Update *]
    LangSecRef=3021
    Detect=HKCU\Software\Google\Update
    Default=False
    FileKey1=%LocalAppData%\Google\Update\Download|*.*|RECURSE
    FileKey2=%LocalAppData%\Google\Update\Install|*.*|RECURSE
    FileKey3=%LocalAppData%\Google\Update\Offline|*.*|RECURSE
    FileKey4=%ProgramFiles%\Google\Update\Download|*.*|RECURSE
    FileKey5=%ProgramFiles%\Google\Update\Install|*.*|RECURSE
    FileKey6=%ProgramFiles%\Google\Update\Offline|*.*|RECURSE

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

    google_update.jpg.5b415e29fa660b65603e27ccebba9d88.jpg


  6. 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:


  7. 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.:

    HKCU\Software\Microsoft\Office\16.0\Outlook\Profiles\Outlook\
    HKCU\Software\Microsoft\Office\16.0\Outlook\Profiles\Personal\
    HKCU\Software\Microsoft\Office\16.0\Outlook\Profiles\Work\


  8. Winapp2.ini updates:
    https://github.com/MoscaDotTo/Winapp2/commit/6fd8702ce4d928f6badf2a5cad71ef60b5e0c916
    https://github.com/MoscaDotTo/Winapp2/commit/aa24a3cf03958bfbeed353377cf7bc1d671f9b5b
    https://github.com/MoscaDotTo/Winapp2/commit/6787d6577e582237ec3d9ab5f895c63638dc9b9f

     

    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.


  9. 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.


  10. 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.


  11. 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:
    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


  12. 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.


  13. 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.

    cc_ff_session.jpg.7697bd4171e6bf9e6da74aa20d1edc9e.jpg


  14. 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.

    wa2_ext_tst_1.jpg.91d59d0de0c713400f3477a27d3305be.jpgwa2_ext_tst_2.jpg.727fa7653ec586c50b7dbe3857fa50f3.jpg

     

    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!


  15. 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.

×
×
  • Create New...