Jump to content
CCleaner Community Forums


Experienced Members
  • Content Count

  • Joined

  • Last visited

Posts posted by APMichael

  1. 13 hours ago, Andavari said:

    Sorry for the confusion, I do NOT have the ExcludeKey. Possibly confused during posting because I was tired and looking at what's been posted on here and what's in two different cleaning programs using two different versions of supposedly the same cleaning entry.

    Trying to determine why CCleaner is no longer breaking it even though as you say it's essentially the same as before, and why BleachBit always breaks it.
    Edit: Maybe ignore the BleachBit stuff and only focus on what's here for CCleaner. Why am I making this more confusing.:lol:

    Thanks again, for your reply.

    E1: The ExcludeKey of the BleachBit entry is no longer necessary, we removed it some time ago. And it couldn't be the culprit for the issue. Even the wildcards in the directory names don't change the situation, only changes have been made to make the entry easier to read.

    E2: The FileKey9 of the BleachBit entry is also not necessary as it is already covered by FileKey6. They have removed the same files.

    So, if you really don't use the ExcludeKey you posted here, then it's very strange that your entry doesn't break Cortana anymore, because without the ExcludeKey the same files will be deleted as with the BleachBit entry. Would it be too much to ask, if you would please post your complete entry here?

  2. 15 hours ago, siliconman01 said:

    [iTunes App *] would work just fine.

    FileKey3 is correct as shown.  See pic. ...

    Thanks for your clarification.

    2 hours ago, siliconman01 said:

    Modified entry:  [FilmOn Live TV *]

    Changed name from [FilmOn *] to [FilmOn Live TV *]

    Detect=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\FilmOnLiveTVFree.*_zx03kxexxb716 ...

    Unfortunately CCleaner does not support wildcards in registry keys. You need to add an additional Detect.

  3. 1 hour ago, siliconman01 said:

    Modified entry:  [iTunes *]
    Changed name from [Apple iTunes *] to [iTunes *] ...

    This is not possible because the desktop version already uses this name. We could leave the name unchanged or use [iTunes App *]. The "App" is also used by some other apps, e.g. [ShareX App *].

    On 24.2.2019 at 05:57, siliconman01 said:

    Modified entry:   [My Office *]
    FileKey3=%LocalAppData%\Packages\Microsoft.MicrosoftOfficeHub_*\AC\Packages\Microsoft.MicrosoftOfficeHub_*\AC\INetHistory\History.*\*|*.*|REMOVESELF ...

    Just to be safe: Is this a copy and paste error or is the path correct? Because of the double "Packages\Microsoft.MicrosoftOfficeHub_*\AC".

  4. 3 hours ago, Andavari said:

    I have exactly as it's quoted in your post, and it hasn't been breaking anything as I reported, and I've been checking several times a day for breakage.

    Previously when the breakage was happening and I reported it I could replicated the breaking each and every time after a reboot, and I haven't had to run that .bat script anymore either to Reset And Rebuild Search Index. Although my laptop has received at least two Automatic Updates for v1803 that I'm fully aware of since I first reported having an issue with the cleaning, now rather that's a coincidence I haven't a clue.

    Ok, thank you very much for your fast reply. I'm very sorry, but now I have to bother you again: If your entry is exactly like in my post, then your entry has an ExcludeKey? Or do we have a misunderstanding? (Because the main question of the current discussion is whether we need to exclude files or not.)

    If your entry has an ExcludeKey, we know why your entry no longer breaks Cortana. If your entry doesn't have an ExcludeKey, it's even stranger, but maybe the "SettingsCache.txt" file is only important for non-English systems.

    The BleachBit entry is the same as the current winapp2.ini entry, but without the correct ExcludeKey.

  5. Here is a compromise to end this little drama:

    [Cortana *]
    Detect1=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\Microsoft.Cortana_8wekyb3d8bbwe
    Detect2=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\Microsoft.Windows.Cortana_cw5n1h2txyewy
    FileKey4=%LocalAppData%\Packages\Microsoft.*Cortana_*\AC\Microsoft\Internet Explorer\DOMStore|*.*|RECURSE

    The ExcludeKey for the single file "SettingsCache.txt" is definitively necessary, because I can still easily repro the issue on every system I tested, even v1803. And we also had an issue report on GitHub. Ok, since the second issue only occurs under special conditions, we try it once again without excluding the files "AppCache###.txt". But if we should get a new issue report, here or on GitHub, we will change the ExcludeKey back.

    I hope everybody will be happy now and we can close this topic.


    19 hours ago, Andavari said:

    It doesn't cause me any issues on Win10 v1803 - I haven't been offered v1809. I tried to post this last night but some forum server error prevented it. ...

    Thanks for your information. But this is very strange, because the changed FileKey9 you are using now deletes the same files as the previous FileKey of the entry that caused issues on your system. But anyway, let's just wait and see if the issue recurs. Just to make sure: You then also removed the ExcludeKey from your own entry? Or is there still an ExcludeKey in your entry?

  6. 14 hours ago, SMalik said:

    Sure, here is another statement. ...

    Again, please read what I wrote:

    23 hours ago, APMichael said:

    ... If you just delete the files "AppCache###.txt" and reboot immediately, the error mostly does not occur. ...

    The second error does not always occur immediately. And we don't know if he also tested the search for settings.


    14 hours ago, SMalik said:

    How about a bunch of AppCache**.txt files? Have you opened one of them to see  what they have in them?

    Yes, I know the contents of the files. But this doesn't matter if the entry breaks a function.

  7. On 22.2.2019 at 23:05, SMalik said:

    Deleting these .txt files from that location in Cortana doesn't break Cortana. Have you tried this yourself? ...

    Sure, I tested it. And only for you I have tested it again now and the problems are still occurring!

    1. Settings search error
    - Search for an option of the Settings app, e.g. Lock screen (in German it is called Sperrbildschirm).
    - Now delete the file "SettingsCache.txt" and reboot.
    - After the reboot, the search for settings is broken.


    2. Application search error
    If you just delete the files "AppCache###.txt" and reboot immediately, the error mostly does not occur. But I could repro it very often this way:
    - Search for an application, e.g. Firefox, and reboot.
    - After the reboot, search for an application again. Now there should be more than two "AppCache###.txt" files in the folder.
    - Delete all "AppCache###.txt" files and reboot.
    - After the second reboot, the search for applications is also broken.


    It would be very nice and fair if you would also trust other people and not always just yourself.

  8. 16 hours ago, Nergal said:

    Why not use detectspecial firefox instead of the limited detects you used.

    If you use SpecialDetect, the Detects and DetectFiles for the other browsers will be ignored. This is a strange behavior of CCleaner. And that's why we don't use SpecialDetect in Winapp2.ini anymore.

  9. 17 hours ago, SMalik said:

    ... There is no harm in deleting files with the .txt extension from %LocalAppData%\Packages\Microsoft.Windows.Cortana_*\LocalState\DeviceSearchCache ...

    I'm sorry, but you're wrong. If you delete the *.txt files, you're breaking Cortana. Please read the previous posts (have you ever read what other people have written?) and the issue report on GitHub. After a reboot, the search for settings and applications no longer works correctly. And please don't discuss this any further with me, because other people (not me) have reported the problems and also confirmed the fix. Thanks for respecting that!

    17 hours ago, SMalik said:

    ... Short paths like "\*Cache" or "\INet*" should not be used. I don't know of any other privacy cleaning programs that use this pattern. ...

    This has already been discussed. By the way, why do you always care what other cleaners do? If every cleaner would do the same, then it is not necessary to have different cleaners...

    17 hours ago, SMalik said:

    ... Filekey1 thru 6 has "\Microsoft.*Cortana_*" and Filekey7 thru 9 has "Microsoft.Windows.Cortana_*". I wonder why? ...

    Because this is one of the few remaining entries that combines the version of Windows 8/8.1 and Windows 10. Therefore it has two different Detects.

  10. 43 minutes ago, siliconman01 said:

    "We should then add DetectOS=6.2|6.3 to the existing entry [Microsoft Reader *]."  I assume that you will make this change, eh?? ...

    Sure, I will add it.

    43 minutes ago, siliconman01 said:

    In Windows 10, the app is named Microsoft News. ...

    Ok, sorry, I didn't know that, because I have a non-English Windows and always remove all pre-installed apps.

  11. 2 hours ago, siliconman01 said:

    New Entries: [Money *]  [Sports *]  [Microsoft News *]

    Note:  These are the replacements for Bing Finance, Bing Sports, and Bings News.  I do not know if these Bing entries are still valid for Windows 8/8.1 plus they are in Winapp.ini.  Therefore I used DetectOS=10.0|  to restrict the new entries to Windows 10. ...

    I would suggest that we rename the existing entry [News *] to [Bing News *] and add DetectOS=6.2|6.3 (as with the other Bing entries). And rename your new entry [Microsoft News *] to [News *].


    2 hours ago, siliconman01 said:

    New entry:  [Reader *] 

    This is the Windows 10 version of [Microsoft Reader *]...again I do not know if that is what is still required for Windows 8/8.1 ...

    We should then add DetectOS=6.2|6.3 to the existing entry [Microsoft Reader *].

  12. 14 hours ago, SMalik said:


    Like I said before, CCleaner can't wipe some of the traces in the entries listed below successfully because some of the traces are locked by Windows or programs similar to MS Search. Let's remove all of these. ...

    No, why should we? You obviously did not read what siliconman01 and I wrote: If the current entry is used without "Windows Safe Mode", it BREAKS the "Windows Search". And that is the big difference to the entries you mentioned! Because the other entries do not break anything! The reason why we will remove the FileKeys is not that CCleaner cannot delete these files or that "Windows Safe Mode" is needed for a complete cleaning, they are removed because they BREAK a function. When an entry or key breaks a function, it is removed, that was always the policy. So please calm down and do not take such things personally. By the way, there were many entries that were removed only on your request, while other people still liked the entries...

    10 hours ago, SMalik said:

    I’m not taking it personally, but it’s hard work. Some people here make smaller things seem much bigger, without understanding the context behind it. All known privacy cleaner programs wipe these traces in Windows Search. These traces can hold all search related things, which is a privacy concern.

    Right, the rest of us are not working hard at it at all. Thank you so much for your appreciation.

    As long as CCleaner is not able to remove locked files, a few entries will not work as in other cleaner programs that have this ability. Therefore, CCleaner cannot be fully compared with these programs. Yes, it may be a privacy concern in this case, but with the limited functions of a Winapp2.ini respectively CCleaner it is not possible to make a safe/harmless entry. But people who are more familiar with Winapp2.ini can still easily add their own entries. (Thanks to Winapp2ool this is now very easy.) And these people will also know how to use "Windows Safe Mode" for some of the entries.

  13. @siliconman01 Just to be safe: Is the name of the entry correct? Because there is a "Dell Mobile Connect" app and a "Dell Customer Connect" app.


    On 9.2.2019 at 17:57, siliconman01 said:

    Several new entries for Dell Apps in Windows Store

    [Dell Mobile Connect *]
    Detect=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\DellInc.DellCustomerConnect_htrsf667h5kn2

  14. I enabled "Windows Sarch" again and did some tests. Now I can confirm that the current entry causes multiple "Search" errors and a rebuild of the index after a reboot. The reason for this behavior is that the .000 files are locked and CCleaner cannot delete them. The only way to avoid this problem is to use "Windows Safe Mode". But using "Windows Safe Mode" for CCleaner is not the default and we cannot force users to use it either.

    Since the current entry breaks "Windows Search" (if CCleaner is used as usual) and therefore always causes a rebuilding of the search index, the corresponding keys should be moved to Winapp3.ini.


  15. I just wanted to say that if [MS Search *] is supposed to be an entry that needs a reboot for a successful cleanup, why do the errors only occur after a reboot? Then the theory with the necessary reboot cannot be completely correct.

  16. 5 hours ago, siliconman01 said:

    In my opinion it is not the intent of the CCleaner developers to force or advocate users to reboot their system following using CCleaner.  ...

    Yes, this cannot be intentional, as it would also collide with the "Smart Cleaning" or "Schedule" function of CCleaner. By the way, you have the "Search" errors even though you rebooted Windows after using CCleaner, right? So a reboot didn't help...

  17. 10 hours ago, SMalik said:

    The programs I mentioned in my previous post wipe the traces and then restart the system to wipe files locked by Windows or other programs.

    Ok, thanks for your reply. But this is a special feature of the other programs, they delete these locked files in a special phase of the boot process. I don't think you can do the same by simply rebooting Windows manually after using CCleaner. Whether Windows is rebooted manually after using CCleaner or not should not matter then, because CCleaner can't delete these files anyway, right?

  • Create New...