Jump to content
Piriform Community Forums


  • Content count

  • Joined

  • Last visited

Everything posted by APMichael

  1. Winapp2.ini additions

    Please change the following entry, because RegKey2 and 3 are included in winapp.ini of CCleaner now: I think you can remove the following entry, because RegKey and FileKey are included in winapp.ini of CCleaner (for Office 2003, 2007 and 2010): Thanks! I'm not sure if all winapp2.ini users will agree, but following entries could possibly be changed or removed. Comments are welcome. Remove - FileKey included in winsys.ini [Windows Log Files]: Remove - FileKey included in winsys.ini : Change - FileKey2 included in winsys.ini [Windows Log Files]: Remove - FileKey included in winsys.ini [Windows Log Files]: Change - FileKey1 included in winsys.ini [Other Explorer MRUs]: Change - FileKey2 included in winsys.ini [Windows Log Files]:
  2. Thanks for the new version!
  3. Winapp2.ini additions

    Good to know, thanks. I thought CC64 checks and deletes both paths (with and without "Wow6432Node"). With this new knowledge we should check the other winapp2.ini entries which include "RegKey".
  4. Winapp2.ini additions

    I thought the CCleaner64.exe knows where to look for a registry entry on a 64-bit system?! Does it only work with "Detect" entries? Do we have to change most of the "RegKey" entries now?
  5. Thank you for the updated version. Another try: Could a moderator pin this useful thread, please? Thanks!
  6. Winapp2.ini additions

    I think you mean "Please do not remove FileKey2 from this entry", right?
  7. Thank you very much for your fast reply. Yes, I just want to remove all my comments before I trim the winapp2.ini. I'm happy with the command line command, so you do not have to add it to your official Trim.bat version. Thanks again!
  8. Is it possible to include a function which sorts all comment lines out (they start with a semicolon ";")? Reason: I want to comment some of the entries in the complete version of winapp2.ini, but those comments shouldn't make it into the trimmed version.
  9. Winapp2.ini additions

    Thank you very much for checking this. Now the entry is perfect.
  10. Winapp2.ini additions

    I would prefer for the entry [MS Office Help Cache*] this Detect line: Detect=HKCU\Software\Microsoft\Office\14.0\Common\HelpViewer This one is 100% safe. Or maybe this: Detect=HKCU\Software\Microsoft\Office\14.0 Because older versions of MS Office doesn't have the new HelpViewer.
  11. Winapp2.ini additions

    I'm not sure, but I think if you have more than one Detect line you have to use Detect1 and Detect2.
  12. Winapp2.ini additions

    Changed all my entries from DetectFile to Detect. Here are the new Detect lines:
  13. Winapp2.ini additions

    Following entries don't get detected using HKCU. Can you change them to HKLM, please? [ASP.NET*] LangSecRef=3025 Detect=HKCU\Software\MicroSoft\ASP.NET Default=False FileKey1=%WinDir%\Microsoft.net\Framework\*\Temporary ASP.NET Files|*.*|RECURSE FileKey2=%WinDir%\Microsoft.net\Framework64\*\Temporary ASP.NET Files|*.*|RECURSE [FileZilla Temps*] LangSecRef=3022 Detect=HKCU\Software\FileZilla Client Default=False FileKey1=%ProgramFiles%\FileZilla FTP Client|*.tmp
  14. Winapp2.ini additions

    I think the entry "[Windows HOSTs Backup*]" is not necessary, because it is included already: [spybot Search and Destroy Hosts Backups*] LangSecRef=3024 DetectFile=%ProgramFiles%\Spybot - Search & Destroy Default=False FileKey1=%WinDir%\System32\drivers\etc|hosts.*.backup I don't know any other program that makes those backup files ("hosts.yyyymmdd-nnnnnn.backup").
  15. Winapp2.ini additions

    Right, that's why the entry doesn't remove the folders and deletes the setup files only. If you remove the folders also, there will appear an error message or a repair installation (e.g. QuickTime).
  16. Winapp2.ini additions

    Thanks for testing! Or maybe this detection line? DetectFile=%LocalAppData%
  17. Winapp2.ini additions

    I could test this entry on a friends PC with Windows 7 (x64) and latest iTunes 10.5.3 (x64). We used CC with the entry and started iTunes again: Absolutely nothing happened, no error message or repair-installer appeared and no re-download of the installer started. I think the entry is safe.
  18. Winapp2.ini additions

    I would prefer the long names - just for better matching with the name of the built-in entry. Here are two more entries without an asterisk. Found thanks to the latest Trim_x.bat from Alan_B. We should change the LangSecRef of the following entry: Thanks!
  19. Thanks for the two patch lines. I changed the code to this... <%1 ( for /L %%b in (!LO!,1,!HI!) do ( set "LN=" & set /p "LN=" SET "HEAD=!LN!" & SET "TAIL=" & IF "!HEAD:~-1!"==" " SET /A SPC+=1 & CALL :DO_TAIL %%b if "!LN:~0,1!"=="[" SET /A OP+=1 & IF "!HEAD:~-2!" NEQ "*]" SET "HEAD=!HEAD:~0,-1!**]" ECHO(!HEAD! ) )> %2 ...and everything works fine. All the entries without an asterisk were found and fixed. Now this is really the ultimate tool for a perfect trimmed winapp2.ini! Could a moderator pin this useful thread please?
  20. Great, trim_9.bat works flawless with #_Exclude.txt. Now I have a perfect matching winapp2.ini with just a double click. Thank you very much. I have a suggestion for an additional "bad" entry check: Can you check if all entries of the original winapp2.ini have a trailing asterisk (*) in their names? Because without the asterisk the entry is ignored by trim.bat.
  21. Winapp2.ini additions

    Found a typo that causes a problem with trim.bat. The name of the following entry has no trailing asterisk (*). Can you rename these 2 entries, please?
  22. Winapp2.ini additions

    IMHO it is worth. Before I make a new disk image I'd like to have a clean system (without those 6 backup files per user account).
  23. Winapp2.ini additions

    Thanks for the update! Missed entry: New entries: And could a user of iTunes test the following entry, please? If iTunes doesn't want to download its installer again, we can add this entry to the winapp2.ini also.
  24. Winapp2.ini additions

    I can confirm this, now. Today I get a pop-up window with the "Customer Experience Improvement Program" and those files were generated. This is the modified entry:
  25. Winapp2.ini additions

    No, for this case "Malwarebytes' Anti-Malware" is correct, because the built-in entry of CC is written exactly like this. The program files folder is labeled "Malwarebytes' Anti-Malware" also. Edit: Big sorry, you are right! CCleaners entry is written "Malwarebytes Anti Malware" (also no hyphen "-"). Shame on me. And thanks for your good eyes. Ok, then the entries should be renamed from I will correct those typos in my post above.