Winapp2.ini

Please review the latest revision I posted above and see if it addresses the problem you are having

https://github.com/MoscaDotTo/Winapp2/pull/138/commits/d2a330ad5c6ef14eda229e4211916080501d0d66 I did not join the internet explorer entries because one refers to the Metro app while the other refers to the desktop one. I included the PRI cache into the Subsystems entry based on this page: https://msdn.microsoft.com/en-us/library/windows/apps/jj552947.aspx The Windows AppCache entry is part of Internet Explorer and some Metro apps based on this page: https://msdn.microsoft.com/en-us/library/hh673545(v=vs.85).aspx and the path is actually covered by an existing filekey in the Internet Explorer More * entry: FileKey6=%LocalAppData%\Microsoft\Windows\*Cache*|*.*|RECURSE

There actually already is an Internet Explorer entry in winapp2.ini [Internet Explorer *] LangSecRef=3031 Detect=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\windows_ie_ac_001 DetectFile=%LocalAppData%\Packages\windows_ie_ac_001 Default=False FileKey1=%LocalAppData%\Packages\windows_ie_ac_*\AC\AppCache|*.*|RECURSE FileKey2=%LocalAppData%\Packages\windows_ie_ac_*\AC\INet*|*.*|RECURSE FileKey3=%LocalAppData%\Packages\windows_ie_ac_*\AC\Microsoft\CLR_v4.0\UsageLogs|*.*|RECURSE FileKey4=%LocalAppData%\Packages\windows_ie_ac_*\AC\Microsoft\CryptnetUrlCache\*|*.* FileKey5=%LocalAppData%\Packages\windows_ie_ac_*\AC\Microsoft\Internet Explorer\DOMStore|*.*|RECURSE FileKey6=%LocalAppData%\Packages\windows_ie_ac_*\AC\PRICache|*.* FileKey7=%LocalAppData%\Packages\windows_ie_ac_*\AC\Temp|*.* FileKey8=%LocalAppData%\Packages\windows_ie_ac_*\LocalState\Cache|*.*|RECURSE FileKey9=%LocalAppData%\Packages\windows_ie_ac_*\LocalState\navigationHistory|*.*|RECURSE FileKey10=%LocalAppData%\Packages\windows_ie_ac_*\TempState|*.*|RECURSE RegKey1=HKCR\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Storage\windows_ie_ac_001\Internet Explorer\DOMStorage [Internet Explorer More *] LangSecRef=3022 Detect=HKCU\Software\Microsoft\Internet Explorer Default=False FileKey1=%AppData%\Microsoft\Internet Explorer|brndlog.bak;brndlog.txt FileKey2=%AppData%\Microsoft\Internet Explorer\UserData|*.*|RECURSE FileKey3=%LocalAppData%\Microsoft\Internet Explorer|frameiconcache.dat;tabiconcache.dat;brndlog.txt;brndlog.bak FileKey4=%LocalAppData%\Microsoft\Internet Explorer\Recovery\Last Active|*.*|RECURSE FileKey5=%LocalAppData%\Microsoft\SmartScreen|*.tmp FileKey6=%LocalAppData%\Microsoft\Windows\*Cache*|*.*|RECURSE FileKey7=%LocalLowAppData%\Microsoft\Internet Explorer\iconcache|*.*|RECURSE FileKey8=%LocalLowAppData%\Microsoft\Windows\AppCache|*.*|RECURSE FileKey9=%SystemDrive%\Documents and Settings\*Service\IETldCache|*.*|RECURSE FileKey10=%SystemDrive%\Documents and Settings\Default User\Application Data\Microsoft\Internet Explorer|brndlog.bak;brndlog.txt FileKey11=%WinDir%\ServiceProfiles\*Service\AppData\Roaming\Microsoft\Windows\IETldCache|*.*|RECURSE FileKey12=%WinDir%\System32\config\Systemprofile\AppData\Local\Microsoft\Windows\INetCache|*.*|RECURSE FileKey13=%WinDir%\System32\config\SystemProfile\AppData\LocalLow\Microsoft\Internet Explorer|brndlog.bak;brndlog.txt FileKey14=%WinDir%\System32\config\SystemProfile\Application Data\Microsoft\Internet Explorer|brndlog.bak;brndlog.txt RegKey1=HKCU\Software\Microsoft\Internet Explorer\International|CNum_CpCache RegKey2=HKCU\Software\Microsoft\Internet Explorer\International|CpCache RegKey3=HKCU\Software\Microsoft\Internet Explorer\International\CpMRU RegKey4=HKCU\Software\Microsoft\Internet Explorer\LowRegistry\Audio\PolicyConfig\PropertyStore RegKey5=HKCU\Software\Microsoft\Internet Explorer\Main\FeatureControl RegKey6=HKCU\Software\Microsoft\Internet Explorer\PageSetup RegKey7=HKCU\Software\Microsoft\Internet Explorer\Recovery\PendingDelete RegKey8=HKCU\Software\Microsoft\Internet Explorer\TypedURLSTime RegKey9=HKCU\Software\Microsoft\Windows\CurrentVersion\Ext\Stats ExcludeKey1=FILE|%LocalAppData%\Microsoft\Windows\INetCache\IE\|container.dat Are these two entries related to something in particular? Could they be included in Windows Subsystems *?

