siliconman01

New Entry: [Amazon.com Software Downloads (Logs)*] The logs are created when you purchase and download software from Amazon.com. [Amazon.com Software Downloads (Logs)*] LangSecRef=3024 DetectFile=%Documents%\Amazon Downloader Logs Default=False FileKey1=%Documents%\Amazon Downloader Logs\|*.*|REMOVESELF

New Entry: [Norton Error Repair Tool (Logs)*] This removes logs that are generated by Symantec's security products repair tool SymNRA.exe. This tool generates sizeable logs for submission to Symantec when debugging Norton products. [Norton Error Repair Tool (Logs)*] LangSecRef=3024 DetectFile=%Documents%\Symantec Default=False Warning=This removes Error Logs created by Norton's SymNRA log tool used for reporting bugs. FileKey1=%Documents%\Symantec\ErrLogs|*.zip FileKey2=%SystemDrive%\Symlogs|*.*|REMOVESELF

New Entry: [TuneUp Utilities (CrashDumps)*] [TuneUp Utilities (CrashDumps)*] LangSecRef=3024 Detect=HKCU\Software\TuneUp Default=False Warning=This removes ALL crash/dump files saved by program TuneUp Utilities. FileKey1=%AppData%\TuneUp Software\TuneUp Utilities\CrashDumps|*.*

Modified Entry for [TuneUp Utilities Reg Defrag Cleanup*] to include TuneUp Utilities 2014. Added Detect4

The ExcludeKey1 addition to Windows SCM Logs* still not resolve the basic issue of this code causing Windows Scheduled Tasks to re-run any scheduled task that has the option "Run task as soon as possible after a scheduled start is missed" activated. The logs in the SCM folder are used to control this option. I strongly recommend that Windows SCM Logs* not be re-added to Winapp2.ini.

It is very tempting to remove reserve.tmp; however, I am going to wait until after Windows 8.1 is installed. If the file is still there, I most likely will save it on a flash drive and delete it from Winsys.

There are a few other web pages referencing this file and stating to NOT remove it. I agree with Nergal's recommendation.

2014 Norton Products Released. Changed name on [Norton Internet Security 2012/13/14 Dumps*] [Norton Internet Security 2012/13/14 Dumps*] LangSecRef=3024 DetectFile=%CommonAppData%\Norton\LocalDumps Default=False FileKey1=%CommonAppData%\Norton\LocalDumps|*.dmp

I am assuming that you have Winapp2.ini installed for CCleaner (be sure that you have the latest version of Winapp2.ini installed if you are running Winapp2.ini). On the applications tab, uncheck Windows 7/8 QuickLaunch* Windows QuickLaunch DiagnosedApplications* Windows QuickLaunch ImplicitAppShortcuts*

Below is the exact cleaning code for NVIDIA as it is set up in CCleaner V4.05 [NVIDIA] ID=2357 LangSecRef=3024 Detect=HKCU\Software\NVIDIA Corporation Default=True FileKey1=%SystemDrive%\NVIDIA|*.*|REMOVESELF FileKey2=%SystemDrive%\NV|*.*|REMOVESELF These folders are nothing more than the extracted files from the Nvidia installer. This extraction occurs when users download a nVidia graphics update and then run the installer. The installer extracts the files to the %SystemDrive%\Nvidia (or NV) folder. It then installs the new nVidia files and completes the update. Once the update is completed, the extracted files in %SystemDrive%\Nvidia (or NV) are no longer needed or used. Deleting them has no negative affect on a user's system. If you feel uncomfortable with removing with file, back it up first on a CD or Flash Drive. Then let CCleaner remove the folder. Reboot your computer and you will find that everything still works just fine. I've done this when my computers had Windows XP, then Vista, then Windows 7, and now Windows 8.

Here is the way I've analzyed that format to work.....using Windows 8 as an example DetectOS=6.2 = Show only on Windows 8 DetectOS=|6.2 = Show on Windows 8 and earlier versions of Windows, but not on versions later than Windows 8 DetectOS=6.2| = Show on Windows 8 and later versions of Windows There is no option that states "Show on all versions (earlier and later versions) except Windows 8". So if you want code to show on all versions but the latest version of Windows which is Windows 8, you would set it as DetectOS=|6.1 which says show on Windows 7 and earlier versions but not on Windows 8 or later. There needs to be a format that states "show on all versions but the specified version". For example: DetectOS=|6.2| = could say "Show on all versions earlier than Windows 8, all versions later than Windows 8, but do not show on Windows 8.

