siliconman01

When the new update, TRIM no longer works on Windows 10x64 Pro. I get the following.

Suggested wording changes for consistency

TRIM worked properly except for the count discrepancy (see attached pic) CCINIDEBUG worked properly WINAPPDEBUG worked properly except for the count discrepancy with TRIM DIFF worked properly. Great progress!!! Update: Examining CCleaner.ini file, it looks as though the count issue is in Winappdebug.exe. This module looks like it is counting all the lines in ccleaner.ini insteard of just the (App) lines.

ISSUE 1 with ccinidebug: In running the new ccinidebug, it falsely displays that every entry in the ccleaner.ini is a stale entry and will be pruned. If I continue to the second step to let it prune and organize ccleaner.ini, it does not actually prune these entries.

I installed the new winapp2ool.exe and performed a TRIM. The new TRIM removed 7 cleaning modules that should not have been removed. In examining the ones falsely trimmed (see attached file), the "Detect" checks are all located in the HKLM\Software\WOW6432Node hive area of the registry. So it looks like the new TRIM is not testing this area or is testing it incorrectly. TrimmedIncorrectly.txt

The new winapp2ool.exe no longer crashes when using DIFF. Yes, it does appear to be improperly trimming. In addition it does not alphabetize its final selection. The new version of Trim is still showing 5 less than the original TRIM.BAT. However, the DIFF run shows a lot of adds and removes that do not look correct. TRIM does not seem to like it if the cleaning module has no DETECT or DETECTFILE in the code. It removes these modules

ISSUE 3: Winappdebug failed to detect the missing backslash in the following ExcludeKey ExcludeKey1=FILE|%SystemDrive%\TomsCommonData\Rainmeter\Skins\Gadgets\@Resources\Language|Weather_EN-US.inc I ran this tool and it did not resolve the crash issue. Yes, I am including the .ini extension Yes, I have run the TRIM module. It is trimming 5 more cleaning items than the original TRIM.BAT. That is why I am wanting to get the DIFF module working. Yes, it still crashes...with and without "Run as Administrator"

My system is Windows 10x64 Professional Build 16299.192 V1709. I am running Winapp2ool.exe as "Run as Administrator" ISSUE 1: When I run the DIFF tool, it crashes after I have entered the 2 names of the Winapp2.ini files I want to compare. Below are the two errors via the Event Viewer ISSUE 2: Even though I run the tool as "Run as Administrator", it trims 5 more items than the original Trim.bat tool. I can't tell which ones are being trimmed because the DIFF tool is crashing.

Won't this leave a lot of empty folders on user's drives ? For example in [AVG *] FileKey4=%CommonAppData%\Avg\AV\SetupBackup|*.*|REMOVESELF FileKey9=%LocalAppData%\AvgSetupLog|*.*|REMOVESELF FileKey14=%WinDir%\System32\config\systemprofile\AppData\Local\AvgSetupLog|*.*|REMOVESELF FileKey17=%WinDir%\SysWOW64\config\systemprofile\AppData\Local\AvgSetupLog|*.*|REMOVESELF

Thanks for the fix.

[Windows Shellbags *] is causing another annoying issue when using Search within File Explorer. It causes the search results to be defaulted back to Content view instead of the user selected view such as Detailed View. Reference the link below which describes/resolves the problem of the selected user view within the Search of File Explorer. https://www.tenforums.com/general-support/60109-how-change-default-folder-view-search-results.html Once a user sets the desired view for Search in File Explorer as per the solution in the link above (and it does work), [Windows Shellbags *] wipes out the fix and reverts File Explorer back to the default Search view which is Content. The two keys below are causing the problem. RegKey1=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\BagMRU RegKey2=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags Removing these two keys from [Windows Shellbags *] is the only "fix" that I can make work; however, maybe someone else can feedback a more desirable fix.

I suspect there are a few entries in Winapp.ini that are not classified properly.

CCinidebug.exe creates/leaves multiple blank lines in file CCleaner.ini.

I recommend that the changes to move such anti-virus programs as Norton, Avast, AVG to 3021 be reversed back to 3024. [Avast *] [AVG *] [Avira AntiVir Desktop *] [Bitdefender *] [Kaspersky *] [McAfee *] [Norton *]

I think this is a bug and I have reported it in the Bug section of CCleaner. In winapp.ini, other av programs such as Avast, AVG, Bitdefender, Malwarebytes, are in 3024

Should not anti-malware/anti-virus programs such as McAfee be placed in Utilities (3024) and not in Applications (3021) [McAfee AntiVirus] ID=2242 LangSecRef=3021 DetectFile=%CommonAppData%\McAfee\MCLOGS Default=True FileKey1=%CommonAppData%\McAfee\MCLOGS|*.log|RECURSE

If I may ask, where does it show that CCleaner uses LangSecRef 3021 for internet security programs ?