There is no regular update schedule. The commits I have been linking refer to a branch (Moscadotto-patch-1) that will eventually be merged with the master (and updating the main file with the aggregate of all 25+ commits in the branch), but has not yet been. https://github.com/MoscaDotTo/Winapp2/pull/138/commits/0ad7e965172522011d7cbf3389d494d6808fc7f2

https://github.com/MoscaDotTo/Winapp2/pull/138/commits/dae02f70f73f70bcfadb22ddf33bfac5bbf44f68

Does this location exist on your machine? Several other members have suggested the AppData filekey is invalid.

https://github.com/MoscaDotTo/Winapp2/pull/138/commits/71dda91f4fe0571befeae2225c68be90aa127665

Have the paths also changed, or just the app names themselves? Key might be in use, have you tried ending explorer.exe before cleaning?

Partially for better alphabetization in the CCleaner interface, but also because many entries have been merged together or otherwise heavily modified, and lacking an effective way to communicate these sweeping changes to the end user, changing the name (which will toggle the entry back to disabled) seemed like a good way to indicate that a lot of changes have occurred. If you're worried about the ccleaner.ini bloat, you can trim it using ccinidebug in the top post. If you're worried about resetting your settings, you can find & replace all the "*" to " *" in ccleaner.ini (this will transition over your old settings to new entries, assuming the name hasn't been otherwise changed other than the added space)

https://github.com/MoscaDotTo/Winapp2/pull/138/commits/e74a63e1daedb6c526a3364b6746d17c02e10eee

Given that it's related to Windows Installer, should we fold this into the [Windows Installer *] entry?

What are previous libraries? I don't use iTunes so I was unsure how to approach this entry, but the entry struck me as a "backups" type of entry so I kept it separate. did or does this location exist on any version of Windows 7-10? I don't have it on my Windows10 system either. Any particular reason why? I think now that we've transitioned to merged entries for different versions of the same application (where applicable) it's not so much of a concern to keep outdated versions supported here. This entry has changed a bit (merged with some other) as part of the refactor. Could you reevalulate the changes you've made here against that and resubmit?

the dvdcss folder seems to be created by applications that use libdvdcss so it's a bit hard to find a specific detectfile for it. Given that it's origin is VLC, that might do, but there's a wide variety of applications that use it. It might be more effective here to simply change the REMOVESELF to RECURSE so that the entry is non volatile

I would like to push this update soon: https://github.com/MoscaDotTo/Winapp2/blob/02be21a40fc454a0005a5cfef005d0214dd60723/Winapp2.ini Let me know if anything jumps out as wrong to you folks

Here's the rest of the links to various newsletters. Photon Engineering Newsletter: 13: https://msujaws.wordpress.com/2017/08/18/photon-engineering-newsletter-13/ 14: https://mikeconley.ca/blog/2017/08/24/photon-engineering-newsletter-14/ 15: https://dolske.wordpress.com/2017/09/11/photon-engineering-newsletter-15/ 16: https://dolske.wordpress.com/2017/09/22/photon-engineering-newsletter-16/ These weeks in firefox: 23: https://blog.nightly.mozilla.org/2017/09/12/these-weeks-in-firefox-issue-23/ 24: https://blog.nightly.mozilla.org/2017/09/26/these-weeks-in-firefox-issue-24/ 25:https://blog.nightly.mozilla.org/2017/10/11/these-weeks-in-firefox-issue-25/ 26:https://blog.nightly.mozilla.org/2017/10/26/these-weeks-in-firefox-issue-26/ 27:https://blog.nightly.mozilla.org/2017/11/07/these-weeks-in-firefox-issue-27/ post quantum twif: 28:https://blog.nightly.mozilla.org/2017/11/22/these-weeks-in-firefox-issue-28/ 29:https://blog.nightly.mozilla.org/2017/12/05/these-weeks-in-firefox-issue-29/ Quantum Flow Engineering Newsletter: 20: https://ehsanakhgari.org/blog/2017-08-18/quantum-flow-engineering-newsletter-20 21: https://ehsanakhgari.org/blog/2017-08-25/quantum-flow-engineering-newsletter-21 22:https://ehsanakhgari.org/blog/2017-09-01/quantum-flow-engineering-newsletter-22 23:https://ehsanakhgari.org/blog/2017-09-07/quantum-flow-engineering-newsletter-23 24:https://ehsanakhgari.org/blog/2017-09-15/quantum-flow-engineering-newsletter-24 25:https://ehsanakhgari.org/blog/2017-09-21/quantum-flow-engineering-newsletter-25 Webrender newsletter: 2: https://mozillagfx.wordpress.com/2017/08/21/webrender-newsletter-2/ 3:https://mozillagfx.wordpress.com/2017/08/28/webrender-newsletter-3/ 4:https://mozillagfx.wordpress.com/2017/09/19/webrender-newsletter-4/ 5:https://mozillagfx.wordpress.com/2017/09/25/webrender-newsletter-5/ 6:https://mozillagfx.wordpress.com/2017/10/02/webrender-newsletter-6/ 7:https://mozillagfx.wordpress.com/2017/10/10/webrender-newsletter-7/ 8:https://mozillagfx.wordpress.com/2017/10/19/webrender-newsletter-8/ 9:https://mozillagfx.wordpress.com/2017/11/06/webrender-newsletter-9/ 10:https://mozillagfx.wordpress.com/2017/11/27/webrender-newsletter-10/ Off Main Thread Painting: https://mozillagfx.wordpress.com/2017/12/05/off-main-thread-painting/ Introduction to WebRender – Part 1 – Browsers today: https://mozillagfx.wordpress.com/2017/09/21/introduction-to-webrender-part-1-browsers-today/ Entering the Quantum Era—How Firefox got fast again and where it’s going to get faster: https://hacks.mozilla.org/2017/11/entering-the-quantum-era-how-firefox-got-fast-again-and-where-its-going-to-get-faster/

Debugger tool updated: https://github.com/MoscaDotTo/Winapp2/tree/master/Tools/WinappDebug Output should be much more readable and actionable now. Let me know if you run into any errors. There's also a new revision of the file out for you to inspect: https://github.com/MoscaDotTo/Winapp2/blob/227c1e19870d5d6466791610f3c181f672724a29/Winapp2.ini All the entries have been renamed to end with a " *" instead of a "*"... a side effect of this will be that all your winapp2 settings will be reset after the refactor.

I will update WinappDebug to be aware of this soon.

I think so. It's a little easier to keep all the winapp2.ini stuff wrangled into one thread (and github is easier to maintain than disjoint forum threads)

Thanks! I've gone and fixed that for you here: https://github.com/MoscaDotTo/Winapp2/pull/138/commits/4a55330c63033b0e6a18addc5dc8cb569f893cf6 as part of the next update. Sorry for breaking your symlinks!

That thread is rather old, the current version of WinappDebug can be found here: https://github.com/MoscaDotTo/Winapp2/tree/master/Tools/WinappDebug I think in lieu of a secondary thread, I'll create readme pages on the github and link them with descriptions in the top level post on this thread.

The refactor is on GitHub as reviewable commits. You can find it here: https://github.com/MoscaDotTo/Winapp2/pull/138 Please let me know if there are any glaring errors. Some of the above submissions may not merge well with this, please check against your local file and resubmit anything that is still pending. Further, many entries have been renamed. If you're worried about ccleaner.ini clutter caused by this, I wrote a tool to prune stale winapp2.ini entries from ccleaner.ini. You can find it here: https://github.com/MoscaDotTo/Winapp2/tree/master/Tools/ccinidebug Place ccinidebug.exe in a folder with both ccleaner.ini and your copy of winapp2.ini. It will compare the list of entries in winapp2.ini to the (App) entries in ccleaner.ini and remove any winapp2.ini entries (detected by their *) that no longer appear in winapp2.ini from ccleaner.ini for you.

this large update is still pending

I created a tool for this, you can find it here If you run it in the CCleaner Program Files directory on Windows 10, you must run it as an administrator. It will prune invalid winapp2.ini entries from the file if handed a winapp2.ini file. Use with caution, it only detects entries marked with the winapp2.ini single asterisk for this operation, and will not remove dead winapp.ini entries (of which I wouldn't imagine there are many)

Any particular reason why? As it is, Chrome* covers Chrome and Chrome SxS (Chrome Canary)

It does, and I imagine that's the intended behavior for CCleaner to preserve the state of entries even when they're not detected. I re-wrote WinappDebug to be a little more comprehendible, this update includes pipe symbol (enforces a preceeding backslash) tracking for FILE exclude keys, and alphabetization & numbering tracking for excludekeys, detects, and detectfiles in general. Let me know if anything seems amiss.