Jump to content
Piriform Community Forums

APMichael

Members
  • Content count

    511
  • Joined

  • Last visited

Everything posted by APMichael

  1. Winapp2.ini additions

    Thank you very much for all your replies and entries. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/26cd94044d952b62d0782a06c86eaf6f6d22eeb2
  2. Winapp2.ini additions

    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... 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.
  3. Winapp2.ini additions

    @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
  4. Winapp2.ini additions

    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.
  5. Winapp2.ini additions

    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.
  6. Winapp2.ini additions

    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...
  7. Winapp2.ini additions

    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?
  8. Winapp2.ini additions

    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.) 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!
  9. Winapp2.ini additions

    Thank you for your research. Should we update the entry or should we wait to see if it's just related to the insider build?
  10. Winapp2.ini additions

    Yes, we might want to think about that. But usually all removed keys or entries are moved to the Winapp3.ini.
  11. Winapp2.ini additions

    Thanks for the new and revised entries. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/cccdfc0b67f2b5e55cc7e598f2ddf9e2746db5d0
  12. Winapp2.ini additions

    What a strange error! Since the file "Windows.edb" is not really crap (only if you have disabled the service "Windows Search", but this is not the system default), removing the FileKey should not be a problem.
  13. Winapp2.ini additions

    Is the file no longer locked by the "Windows Search" service? Normally, you cannot delete it without stopping the service.
  14. Winapp2.ini additions

    The use of PATH is correct, but also requires the "\|*.*" at the end. 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.
  15. Winapp2.ini additions

    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.)
  16. I can't confirm this behavior. It works for me. (I also tested it with a file trimmed by Winapp2ool.)
  17. But unfortunately, not without networking. They want to fix it, but it's still not done. https://forum.piriform.com/topic/52593-ccleaner-beta-v5476700/?tab=comments#comment-299569 https://forum.piriform.com/topic/52921-bugs-ccleaner-v5496856/?tab=comments#comment-301268
  18. Avast Hidden Install

    The installer does not offer Avast (or Chrome) for every installation, only occasionally. If the first page is empty, nothing additional will be installed. This is the first page of the installer:
  19. Winapp2.ini additions

    Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/cac3e7778713681a5fb7d6197f5e727e55fce761
  20. Winapp2.ini additions

    Thank you for your entries and replies. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/191b47035c1058c4d13c193ebdc985b39ed5511b https://github.com/MoscaDotTo/Winapp2/commit/3eaeadc81a19f095c54ac25f5da80a94e608b8e4
  21. Winapp2.ini additions

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

    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?
  23. Winapp2.ini additions

    Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/a59462c95d7b9325b365364d4d5510fad4c2ddb9
  24. Winapp2.ini additions

    Ok, thanks for the information. We can add a "warning" to the entry.
  25. Winapp2.ini additions

    Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/6b7f866eb09f7cb5e1b3c516563b66622a3dc4c8 https://github.com/MoscaDotTo/Winapp2/commit/c933cfeb6b3558fc8c2d796552ba6fc167334c09
×