Jump to content

APMichael

Experienced Members
  • Posts

    984
  • Joined

  • Last visited

Posts posted by APMichael

  1. 6 hours ago, noahphense said:

    That doesn't work.  Still comes back after a double reboot...

    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.

  2. 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
  3. 7 hours ago, SteveW said:

    ...The registry setting is now in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Piriform\CCleaner...

    The supposed fix, adding a string value (in the correct registry hive) of "CustomLocation1" with data "CHROME|"C:\Program Files (x86)\Google\Chrome Beta\Application"" doesn't work.

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

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

  5. 3 hours ago, siliconman01 said:

    Modified entry:  [Syncios Cell Phone Backup & Manage *]

    Added FileKey3 ...

    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

     

  6. @javagate: I think he answered your question already. It seems that a Windows update causes the issue.

    17 hours ago, Stephen Piriform said:

    In this case, there is another cause which is an update to Windows 10 (build 1803) that is breaking this functionality. We are working on this issue currently and anticipate a fix for the v5.46 release (release after the next one).

    But it's strange that previous versions of CCleaner are still working...

  7. 23 hours ago, PICPro said:

    After installing the current 64 bit Vivaldi in Windows 7, I noticed that an entry was missing in [SetupMetrics *].  I'm suggesting to add FileKey21 as this is where the files have been going:...

    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

  8. On 15.6.2018 at 03:12, PICPro said:

    For the new README.md file with the Winapp2 instructions, it appears that most of the backslashes have been "escaped" like in a c string.  So most of the backslashes in the path names are doubled up, also some of the asterisks are escaped, showing up as *\ instead of just *

    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.

    On 15.6.2018 at 03:12, PICPro said:

    For the LangSecRef list, here are a few more:
    LangSecRef=3029 = Google Chrome
    LangSecRef=3030 = Thunderbird
    LangSecRef=3031 = Windows Store

    Thanks!

     

    Winapp2.ini update:
    https://github.com/MoscaDotTo/Winapp2/commit/ecc4968946fb8b4a796cf55e2c15a8ab6c340203

    Winapp3.ini update:
    https://github.com/MoscaDotTo/Winapp2/commit/0ce47e9475825095ffb481eb001deaa440e35dbc

  9. On 1.6.2018 at 05:49, Joe737 said:

    BTW, even if you don't install Avast an Avast Registry Key will be dropped.  I attached a screenshot of it.  If you are not familiar with the Registry just leave it.  Otherwise, you can delete the key if you want to.

    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

  10. 10 hours ago, siliconman01 said:

    For some reason, the TRIM function of winapp2ool.exe (V0.8.0.0) does not recognize the DetectFile shown below for Chrome and it trims these all out.
    DetectFile2=%LocalAppData%\Google\Chrome*

    I can confirm this behavior. It seems that the TRIM function has a little bug. I think Winapp2.ini will fix this soon.

    10 hours ago, siliconman01 said:

    I wonder if CCleaner is recognizing %LocalAppData%\Google\Chrome*  where it is used in FileKey and ExcludeKey. ??? 

    No need to worry. Wildcards are working flawless with CCleaner.

    DetectFile_Chrome_Wildcard.jpg

×
×
  • Create New...

Important Information

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