http://forum.pirifor...260#entry237883 The post above recommends that [Windows Search Cache*] be removed from Winapp2.ini. Even with DetectOS=|6.2 it is showing up on Windows 8 and also Windows 7. I suggest [Windows Search Cache*] be removed from WinApp2.ini

The Nvidia in CCleaner as well as the "just removed" Nvidia entry in Winapp2.ini below [Nvidia Graphics Driver Installation Files*] LangSecRef=3023 Detect=HKCU\Software\NVIDIA Corporation Default=False FileKey1=%SystemDrive%\Nvidia|*.*|REMOVESELF are the same. This folder is nothing more than the extracted files from the Nvidia installer. This extraction occurs when users download a nVidia graphics update and then run the installer. The installer extracts the files to the %SystemDrive%\Nvidia folder. It then installs the new nVidia files and completes the update. Once the update is completed, the extracted files in %SystemDrive%\Nvidia are no longer needed or used. Deleting them has no negative affect on a user's system. At one time the entry below was included in Winapp2.ini [Nvidia Graphics Driver Installation Files*] LangSecRef=3023 Detect=HKCU\Software\NVIDIA Corporation Default=False Warning=You will not be able to do an uninstall of your drivers without first reinstalling them. FileKey1=%SystemDrive%\Nvidia|*.*|REMOVESELF FileKey2=%ProgramFiles%\NVIDIA Corporation\Installer2|*.*|RECURSE FileKey2 was the entry that was causing problems with removing Nvidia graphics file because it was removing an huge folder named Installer2 which has the uninstaller.exe file in it. FileKey2 was removed a few months back and the warning was removed as well. If users have not updated Winapp2.ini since that error was discovered then they could definitely run into a problem with using CCleaner. I am running 326.80 (which is a beta version of nVidia graphics for my NVIDIA GeForce GTX 650 graphics card) on my Windows 8 x64 Professional systems. And CCleaner V4.05 cleaning has done nothing to negatively impact the nVidia graphics software.

New Entry: jv16 PowerTools 2014 jv16 PowerTools 2014 is in the RC1 phase so I suggest that its cleaning code be added to Winapp2.ini

This also applies to IE 11. Changed name from [internet Explorer 10*] to [internet Explorer 10/11*] [internet Explorer 10/11*] LangSecRef=3022 DetectFile=%LocalAppData%\Microsoft\Windows\WebCache Default=False FileKey1=%LocalAppData%\Microsoft\SmartScreen|*.tmp FileKey2=%LocalAppData%\Microsoft\Vault\*|*.vcrd FileKey3=%LocalAppData%\Microsoft\Windows\AppCache|*.*|RECURSE FileKey4=%LocalAppData%\Microsoft\Windows\WebCache|*.*|RECURSE FileKey5=%LocalAppData%\Microsoft\Windows\WebCache.old|*.*|REMOVESELF FileKey6=%LocalLowAppData%\Microsoft\Windows\AppCache|*.*|RECURSE

Looks like you missed LifeCam at http://forum.piriform.com/index.php?showtopic=32310&st=3220&do=findComment&comment=237487

