Jump to content
CCleaner Community Forums


Experienced Members
  • Content Count

  • Joined

  • Last visited

Posts posted by APMichael

  1. On 27.4.2018 at 07:06, ROCKNROLL said:

    ...Also, I am looking for someone who would be willing to spend a little time looking over the "Windows 10 Useless Files" entry and the "Useless File Extension"...


    IMHO the entry [Useless File Extension *] should be used with "Analyze" only. It would be hard work to make this entry safe.

    The entry [Windows 10 Useless Files *] seems to be wrong: The path "%ProgramFiles%\WindowsApps\Microsoft.CloudExperienceHost_*\" doesn't exist; it should be "%WinDir%\SystemApps\Microsoft.Windows.CloudExperienceHost_*\". But the sub-folder "media" doesn't contain *.mp4 files. We can correct the path and rename the entry to "Windows Apps Media Files". (Or because the files don't exist on your system also; maybe we can remove the entry then?)

  2. On 27.4.2018 at 09:13, siliconman01 said:

    In Winapp3.ini, why is [QuickLaunch *] considered dangerous?  This feature was removed in starting with Windows 7.  There is a procedure that permits users to add the Quick Launch bar back in, but I suggest that 99.9% of Windows users do not add it back in...

    The entry was removed by request: https://forum.piriform.com/topic/32310-winapp2ini-additions/?page=234&tab=comments#comment-277438.
    I was not happy about that also: https://forum.piriform.com/topic/32310-winapp2ini-additions/?page=234&tab=comments#comment-277444.

    On 27.4.2018 at 09:27, siliconman01 said:

    If this entry is not considered dangerous in Winapp3.ini, why not add it to Winapp2.ini ? [Windows Tracing *]...

    That's just a mistake; all entries should have Section=Dangerous. I can't find any information why this entry was removed from Winapp2.ini.
    (It seems that the folder isn't used by Windows anymore. On my systems the folder is empty always.)

  3. 13 hours ago, kiddac said:

    ...So I would like to know where exactly this is referencing to show this message whether it be a cookie, registry or folder...

    I checked the registry and found the following key "HKEY_CURRENT_USER\Software\AvastAdSDK\". If I delete the value "LastOffer" the Avast offer shows up again.


  4. 10 hours ago, kiddac said:

    Why do you keep posting this as an answer .. no it is not.

    It is! But if you had installed Avast already; the Avast offer won't show up again.

    Your screenshot doesn't show the first page; it's the "Customize" page! This is the first page:


  5. 15 hours ago, PICPro said:

    This is a good question.  Winapp3 isn't meant to be safe or used blindly.  Presumably people would use it by copying sections of interest to their custom.ini files, editing to their taste, run analysis only on that entry in ccleaner, open the relevant folder in explorer, look at the files to be deleted, make the decision etc. ...

    Thank you very much for your reply.

  6. Winapp3.ini:

    Thanks for your feedback.

    It seems that all GhostScript based tools use that "Fontmap.Sol" file. We could make the ExcludeKey more universal:

    [Flash Local Shared Object Files *]

    And I think we should remove the entry [Flash SOL Files *], because it deletes nothing but those GhostScript files.

    Edit: Or should we remove both entries, because Flash is a "dying" software anyway?

  7. 12 hours ago, SMalik said:

    In Windows 8/10, TokenBroker/Cache is being used to store login infos, so this should be removed from all the Windows 8/10 related entries. There was a similar issue with the [Security Service Token Cache *] entry, where Windows Insider Program account login infos were being removed.

    That's done already.

  8. 13 hours ago, SMalik said:

    You’re wrong, I have not said that in that post.

    Did you read your old post?!

    On 24.1.2018 at 22:52, SMalik said:


    This exclude key should be added into each Windows Store app entry.


    You clearly talked about "%LocalAppData%\Packages\*\AC\INetCache"!

    13 hours ago, SMalik said:

    ...I did not know much about these files at that time. When I saw that deleting these files from %LocalAppData%\Packages\appname_*\AC\TokenBroker\Cache was causing issues, I thought all those files should be excluded.

    IMHO it's not a good idea to recommend something if you don't know why... But let's forget the topic.

    BTW, I checked the container.dat files on my system. They all are empty and have 0 KB. And they get recreated after deletion. It seems there's no reason for deleting them.

  9. 1 hour ago, SMalik said:

    I have tested some other privacy cleaners and they all remove container.dat file from %LocalAppData%\Packages\*\AC\INetCache\

    I think we should remove ExcludeKeys for this from all the Windows Store apps.

    It seems that just a few apps need the ExcludeKey. But you wanted that we add the ExcludeKey to all Windows Store entries!
    Now you changed your mind again... :(

    Those apps need the ExcludeKey: Bing Weather, HuluPlus, Netflix (and maybe other?)

  10. 13 hours ago, internetaddict47 said:

    Hello, new user so sorry if been asked before: I switched from Chrome to Chrome Beta, simply copying the old user profile over in appdata. It seems that CCleaner doesn't recognize Chrome Beta. Can I use winapp2.ini to make Chrome Beta "look like" the normal Chrome to CCleaner? (e.g. replacing each entry or something?)

    You can use following methods to add other browsers:


  11. Please add an optional setting for cleaning the VirtualStore of Windows Vista and newer. If you enable this setting the variables used in FileKeys get additionally expanded to:

    %ProgramFiles% additionally to...
    %LocalAppData%\VirtualStore\Program Files
    %LocalAppData%\VirtualStore\Program Files (x86)

    %CommonAppData% additionally to...

    Older applications and games are still used by many users, but the data of those programs get redirected to the VirtualStore.
    (Another benefit of the setting would be that all VirtualStore FileKeys could be removed from winapp.ini/winapp2.ini.)

    RegKeys with "HKLM\SOFTWARE\..." should also check and clean "HKCU\Software\Classes\VirtualStore\MACHINE\SOFTWARE\...".

  12. 15 hours ago, PICPro said:

    Actually they do work in 5.40 but the entries appear as an additional section with the correct name and icon at the bottom of the applications tab.  I don't know if they work in all previous versions.  There are many people stuck at 5.26 since later versions of ccleaner don't work without an SSE2 processor.

    Thanks for the tip. I probably never checked the bottom of the applications tab! :lol:

  13. 14 minutes ago, PICPro said:

    I was just curious why in Winapp2.ini that LangSecRef=3001 or 3005 isn't used by Winapp2.ini for [Internet Explorer *] or [Microsoft Edge *] respectively.  I'm not suggesting a change as 3022 is also a good choice.

    The LangSecRefs of winsys.ini unfortunately don't work with winapp2.ini.

  14. 11 hours ago, CSGalloway said:

    Why remove [ACDSee Standard *] ??
    I use it....

    [ACDSee Photo Studio *] shows on my system, which I do not have installed....

    All "ACDSee" entries had the same FileKeys. Therefore, we merged them into one big "versions independent" entry. (Please check the first two posts.)

    [ACDSee Pro *], [ACDSee Standard *], [ACDSee Photo Studio Professional 2018 *], [ACDSee Photo Studio Standard 2018 *], [ACDSee Photo Studio Ultimate 2018 *] = [ACDSee Photo Studio *]


    10 hours ago, CSGalloway said:

    [dvdcss *] shows on my system; What is it?

    It's used for decryption of DVDs. The folder "%AppData%\dvdcss" gets created by several Media Player or DVD Copy software.

  15. Just a comment/suggestion:

    The last big overhaul merged many entries with duplicate FileKeys. Therefore, the entries count and file size was dramatically reduced. IMHO it would be wise to continue that.

    The 3 new "ACDSee" entries could be merged with the 2 existing ones into one big entry, like the many other "versions independent" entries:

    [ACDSee Photo Studio *]
    Detect1=HKCU\Software\ACD Systems\ACDSee Pro\90
    Detect2=HKCU\Software\ACD Systems\ACDSee Professional\110
    Detect3=HKCU\Software\ACD Systems\ACDSee Standard\210
    Detect4=HKCU\Software\ACD Systems\ACDSee Ultimate\110
    Detect5=HKCU\Software\ACD Systems\ACDSee\60
    FileKey1=%LocalAppData%\ACD Systems\ICMCache|*.*|RECURSE
    FileKey2=%LocalAppData%\ACD Systems\Logs|*.*|RECURSE
    FileKey3=%LocalAppData%\ACD Systems\SavedSearches|*.*|RECURSE
    RegKey1=HKCU\Software\ACD Systems\ACDSee Pro\90|HistMCFDestFolder
    RegKey2=HKCU\Software\ACD Systems\ACDSee Pro\90|HistPaths
    RegKey3=HKCU\Software\ACD Systems\ACDSee Pro\90|LastOptionPageName
    RegKey4=HKCU\Software\ACD Systems\ACDSee Pro\90|OpenFolder
    RegKey5=HKCU\Software\ACD Systems\ACDSee Pro\90\PrintOptions\OutputContactSheet|ContactSheetFN
    RegKey6=HKCU\Software\ACD Systems\ACDSee Pro\90\PrintOptions\OutputContactSheet|ImageMapFN
    RegKey7=HKCU\Software\ACD Systems\ACDSee Professional\110|HistMCFDestFolder
    RegKey8=HKCU\Software\ACD Systems\ACDSee Professional\110|HistPaths
    RegKey9=HKCU\Software\ACD Systems\ACDSee Professional\110|LastOptionPageName
    RegKey10=HKCU\Software\ACD Systems\ACDSee Professional\110|OnlineHistPaths
    RegKey11=HKCU\Software\ACD Systems\ACDSee Professional\110|OpenFolder
    RegKey12=HKCU\Software\ACD Systems\ACDSee Standard\210|HistMCFDestFolder
    RegKey13=HKCU\Software\ACD Systems\ACDSee Standard\210|HistPaths
    RegKey14=HKCU\Software\ACD Systems\ACDSee Standard\210|LastOptionPageName
    RegKey15=HKCU\Software\ACD Systems\ACDSee Standard\210|OnlineHistPaths
    RegKey16=HKCU\Software\ACD Systems\ACDSee Standard\210|OpenFolder
    RegKey17=HKCU\Software\ACD Systems\ACDSee Ultimate\110|HistMCFDestFolder
    RegKey18=HKCU\Software\ACD Systems\ACDSee Ultimate\110|HistPaths
    RegKey19=HKCU\Software\ACD Systems\ACDSee Ultimate\110|LastOptionPageName
    RegKey20=HKCU\Software\ACD Systems\ACDSee Ultimate\110|OnlineHistPaths
    RegKey21=HKCU\Software\ACD Systems\ACDSee Ultimate\110|OpenFolder
    RegKey22=HKCU\Software\ACD Systems\ACDSee\60|HistMCFDestFolder
    RegKey23=HKCU\Software\ACD Systems\ACDSee\60|HistPaths
    RegKey24=HKCU\Software\ACD Systems\ACDSee\60|LastOptionPageName
    RegKey25=HKCU\Software\ACD Systems\ACDSee\60|OpenFolder
    RegKey26=HKCU\Software\ACD Systems\ACDSee\60\PrintOptions\OutputContactSheet|ContactSheetFN
    RegKey27=HKCU\Software\ACD Systems\ACDSee\60\PrintOptions\OutputContactSheet|ImageMapFN
    RegKey28=HKCU\Software\ACD Systems\EditLib\Presets\Photo Repair 2|Last Used


  16. 6 minutes ago, SMalik said:

    Removing files from that location removed login information of Windows Insider account on a Windows 10 Insider Preview (build 17083.1000), which I have reported.
    Otherwise, it is recommended to empty this cache and I tested this on a Windows 10 (build 16299.192), no issues. I just forgot to mention this in that post.

    I should not have reported the Windows Insider account issue here since it was with a preview build.

    I always use the latest Winapp2.ini file. I have put those entries in order, that is why the order is changed.

    I am not asking to change the sort order of all the entries that are already there, but at least from now on we can keep the order. This way, it is easy to locate the location or path when modifying an entry with lots of Filekeys or RegKeys.

    Thanks for your clarification. Ok, but changing the sort order of new entries will break WinappDebug/Winapp2ool. I personally prefer alphabetical order, but let’s wait for other comments.

  • Create New...