Jump to content
CCleaner Community Forums

APMichael

Experienced Members
  • Content count

    605
  • Joined

  • Last visited

Posts posted by APMichael


  1.  

    Great! Thank you for the hint.

     

    I believe the following apply's to the Professional version only and should be removed from the Docs for the free version.

     

    I am not sure. Maybe they want to clarify what will be cleaned if you confirm the balloon notification.


  2. Yes, you have to uncheck both options if you want to disable the new Monitoring feature:

     

    Active Monitoring can now be disabled by:
    1. Open CCleaner, then click Options > Monitoring
    2. Disable System Monitoring by unticking the box next to "Enable System Monitoring"
    3. Disable Active Monitoring by unticking the box next to "Enable Active Monitoring", and click Yes when the confirmation box appears


  3. I checked the portable version on my system (Windows 7, 64-bit). The command /AUTO works flawless even if the Monitoring feature is enabled. It seems that the Monitoring options are not relevant for the command /AUTO.

     

    I am sorry; I do not have another idea why it does not work correctly on your system. :(

     

    I thought it may be Windows 8 related, but you are using Vista. So only the coder can help now.


  4. Both versions get stuck in the Task Bar when /AUTO command is used to automatically start then clean then close CCleaner. This has not been fixed.

     

    I cannot confirm that! Also the command /AUTO works flawless (on 3 different PCs). There are no Windows Startup entries of CCleaner.

    I am sorry; I do not know why it does not work on your system. Maybe there is a conflict with a security tool?

    And I agree with you that Monitoring should be disabled by default. It causes too much trouble.

     

    thanks APMichael but until a final released version is fully tested and ready for the public, .... I don't like enabling new features, when I have no idea what it does, and why I would want it.

     

    Ok, I understand your point. Right, Piriform should publish a manual or detailed description for the new Monitoring feature.


  5. Enable Active Monitoring was not checked on my 4.18 install by default, only the Enable System Monitoring.  I turned it off, and it would still not go away, so not sure what you are talking about.

    It only seems that "Enable Active Monitoring" is not turned on.

     

    After the update/installation of version 4.18.4842 the Options > Advanced menu looks like attached image 42_01.jpg.

    The option "Enable Active Monitoring" is locked and greyed out.

    Now go to Options > Monitoring and uncheck the option "Enable system monitoring" (image 42_02.jpg).

    After that go back to Options > Advanced and you will see that the option "Enable Active Monitoring" becomes accessible (image 42_03.jpg).

    Uncheck it and click Yes when the confirmation box appears. Done!

     

    The new version 4.18.4844 changed the layout of the menus. Options > Monitoring shows both options now (image 44_01.jpg).

    Uncheck the option "Enable system monitoring". After that the option "Enable Active Monitoring" becomes accessible (image 44_02.jpg).

    Uncheck it and click Yes when the confirmation box appears. Done!

    post-58475-0-17848100-1411759525_thumb.jpg

    post-58475-0-21627300-1411759533_thumb.jpg

    post-58475-0-40671100-1411759538_thumb.jpg

    post-58475-0-43655500-1411759545_thumb.jpg

    post-58475-0-71328200-1411759554_thumb.jpg


  6. Go to ccleaner.ini in the ccleaner folder and change the Monitoring line from 1 to 0.

     

    You are right, changing the Enable System Monitoring will not stop the monitoring.

    Not every installation uses the ccleaner.ini. Just uncheck Enable System Monitoring and Enable Active Monitoring and you are fine. Both options have to be disabled.


  7. About the use of ExcludeKey:

     

    I recognized that some of the ExcludeKeys don't work. Conclusion: If you exclude a single file only (without a wildcard *), you have to use a backslash instead of the pipe symbol.

     

    Here is an example:

    ExcludeKey1=FILE|%ProgramFiles%\ProgramXY|file.exe (does not work)

    ExcludeKey1=FILE|%ProgramFiles%\ProgramXY\file.exe (does work)

     

    The pipe symbol is necessary if you use a wildcard (*) or a separator ( ;):

    ExcludeKey1=FILE|%ProgramFiles%\ProgramXY|*.exe;*.log

     

    This apparently works as well

     

    ExcludeKey1=FILE|%ProgramFiles%\ProgramXY\|file.exe


  8. Ok, I understand, unfortunately I don't have any experience with more recent games. I use the highest UAC level ("Always notify") on all my computers and only one program uses the VirtualStore folder. It is an old XP program which stores the config file in the %ProgramFiles% path.


  9. Thank you very very much for this huge update!
     
    I don't want to be a grinch, but I think there was a big misunderstanding about the VirtualStore folder. Sorry! :(

     

    Only Pre-Windows-Vista programs or programs which ignores the Windows guidelines for Vista (and higher) uses the VirtualStore folder. The majority of programs works correctly with UAC and will never need the VirtualStore folder, even if they write to %ProgramFiles%. (On my computer only one very old XP program needs the VirtualStore folder.)

    Nergal wrote this already:

    No because VS is only made by programs not fixed for vista/7/8 and only some of them (the ones that try to store in program folder but don't run with UAC elevation and the ones (I think) set to run as XP or lower in compatibility mode)


  10. Shouldn't FileKey2 be?

     

    [Avidemux log*]
    LangSecRef=3023
    Detect1=HKLM\Software\Avidemux 2.4
    Detect2=HKLM\Software\Avidemux 2.5
    Detect3=HKLM\Software\Avidemux 2.6
    Default=False
    FileKey1=%AppData%\avidemux|admlog.txt
    FileKey2=%LocalAppData%\VirtualStore\Program Files (x86)\Avidemux*|admlog.txt


  11. Thanks for the huge update! :)

     

    Missing dots:

     

    [DivX Logs*]
    LangSecRef=3023
    Detect=HKCU\Software\DivX
    Default=False
    FileKey1=%CommonAppData%\DivX|*.log|RECURSE

     

    [Lexware Logs*]
    LangSecRef=3021
    DetectFile=%LocalAppData%\Lexware
    Default=False
    FileKey1=%CommonAppData%\Lexware\logs|*.*|REMOVESELF
    FileKey2=%CommonAppData%\Lexware\elster\Log|*.*|REMOVESELF
    FileKey3=%CommonAppData%\Lexware|*.log;*.logx|RECURSE
    FileKey4=%LocalAppData%\Lexware|*.log;*.logx|RECURSE
    FileKey5=%SystemDrive%|LxDasi.Log
    FileKey6=%ProgramFiles%\Common Files\Lexware|*.log|RECURSE

     

    Modified FileKey2 - should work with version 1 and 2 now:

     

    [MalwareBytes Anti Malware More*]
    LangSecRef=3024
    Detect1=HKCU\Software\Malwarebytes' Anti-Malware
    Detect2=HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths\mbam.exe
    Default=False
    FileKey1=%AppData%\Malwarebytes\Malwarebytes' Anti-Malware\Logs|*.*
    FileKey2=%CommonAppData%\Malwarebytes\Malwarebytes*Anti-Malware\Logs|*.*
    FileKey3=%CommonAppData%\Malwarebytes\Malwarebytes' Anti-Malware|mbam-setup.exe


  12. Thanks for the update!

    - FileKey4 is not necessary because FileKey3 deletes aum.log also:

    [Adobe Updater Logs*]
    LangSecRef=3021
    Detect=HKCU\Software\Adobe
    Default=False
    FileKey1=%AppData%\Adobe\LogTransport*\Logs|ulog_*.tmp
    FileKey2=%LocalAppData%\Adobe\AAMUpdater|*.Log|RECURSE
    FileKey3=%LocalAppData%\Adobe\Updater*|*.log|RECURSE
    FileKey4=%LocalAppData%\Adobe\Updater5|aum.log

     
    - The entry [Windows Log Files More*] exists twice. Please delete the first one:

    [Windows Log Files More*]
    LangSecRef=3025
    DetectFile=%windir%\Panther
    Default=False
    FileKey1=%windir%\PANTHER|

     
    - Above the entry [sKSE*] are blank lines.

×