Jump to content

APMichael

Experienced Members
  • Posts

    984
  • Joined

  • Last visited

Everything posted by APMichael

  1. 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.
  2. 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.
  3. 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...
  4. 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?
  5. 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!
  6. 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?
  7. Yes, we might want to think about that. But usually all removed keys or entries are moved to the Winapp3.ini.
  8. Thanks for the new and revised entries. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/cccdfc0b67f2b5e55cc7e598f2ddf9e2746db5d0
  9. 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.
  10. Is the file no longer locked by the "Windows Search" service? Normally, you cannot delete it without stopping the service.
  11. 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.
  12. 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.)
  13. I can't confirm this behavior. It works for me. (I also tested it with a file trimmed by Winapp2ool.)
  14. 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
  15. 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:
  16. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/cac3e7778713681a5fb7d6197f5e727e55fce761
  17. Thank you for your entries and replies. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/191b47035c1058c4d13c193ebdc985b39ed5511b https://github.com/MoscaDotTo/Winapp2/commit/3eaeadc81a19f095c54ac25f5da80a94e608b8e4
  18. Did you disable "Download" (2. Toggle Download)? It is now enabled by default and therefore Trim ignores your local winapp2.ini file.
  19. 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?
  20. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/a59462c95d7b9325b365364d4d5510fad4c2ddb9
  21. Ok, thanks for the information. We can add a "warning" to the entry.
  22. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/6b7f866eb09f7cb5e1b3c516563b66622a3dc4c8 https://github.com/MoscaDotTo/Winapp2/commit/c933cfeb6b3558fc8c2d796552ba6fc167334c09
  23. The offer for Avast is only displayed on the first page of the setup. https://forum.piriform.com/search/?&q=avast install&type=forums_topic&nodes=4&sortby=newest
  24. Did you also untick all checkboxes under "Options" > "Smart Cleaning"?
  25. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/66012b611495accc847e136e5180d6ba77ef6c81 https://github.com/MoscaDotTo/Winapp2/commit/c52a6dd1c7021fbfc583412e0a8707c2b1aec930
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.