Modified entries: [Intel iCLS Client *] and [Intel Storage Counters *] Changed LangSecRef=3024 [Intel iCLS Client *] LangSecRef=3024 DetectFile=%CommonAppData%\Intel\iCLS Client Default=False FileKey1=%CommonAppData%\Intel\iCLS Client|*.log FileKey2=%LocalAppData%\VirtualStore\ProgramData\Intel\iCLS Client|*.log [Intel Storage Counters *] LangSecRef=3024 DetectFile=%WinDir%\Inf\Intel Storage Counters Default=False FileKey1=%WinDir%\Inf\Intel Storage Counters|*.tmp|RECURSE

Modified entry: [Realtek Logs *] Changed LangSecRef=3024 [Realtek Logs *] LangSecRef=3024 Detect=HKLM\Software\Realtek Default=False FileKey1=%LocalAppData%\VirtualStore\Program Files*\Realtek*|*.log;*.txt|RECURSE FileKey2=%ProgramFiles%\Realtek*|*.*log;*.txt|RECURSE FileKey3=%SystemDrive%|RHDSetup.log ExcludeKey1=FILE|%ProgramFiles%\Realtek\*\|InstCtrl.txt ExcludeKey2=FILE|%ProgramFiles%\Realtek\*\|setupctrl.txt

Modified entries: [Snagit *] and [Snagit 13/18 *] Change LangSecRef=3024 to LangSecRef=3021 [Snagit *] LangSecRef=3021 Detect=HKCU\Software\TechSmith\Snagit Default=False Warning=This will delete the backups of the captures. FileKey1=%Documents%|SnagitDebug.log FileKey2=%LocalAppData%\TechSmith\Logs|*.log FileKey3=%LocalAppData%\TechSmith\Snagit\CrashDumps|*.* FileKey4=%LocalAppData%\TechSmith\Snagit\DataStore|*.SNAG;*.SNAGundo;*.MP4 FileKey5=%LocalAppData%\TechSmith\Snagit\TrackerbirdFiles|*.log RegKey1=HKCU\Software\TechSmith\Snagit\9|StampCustomFolder RegKey2=HKCU\Software\TechSmith\Snagit\10|StampCustomFolder RegKey3=HKCU\Software\TechSmith\Snagit\11|CaptureCount RegKey4=HKCU\Software\TechSmith\Snagit\11|CaptureOpenCount RegKey5=HKCU\Software\TechSmith\Snagit\12|CaptureCount RegKey6=HKCU\Software\TechSmith\Snagit\12|CaptureOpenCount RegKey7=HKCU\Software\TechSmith\Snagit\13|CaptureCount RegKey8=HKCU\Software\TechSmith\Snagit\13|CaptureOpenCount RegKey9=HKCU\Software\TechSmith\Snagit\18|CaptureCount RegKey10=HKCU\Software\TechSmith\Snagit\18|CaptureOpenCount RegKey11=HKCU\Software\TechSmith\Snagit\Stamps|StampCustomFolder [Snagit 13/18 *] LangSecRef=3021 Detect1=HKCU\Software\TechSmith\Snagit\13 Detect2=HKCU\Software\TechSmith\Snagit\18 Default=False FileKey1=%CommonAppData%\TechSmith\Uploader|*.log FileKey2=%LocalAppData%\TechSmith\Snagit|Tray.bin FileKey3=%LocalAppData%\TechSmith\Snagit\DataStore\AppIcons|*.ico FileKey4=%LocalAppData%\TechSmith\Snagit\DataStore\WebSiteIcons|*.ico FileKey5=%LocalAppData%\TechSmith\Snagit\Thumbnails|*.* RegKey1=HKCU\Software\TechSmith\Snagit\13\Recent Captures RegKey2=HKCU\Software\TechSmith\Snagit\13\SnagitEditor\Recent File List RegKey3=HKCU\Software\TechSmith\Snagit\18\Recent Captures RegKey4=HKCU\Software\TechSmith\Snagit\18\SnagitEditor\Recent File List

Application software vs Utility software. https://www.difference.wiki/application-software-vs-utility-programs/ The above article defines that we are wrong in calling anti-malware software "Applications".

Post removed

Modified entry: [SetRegistryKey Leftovers *] Change name from [setRegistryKey Leftovers *] to [SetRegistryKey Leftovers *] (capital S)

Yep, you did initially submit it on 25-July-2013 so it's been in Winapp2.ini for 4.5 years. Anyone complained about it destroying their system as of yet? I yield on this point to whatever y'all decide.

The explanation between Lastgood.tmp and System Restore at the link below implies that using System Restore is better. https://social.technet.microsoft.com/Forums/windows/en-US/0d818ddf-6de9-4931-8a55-a8b4792c8863/the-difference-between-system-restore-and-last-good-known-configuration?forum=w8itprogeneral