New addition of App LifeCam [LifeCam*] LangSecRef=3031 Detect=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\Microsoft.LifeCamDashboard_8wekyb3d8bbwe DetectFile=%LocalAppData%\Packages\Microsoft.LifeCamDashboard_8wekyb3d8bbwe Default=False FileKey1=%LocalAppData%\Packages\Microsoft.LifeCamDashboard_*\AC\INetCache|*.*|RECURSE FileKey2=%LocalAppData%\Packages\Microsoft.LifeCamDashboard_*\AC\INetCookies|*.*|RECURSE FileKey3=%LocalAppData%\Packages\Microsoft.LifeCamDashboard_*\AC\INetHistory|*.*|RECURSE FileKey4=%LocalAppData%\Packages\Microsoft.LifeCamDashboard_*\AC\PRICache|*.* FileKey5=%LocalAppData%\Packages\Microsoft.LifeCamDashboard_*\AC\Temp|*.* FileKey6=%LocalAppData%\Packages\Microsoft.LifeCamDashboard_*\TempState|*.*|RECURSE Also a language addition for US English edit on LifeCam [LifeCam (Lng)*] Section=US English Language Detect=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\Microsoft.LifeCamDashboard_8wekyb3d8bbwe DetectFile=%LocalAppData%\Packages\Microsoft.LifeCamDashboard_8wekyb3d8bbwe Warning=This deletes all languages EXCEPT the United States English language. Default=False FileKey1=%ProgramFiles%\Microsoft LifeCam\DriverComponents\de-DE\|*.*|REMOVESELF FileKey2=%ProgramFiles%\Microsoft LifeCam\DriverComponents\el-GR\|*.*|REMOVESELF FileKey3=%ProgramFiles%\Microsoft LifeCam\DriverComponents\es-ES\|*.*|REMOVESELF FileKey4=%ProgramFiles%\Microsoft LifeCam\DriverComponents\fr-FR\|*.*|REMOVESELF FileKey5=%ProgramFiles%\Microsoft LifeCam\DriverComponents\it-IT\|*.*|REMOVESELF FileKey6=%ProgramFiles%\Microsoft LifeCam\DriverComponents\ja-JP\|*.*|REMOVESELF FileKey7=%ProgramFiles%\Microsoft LifeCam\DriverComponents\ko-KR\|*.*|REMOVESELF FileKey8=%ProgramFiles%\Microsoft LifeCam\DriverComponents\pt-BR\|*.*|REMOVESELF FileKey9=%ProgramFiles%\Microsoft LifeCam\DriverComponents\pt-PT\|*.*|REMOVESELF FileKey10=%ProgramFiles%\Microsoft LifeCam\DriverComponents\ru-RU\|*.*|REMOVESELF FileKey11=%ProgramFiles%\Microsoft LifeCam\DriverComponents\zh-CN\|*.*|REMOVESELF FileKey12=%ProgramFiles%\Microsoft LifeCam\DriverComponents\zh-TW\|*.*|REMOVESELF

It is my recommendation that CCleaner be restricted so that only one copy of CCleaner can be in RAM memory running at any point in time. At the present time, multiple copies of CCleaner can be loaded in RAM. IMO, this is a CCleaner bug that should be fixed. On my systems, I have CCleaner /auto pinned to the taskbar. I sometimes accidentally click on the CCleaner icon in the taskbar while CCleaner is already running. This starts a second copy of CCleaner running in RAM. I use Winapp2.ini which makes CCleaner load slower. Therefore the CPU usage of 2 copies of CCleaner loading//running can be as high as 85%.

New App Network Speed Test by Microsoft [Network Speed Test*] LangSecRef=3031 Detect=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\Microsoft.NetworkSpeedTest_8wekyb3d8bbwe DetectFile=%LocalAppData%\Packages\Microsoft.NetworkSpeedTest_8wekyb3d8bbwe Default=False FileKey1=%LocalAppData%\Packages\Microsoft.NetworkSpeedTest_*\AC\INetCache|*.*|RECURSE FileKey2=%LocalAppData%\Packages\Microsoft.NetworkSpeedTest_*\AC\INetCookies|*.*|RECURSE FileKey3=%LocalAppData%\Packages\Microsoft.NetworkSpeedTest_*\AC\INetHistory|*.*|RECURSE FileKey4=%LocalAppData%\Packages\Microsoft.NetworkSpeedTest_*\AC\Microsoft\CLR_v4.0*\UsageLogs|*.*|RECURSE FileKey5=%LocalAppData%\Packages\Microsoft.NetworkSpeedTest_*\AC\PRICache|*.* FileKey6=%LocalAppData%\Packages\Microsoft.NetworkSpeedTest_*\AC\Temp|*.* FileKey7=%LocalAppData%\Packages\Microsoft.NetworkSpeedTest_*\TempState|*.*|RECURSE

If these are added to Winapp2.ini, I suggest the name be "Local System" instead of the abbreviated "LSys" so that users are better able to identify what these are related to. Does Windows have to rebuild these after they are cleared?

I strongly recommend that the entry Windows SCM Logs* be removed from WinApp2.ini because it causes the Event ID 114 failure in the system Task Scheduler as described above. [Windows SCM Logs*] LangSecRef=3025 Detect=HKCU\Software\Microsoft\Windows Default=False FileKey1=%WinDir%\System32\LogFiles\Scm|*.*

