Jump to content
CCleaner Community Forums

APMichael

Experienced Members
  • Content Count

    645
  • Joined

  • Last visited

Everything posted by APMichael

  1. Thanks for fixing this in version 5.03!
  2. Thanks for the update! Missed post: Doubled FileKey1:
  3. Thanks for the update! Modified: Typo. Modified: I think DetectFile should be: Space before asterisk: Remove: Already inside [internet Explorer 10/11] (FileKey7).
  4. Sadly not fixed in the new CC version 5.02.
  5. @CSGalloway: Did you see our posts?! Please read post #4767, #4768 and #4770.
  6. Is this really safe? Deleting the "OPA11.BAK" file usually de-activates Office (OPA = Office Product Activation). Some FileKeys of your other entries are not correct. Please use the variables only (e.g. %CommonAppData% instead of C:\ProgramData, %ProgramFiles% instead of C:\Program Files). Check the "How to make your own Winapp2.ini entry!" spoiler on page 1 of this thread.
  7. Hello! Please update the [PDFCreator] entry for detection of version 2.0: Detect1=HKCU\Software\PDFCreator Detect2=HKCU\Software\PDFCreator.net Thank you!
  8. You are right! The latest version (QT 7.7.6) does not show this issue anymore. Great! Thanks for the hint.
  9. Please do not modify this entry! If you delete the (latest) folders also, QuickTime (and probably iTunes) recognizes this and wants to start a repair installation. Last post about that issue: #3556. @Winapp2.ini: Please ignore my post. REMOVESELF works flawless now.
  10. Modified entries: They work with new TeamViewer v10.0 now. [TeamViewer Incoming Connections*] LangSecRef=3024 Detect=HKCU\Software\TeamViewer Default=False FileKey1=%ProgramFiles%\TeamViewer|Connections_incoming.txt|RECURSE FileKey2=%LocalAppData%\VirtualStore\Program Files*\TeamViewer|Connections_incoming.txt|RECURSE [TeamViewer Logs*] LangSecRef=3024 Detect=HKCU\Software\TeamViewer Default=False FileKey1=%AppData%\TeamViewer|*.log FileKey2=%ProgramFiles%\TeamViewer|*.log|RECURSE FileKey3=%WinDir%\System32|TeamViewer*_Hooks.log FileKey4=%LocalAppData%\VirtualStore\Program Files*\TeamViewer|*.log|RECURSE [TeamViewer Temporary Files*] LangSecRef=3024 Detect=HKCU\Software\TeamViewer Default=False FileKey1=%ProgramFiles%\TeamViewer|*.tmp|RECURSE FileKey2=%LocalAppData%\VirtualStore\Program Files*\TeamViewer|*.tmp|RECURSE
  11. This will not work, because CC uses the names only (in registry or config file). You cannot use both entries together.
  12. 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.
  13. 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
  14. 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.
  15. 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.
  16. Yes, you have to uncheck both options if you want to disable the new Monitoring feature:
  17. Please see the attached picture. If you do not see both options, please update to the new version 4.18.4844.
  18. 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.
  19. Not that I know of. Only buyers of the "Professional" version get priority support.
  20. 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.
  21. 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?
  22. 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
  23. 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.
×
×
  • Create New...