Jump to content
Piriform Community Forums

APMichael

Members
  • Content count

    514
  • Joined

  • Last visited

Posts posted by APMichael


  1. 14 hours ago, SMalik said:

    @APMichael

    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.


  2. @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.

    https://www.microsoft.com/en-us/p/dell-mobile-connect/9nx51w9gbs5t
    https://www.microsoft.com/en-us/p/dell-customer-connect/9nf0ggq5s6qx

    On 9.2.2019 at 17:57, siliconman01 said:

    Several new entries for Dell Apps in Windows Store

    [Dell Mobile Connect *]
    LangSecRef=3031
    Detect=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\DellInc.DellCustomerConnect_htrsf667h5kn2
    Default=False
    FileKey1=%LocalAppData%\Packages\DellInc.DellCustomerConnect_*\AC\Microsoft\CryptnetUrlCache\*|*.*|RECURSE
    FileKey2=%LocalAppData%\Packages\DellInc.DellCustomerConnect_*\AC\Temp|*.*|RECURSE
    FileKey3=%LocalAppData%\Packages\DellInc.DellCustomerConnect_*\LocalCache\Local\Microsoft\CLR_v4.0_32\UsageLogs|*.log
    FileKey4=%LocalAppData%\Packages\DellInc.DellCustomerConnect_*\LocalState\serilog|*.txt
    FileKey5=%LocalAppData%\Packages\DellInc.DellCustomerConnect_*\TempState|*.*|RECURSE
    ...


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

    wa2_search.jpg.bfe30df2e4a46998f0b672e6a4a047d6.jpg


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


  5. 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?


  6. 12 hours ago, SMalik said:

    ... entries require the system to be restarted to wipe those traces successfully.

    Can you please explain a little more? You mean that the system should be rebooted immediately after using CCleaner, right? Is the reason that Windows caches the content in the memory (RAM)? Or what else does the reboot do? Files that CCleaner can not delete are also not deleted after a reboot, right? (I ask this because I usually don't reboot after cleaning and I haven't noticed any side effects yet.)

     

    12 hours ago, SMalik said:

    By the way, I always wipe PropMap and SecStore in Windows Search and I have never gotten any errors related to Search in Event Viewer. ...

    I think that's the only thing we should be judging. Are there errors due to the current entry or not? Unfortunately I have disabled Windows Search on all my systems, so I can't help here. Can someone else please tell here if the entry causes errors on their system? Thanks!


  7. 15 hours ago, Andavari said:

    Does this look right to exclude that whole path you refer to?
    ExcludeKey1=PATH|%LocalAppData%\Packages\Microsoft.Windows.Cortana_*\LocalState\|DeviceSearchCache

    Edit:
    Couldn't get it to exclude using a path, however I got this to work as intended:
    ExcludeKey1=FILE|%LocalAppData%\Packages\Microsoft.Windows.Cortana_*\LocalState\DeviceSearchCache\|*.*

    The use of PATH is correct, but also requires the "\|*.*" at the end.

    15 hours ago, Andavari said:

    Also the way you suggest to restore Cortana functionality does not work if Cortana is purposely disabled by the user, and the user is instead just using it as a normal local search, hence the reason I use a batch script to restore the functionality.

    Strange, I have disabled Cortana on all my systems (using group policies) and was able to restore it (rebuild those cache files) using the suggested way.


  8. We revised the entry [Cortana *] a few weeks ago because it always broke the search for settings. We fixed that by adding an ExcludeKey for a cache file ("SettingsCache.txt"). But now it looks like the other files ("AppCache###.txt") should not be deleted either. I think we should then exclude the entire folder ("\LocalState\DeviceSearchCache").

    (An easy way to restore Cortana: Right-click on the Cortana icon and click on "More" and then on "App Settings". Now click on "Reset" and wait a few seconds.)


  9. 2 hours ago, siliconman01 said:

    There is a major problem with the TRIM function in this version.  It does not honor SECTION=.  It trims out all the modules with SECTION= ...

    Did you disable "Download" (2. Toggle Download)? It is now enabled by default and therefore Trim ignores your local winapp2.ini file.


  10. 2 hours ago, siliconman01 said:

    Modified Entry:  [Extensions Databases *]

    This entry is causing problems with False Detections with the Malwarebytes Browser Extension for Chrome.  ...

    Thank you for your information and research.
    I wonder about the entry, because why would anyone want to delete all databases of all installed extensions? Doesn't this reset all extensions?
    I think we should move the entry to the winapp3.ini. Does everyone agree?

×