I am attempting to track down what WinApp2.ini entry is causing the system Task Scheduler to experience Event ID 114 on scheduled tasks that run via the Task Scheduler. If anyone has any clues or feedback on what entry might be causing this, please "point me in the right direction". Below is a more detailed description of the issue. I use my "Casper" system backup program as the example; however, the problem affects all programs in the Task Scheduler. My systems are Windows 7 and Windows 8. - I have Casper set up in the Task Scheduler to run every Tuesday and Saturday at 3:00 a.m. to copy my primary operating system to a separate bootable backup drive. - In the Task Scheduler on the Settings tab, I have "Run task as soon as possible after a scheduled start is missed" selected. - The Task Scheduler works correctly and runs Casper on Tuesday and Saturday at the prescribed times. - The time/date of the Casper run is properly displayed via the Task Scheduler under "Last Run Time". - The time/date of the next scheduled Casper execution is properly displayed via the Task Scheduler under "Next Run Time" - When I run CCleaner after the above Casper execution, the "Last Run Time" is cleared out and "Never" now shows as the "Last Run Time". - On system reboot, this causes the Task Scheduler to think that Casper did not run when scheduled (Event ID 114). And it then runs Casper as directed via the option "Run task as soon as possible after a scheduled start is missed". I am going through the process of elimination under the Applications tab of CCleaner; however, in the interest of time I am posting this "request for assistance".

New Windows 8 Apps: GasBuddy and Team Crossword [GasBuddy*] Section=Windows 8 Apps DetectFile=%LocalAppData%\Packages\45351D82.GasBuddy-FindCheapGasPrices_932xwky9axss4 Default=False FileKey1=%LocalAppData%\Packages\45351D82.GasBuddy-FindCheapGasPrices_*\AC\INetCache|*.*|RECURSE FileKey2=%LocalAppData%\Packages\45351D82.GasBuddy-FindCheapGasPrices_*\AC\INetCookies|*.*|RECURSE FileKey3=%LocalAppData%\Packages\45351D82.GasBuddy-FindCheapGasPrices_*\AC\INetHistory|*.*|RECURSE FileKey4=%LocalAppData%\Packages\45351D82.GasBuddy-FindCheapGasPrices_*\AC\Temp|*.* FileKey5=%LocalAppData%\Packages\45351D82.GasBuddy-FindCheapGasPrices_*\AC\PRICache|*.* FileKey6=%LocalAppData%\Packages\45351D82.GasBuddy-FindCheapGasPrices_*\AC\Microsoft\CLR_v4.0\UsageLogs|*.*|RECURSE FileKey7=%LocalAppData%\Packages\45351D82.GasBuddy-FindCheapGasPrices_*\TempState|*.*|RECURSE [Team Crossword*] Section=Windows 8 Apps DetectFile=%LocalAppData%\Packages\Microsoft.TeamCrossword_8wekyb3d8bbwe Default=False FileKey1=%LocalAppData%\Packages\Microsoft.TeamCrossword_*\AC\Microsoft\CryptnetUrlCache\Content|*.* FileKey2=%LocalAppData%\Packages\Microsoft.TeamCrossword_*\AC\Microsoft\CryptnetUrlCache\MetaData|*.* FileKey3=%LocalAppData%\Packages\Microsoft.TeamCrossword_*\AC\INetCache|*.*|RECURSE FileKey4=%LocalAppData%\Packages\Microsoft.TeamCrossword_*\AC\INetCookies|*.*|RECURSE FileKey5=%LocalAppData%\Packages\Microsoft.TeamCrossword_*\AC\INetHistory|*.*|RECURSE FileKey6=%LocalAppData%\Packages\Microsoft.TeamCrossword_*\AC\Temp|*.* FileKey7=%LocalAppData%\Packages\Microsoft.TeamCrossword_*\AC\PRICache|*.* FileKey8=%LocalAppData%\Packages\Microsoft.TeamCrossword_*\AC\Microsoft\CLR_v4.0_32\UsageLogs|*.*|RECURSE FileKey9=%LocalAppData%\Packages\Microsoft.TeamCrossword_*\TempState|*.*|RECURSE

This apparently works as well ExcludeKey1=FILE|%ProgramFiles%\ProgramXY\|file.exe

Changing [Nvidia Graphics Driver Installation Files*] from: [Nvidia Graphics Driver Installation Files*] LangSecRef=3023 Detect=HKCU\Software\NVIDIA Corporation Default=False Warning=You will not be able to do an uninstall of your drivers without first reinstalling them. FileKey1=%SystemDrive%\Nvidia|*.*|REMOVESELF FileKey2=%ProgramFiles%\NVIDIA Corporation\Installer2|*.*|RECURSE to [Nvidia Graphics Driver Installation Files*] LangSecRef=3023 Detect=HKCU\Software\NVIDIA Corporation Default=False FileKey1=%SystemDrive%\Nvidia|*.*|REMOVESELF is a solution to the problem that Saad2011 aptly points out. I recommend this change be made. %SystemDrive%\Nvidia is an extraction folder that is used by the Nvidia installer when performing an update. After the update is completed, this folder is no longer needed or used.