Jump to content
CCleaner Community Forums

APMichael

Experienced Members
  • Content Count

    776
  • Joined

  • Last visited

Everything posted by APMichael

  1. Thanks for your fast feedback, too. Unfortunately, siliconman01 reports a problem with a Chrome extension. Therefore, we have to add the ExcludeKeys to the entry [Logs *] again. Suggestion: Should we move the *.old cleaning into a new entry, e.g. [Logs old *]?
  2. Thanks for your fast feedback. Unfortunately, I can't reproduce this problem. This should only happen if the spartan.edb file gets removed, but the file is protected by an ExcludeKey. (The "DBStore" FileKey and ExcludeKeys were used for a long time previously, without any problem report.) Not good, then we have to add the ExcludeKeys to the entry [Logs *] again.
  3. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/1ba2e70cea37cb24a01de505f9e6f2ea32b76a72
  4. Sorry, but I didn't define that "policy". The community decided not to include such files from security programs! Feel free to start a survey on whether the community wants to include the definition backups in Winapp2.ini again. (BTW I use that FileKey in my custom Winapp2.ini also.)
  5. Correct, the entries for cleaning old definitions of "Microsoft Security Essentials" and "Windows Defender" are in Winapp3.ini already. I opened a pull request for all revised entries and suggestions: https://github.com/MoscaDotTo/Winapp2/pull/301. If no one objects on GitHub, I will merge it on Wednesday.
  6. Thanks for the hint! I don't use Chrome, therefore I can't test it. I will wait 2-3 days before updating Winapp2.ini, because maybe someone will object. I can confirm this. CCleaner can't remove the files.
  7. Thank you for your revised entries. The entry [Logs *] should remove those .old files already: FileKey23=%LocalAppData%\Google\Chrome*\User Data\*|*LOG.*;Log;*.log;*.old|RECURSE
  8. Why didn't you just update to the latest version? The "bug" is fixed already.
  9. I can confirm this bug! (Workaround: add HelpImproveCCleaner=0 to ccleaner.ini or the registry.)
  10. Like nukecad has described already: CC disappears without any error message as soon as "Analyze" or "Run Cleaner" reaches 100%. JFYI: This doesn't happen when using "Safe Mode with Networking" (boot option 5).
  11. Thank you for the new Beta programme. I can confirm that context menu and command line cleaning are working again! But still not fixed: crashing in Windows Safe Mode (boot option 4).
  12. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/043ba42e0fa0b94c3d1c772ad3f5a28a102833b6 https://github.com/MoscaDotTo/Winapp2/commit/9dd627fc8ece26aabec47fd80c12d756a2f19ab2
  13. CCleaner doesn't change the "CustomLocationX" entries. Your "CustomLocationX=FIREFOX|..." entries for Waterfox should work (Waterfox). If the option "Save all settings to INI file" is checked and you don't have a correct "ccleaner.ini" file in the installation folder, then the installation is corrupt. That's probably the reason why the "CustomLocationX=FIREFOX|..." entries don't work also. I assume that you have accessed the build-in "winapp.ini" (this "file" isn't visible by default) with Resource Hacker and not the "ccleaner.ini" file, because that phrase isn't in a "ccleaner
  14. Strange! Maybe uninstalling and reinstalling CCleaner will fix it?
  15. Is "Save all settings to INI file" under Options > Advanced checked?
  16. Edge is a system app and you can uninstall it only with "workarounds". Did you really do this? Apart from this, please check the following: - Open the "Settings" App. - Click on "Apps". - Click on "Default apps". - Check that Edge is not the "Web browser".
  17. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/3a45cbf50d745037c45e4b4b96680722cd3475bd https://github.com/MoscaDotTo/Winapp2/commit/0a6ff0803b353539c44770bd7aaad5238bcb093a
  18. Did you try the following already? https://www.ccleaner.com/docs/ccleaner/advanced-usage/ccleaner-ini-files/how-to-clean-user-data-from-non-standard-mozilla-browsers I guess CustomLocation1 for Brave should be: CustomLocation1=CHROME|C:\Users\<your user name>\AppData\Roaming\brave
  19. Sorry, but it works! Why should I confirm/post a workaround that doesn't work?! I used the workaround on 3 different systems and on all 3 systems the "Active Monitoring" still stays off (for 7 days now, no matter how often I reboot). If you read the many other posts, you will see that the "CCUpdate.exe" is the culprit. But if you have disabled the scheduled task, the "Active Monitoring" isn't able to reenable itself. The scheduled task gets created while installation only. Therefore, if you disable it, it stays disabled.
  20. The first workaround posted by TheOwner works reliable: https://forum.piriform.com/topic/52329-workaround-how-permanently-disable-monitoring-in-5456611/ Easy version: - Open CCleaner and uncheck "Enable Active Monitoring" under Options > Monitoring. - Close CCleaner. - Run the following batch file as administrator. First copy and paste into Notepad and save as e.g. "cc.bat": @ECHO OFF TASKKILL /F /FI "IMAGENAME eq CCleaner*" SCHTASKS /Change /TN "CCleaner Update" /DISABLE REG DELETE "HKCU\Software\Microsoft\Windows\CurrentVersion\Run" /v "CCleaner Monitoring" /f
  21. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/599d3c9c6895b6682a8b37d9dcd97925431b0359
  22. CCleaner settings are still stored under the registry key "Computer\HKEY_CURRENT_USER\Software\Piriform\CCleaner". The registry key "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Piriform\CCleaner" is used for a few installation settings only. If your registry key "Computer\HKEY_CURRENT_USER\Software\Piriform\CCleaner" is empty, then you probably enabled "Save all settings to INI file". Therefore, you have to add the CustomLocation1 to the ccleaner.ini file. And you have to specify the path to the user profile, for example: CustomLocation1=CHROME|C:\Users\<your user name>\AppData\Loca
  23. I can confirm all three bugs also! Workaround for #2: https://forum.piriform.com/topic/52280-unable-disable-monitoring-in-5456611/?tab=comments#comment-297838. @Piriform: I'm really disappointed about the poor in-house testing and the extremely slow bug fixing. Please stop adding new and useless features and concentrate on bug fixing! And please release a bug free version as soon as possible, not in 4 weeks or later. Other developers are fixing bugs within hours, your developers need many weeks or months! Why? And keep in mind that your customers of the non-free versions paid
×
×
  • Create New...