APMichael

Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/3a45cbf50d745037c45e4b4b96680722cd3475bd https://github.com/MoscaDotTo/Winapp2/commit/0a6ff0803b353539c44770bd7aaad5238bcb093a

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

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.

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

Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/599d3c9c6895b6682a8b37d9dcd97925431b0359

Great! I'm glad I was able to help.

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\Local\Google\Chrome Beta\User Data\Default (Quotation marks are not necessary.)

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 for the now broken functions and that there is a warranty for software in the EU.

You could try the following options: https://www.thewindowsclub.com/winsxs-folder-cleanup-windows-8-1.

Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/e22e97e681edc140c21d265e7ffc2140ab7c3cbb https://github.com/MoscaDotTo/Winapp2/commit/40e7b8ff9985d75aa9aaf0f756bb7aa6cffb46b9

Thanks for the modified entry. For the FileKey3 you can use the variable %Documents%: [Syncios Cell Phone Backup & Manage *] LangSecRef=3024 Detect1=HKCU\Software\Syncios Detect2=HKCU\Software\Syncios Data Transfer Default=False FileKey1=%AppData%\Syncios|android.log;log.txt FileKey2=%AppData%\Syncios Data Transfer|*.log FileKey3=%Documents%\Syncios Data Transfer|preference_conf.ini.old.bak

JFYI: I can confirm this bug, too! (Windows 10 Pro 1803 64-bit, only Windows Defender) More threads:

@javagate: I think he answered your question already. It seems that a Windows update causes the issue. But it's strange that previous versions of CCleaner are still working...

Thanks for the revised entry. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/ea1dc7b355bfae90ce19ce463c3c101beaea6ebf https://github.com/MoscaDotTo/Winapp2/commit/04caa3b62cfc2ba273e2bd2b61e5d1cd5eae0dd2

Great! I'm glad I was able to help.

I'm not sure if CCleaner is responsible for it, but the following should help: Open a "Command Line" with Administrator rights and enter: ATTRIB "C:\Program Files (x86)" +R

I can confirm the bugs! 1. Free 2. No, just Windows Defender 3. No 4. Yes, Windows 10 Pro 1803 64-bit I can confirm that also.

Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/e2db8b12e6ea333145381b10a616d18710df9c91 https://github.com/MoscaDotTo/Winapp2/commit/8bc1717672f904cddfbeaec0d00f36554f0db372

Thank you for the info. I found out that it depends on the installation type. On the first setup screen you can click on "Advanced" and choose the "Installation type": "Install per user" (default setting) uses "%LocalAppData%\Vivaldi\Application" and "Install for all users" uses "%ProgramFiles%\Vivaldi\Application". Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/f26f273c079d3273935f80d8a0deed18a39cb3e1

That's correct, because GitHub uses the Markdown format (.md not .txt). Workaround: You can copy and paste the readme text, instead of downloading the .md file. Thanks! Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/ecc4968946fb8b4a796cf55e2c15a8ab6c340203 Winapp3.ini update: https://github.com/MoscaDotTo/Winapp2/commit/0ce47e9475825095ffb481eb001deaa440e35dbc

Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/6e94b5b89525af861a809de23bc69ac6a3f0df58 https://github.com/MoscaDotTo/Winapp2/commit/503652f3057ccb4e72b92db89b3448132d3c64b4

This registry key prevents that Avast will be offered again (with the next update). https://forum.piriform.com/topic/51681-avast-hidden-install/?tab=comments#comment-295038

Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/67c012bc3c71e07f9d16b86e463b0868475939eb

I can confirm this behavior. It seems that the TRIM function has a little bug. I think Winapp2.ini will fix this soon. No need to worry. Wildcards are working flawless with CCleaner.

Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/753a5f3ec9a112006eba7a7ca83d6c6e4e4e2a2e https://github.com/MoscaDotTo/Winapp2/commit/208af4e067d8eb25321008c6ab8b830dfd038d6b https://github.com/MoscaDotTo/Winapp2/commit/cad0fd293eecbfd36414ef164f8ed7019aef5eed