APMichael

Thank you for the update! Missed post: [Yahoo Messenger Cache*] LangSecRef=3022 DetectFile=%ProgramFiles%\Yahoo!\Messenger\YahooMessenger.exe Detect1=HKCU\Software\Yahoo Detect2=HKCU\Software\Yahoo\pager Default=False FileKey1=%AppData%\Yahoo!\Messenger|*.*|RECURSE FileKey2=%LocalAppData%\VirtualStore\*\Yahoo!\Messenger\Cache|*.*|RECURSE > Suggest removing DetectFile and Detect1 and rename Detect2 to Detect1 < And the file "changes.txt" is not up-to-date.

Missed entry (changes are not in winapp2.ini): [AVG PC TuneUp & TuneUp Utilities Reg Defrag Cleanup*] LangSecRef=3024 Detect1=HKCU\Software\TuneUp\Utilities\10.0 Detect2=HKCU\Software\TuneUp\Utilities\12.0 Detect3=HKCU\Software\TuneUp\Utilities\13.0 Detect4=HKCU\Software\TuneUp\Utilities\14.0 Detect5=HKCU\Software\AVG\AWL\RegistryCleaner Default=False FileKey1=%LocalAppData%\Microsoft\Windows|USRCLASS.DAT_tureg_new.LOG*;USRCLASS.DAT_tureg_old FileKey2=%SystemDrive%\Boot|BCD_tureg_new.LOG*;BCD_tureg_old FileKey3=%SystemDrive%\Documents and Settings\LocalService|NTUSER.DAT_tureg_new.LOG*;NTUSER.DAT_tureg_old FileKey4=%SystemDrive%\Documents and Settings\LocalService.NT*|NTUSER.DAT_tureg_new.LOG*;NTUSER.DAT_tureg_old FileKey5=%SystemDrive%\Documents and Settings\NetworkService|NTUSER.DAT_tureg_new.LOG*;NTUSER.DAT_tureg_old FileKey6=%SystemDrive%\Documents and Settings\NetworkService.NT*|NTUSER.DAT_tureg_new.LOG*;NTUSER.DAT_tureg_old FileKey7=%UserProfile%|NTUSER.DAT_tureg_new.LOG*;NTUSER.DAT_tureg_old FileKey8=%WinDir%\ServiceProfiles\LocalService|NTUSER.DAT_tureg_new.LOG*;NTUSER.DAT_tureg_old FileKey9=%WinDir%\ServiceProfiles\NetworkService|NTUSER.DAT_tureg_new.LOG*;NTUSER.DAT_tureg_old FileKey10=%WinDir%\System32\config|COMPONENTS_tureg_new.LOG*;COMPONENTS_tureg_old;DEFAULT_tureg_new.LOG*;DEFAULT_tureg_old;SAM_tureg_new.LOG*;SAM_tureg_old;SECURITY_tureg_new.LOG*;SECURITY_tureg_old;SOFTWARE_tureg_new.LOG*;SOFTWARE_tureg_old;SYSTEM_tureg_new.LOG*;SYSTEM_tureg_old;DRIVERS_tureg_new.LOG*;DRIVERS_tureg_old FileKey11=%WinDir%\ServiceProfiles\NetworkService\AppData\Local\Microsoft\Windows\|USRCLASS.DAT_tureg_old;USRCLASS.DAT_tureg_new.LOG* FileKey12=%WinDir%\ServiceProfiles\LocalService\AppData\Local\Microsoft\Windows\|USRCLASS.DAT_tureg_old;USRCLASS.DAT_tureg_new.LOG* - Added FileKeys11 and 12

Sounds good to me!

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

As there is still no manual or description for the new Monitoring feature it is difficult to say. Most of the automatic functions need a "Professional" license, so I do not see a benefit for enabling it. But this is just my personal opinion.

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

Please see the attached picture. If you do not see both options, please update to the new version 4.18.4844.

You have to uncheck two options: Enable System Monitoring and Enable Active Monitoring. http://forum.piriform.com/index.php?showtopic=41858&p=253811 But there is also a new version available (4.18.4844). http://forum.piriform.com/index.php?showtopic=41858&p=253778 Edit: hazelnut was faster.

Not that I know of. Only buyers of the "Professional" version get priority support.

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.

Good, the new Monitoring feature is disabled correctly. If you start CCleaner without the command /AUTO does cleaning work flawless or does it hang? Which Windows version you are using?

Ok, you are using the portable version. Please open the "ccleaner.ini" file and check if the following lines are included and the value is respectively zero: Monitoring=0 SystemMonitoring=0

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. Ok, I understand your point. Right, Piriform should publish a manual or detailed description for the new Monitoring feature.

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!

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.

This works fine for me too! And after a reboot monitoring is still disabled. (Tested on 3 PCs.)

Strange, no problem here. I disabled monitoring that way: 1.) Options > Monitoring > uncheck "Enable system monitoring" 2.) Options > Advanced > uncheck "Enable Active Monitoring" Edit: Found the Bug Reporting thread. Strange that it does not work one some systems?!

Thanks for the update! All missed posts are reported already.

About the use of ExcludeKey:

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.

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:

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

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

Thanks for the update! Missed posts: #3889, #3894, #3898

Thanks for the update!