APMichael

Just for your information: The "empty.check" is not a new function, but only a fantasy file pattern. You can use any file pattern you like, which is normally never used by programs (examples: "abc.xyz" or "no.content"). By the way, the culprit really seems to be the "Microsoft Provisioning".

@dvdbane Most entries for "Metro Apps" clean up the "AC\Temp" folder, so this should be safe. I think we can add this to Winapp2.ini. @CSGalloway https://github.com/MoscaDotTo/Winapp2/issues/391 @Andavari The FileKey of your entry should work, but I would still recommend the "official" syntax: FileKey1=%WinDir%\System32\config\systemprofile\AppData\Local\tw-*.tmp|*.*|REMOVESELF To make sure that only empty folders are deleted, a "fake" file pattern can be used: FileKey1=%WinDir%\System32\config\systemprofile\AppData\Local\tw-*.tmp|empty.check|REMOVESELF

Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/57ffa85d23ab869dd1e01e5d42a5b13aac95aeb2 Winapp3.ini update: https://github.com/MoscaDotTo/Winapp2/commit/f0c1ffa59c9380e1e4afb42da8b9a81e90422930

I guess the entries "DeleteMe=" are caused by the CCiniDebug feature of Winapp2ool. @Winapp2.ini should be able to help here.

@ricktendo64: Many thanks for your reply. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/a395bc93477a182494e6d64dffd513ecae8a719e

And this is exactly the reason why CCleaner freezes when the HealthCheck is activated. As I explained in my previous posts.

I think we've got two freezing issues mixed in here. With some users CCleaner freezes already during the installation. For other users the CCleaner GUI freezes right after startup. A screenshot won't help much here, because CCleaner is loaded completely, but is not usable. With every click nothing happens, except that a sound is played. A solution for this problem can be read here: https://community.ccleaner.com/topic/56994-update-freezes/?tab=comments#comment-315830 https://community.ccleaner.com/topic/56994-update-freezes/?tab=comments#comment-315886 The problem can be easily reproduced. Simply delete the value "DisplayIM" (HKCU) from the registry.

On all systems I use Windows Defender with PUA protection enabled. Excluding CCleaner with the whitelist will not cure the frozen GUI. Windows Defender will also usually notify you whenever it blocks a PUA. I could find another solution: If the regsitry value "(Cfg)HealthCheckIpm" (HKLM) is deleted or set to 0, CCleaner starts with the introduction of the HealthCheck and sets the necessary setting "DisplayIM" (HKCU) itself. Therefore the installer probably sets the wrong start value for "(Cfg)HealthCheckIpm".

On one PC, I also had the problem that the GUI was frozen immediately after starting. (The installation went through without any problems). This problem is definitely related to the HealthCheck. If I deactivate the HealthCheck via Registry, the GUI works. Afterwards I compared the settings with another PC and found the cause. The other PC has the following additional CCleaner setting: "DisplayIM=1-1|2-1|". If I add this setting the GUI works again even if HealthCheck is activated. Can Piriform please clarify this? Thank you.

Suggestion: Ricktendo64 has reported that Windows Apps now have a (shader-)cache folder from AMD. In my opinion it is not really necessary to clean up these folders per Windows App, because: - The folders are not app-based, but driver-based and are only redirected into the app container. - For classic Win32 applications, the (shader-)cache can also not be cleaned separately per application, but only for all applications together. - It would also simplify the maintenance of the Windows App entries and save many duplicate lines. Therefore, my suggestion would be to add the FileKeys to the entries [AMD/ATI *] and [NVIDIA *]. [AMD/ATI *] FileKeyX=%LocalAppData%\Packages\*\AC\AMD\DxCache|*.* [NVIDIA *] FileKeyX=%LocalAppData%\Packages\*\AC\NVIDIA Corporation\NV_Cache|*.*

Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/cd026108ddd2368982840f63d938a58893dec21f Edit: Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/359ed9c264bac02ef4445cb87bb003a5e2ba4f8d (Revised and removed entries for Edge Chromium, as it is now officially supported by CCleaner.)

You can add the browser to CCleaner using one of the following methods: https://www.ccleaner.com/docs/ccleaner/advanced-usage/ccleaner-ini-files/how-to-clean-user-data-from-non-standard-mozilla-browsers CustomLocation1=CHROME|path_to_user_profile: https://community.ccleaner.com/search/?&q="CustomLocation1%3DCHROME" Example: CustomLocation1=CHROME|C:\Users\<your user name>\AppData\Local\Yandex\YandexBrowser\User Data\Default

Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/81159e6c5eb478890e7ffb772446d1e0979601f4 Winapp3.ini update: https://github.com/MoscaDotTo/Winapp2/commit/7c71f8aafde1de7af0cee17d8858a4282f391a53

Unfortunately, many suggestions and fixes do not seem to have a high priority at Piriform...

Great! I'm glad I could help. In the Winapp2.ini you will not find "Detect=" with "WOW6432Node" because CCleaner adds it under 64-bit internally by itself.

Did you also check "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node" for an "ESET" key? Programs that are coded in 32-bit add their registry keys there under a 64-bit operating system.

Did you use regedit.exe and delete the following registry keys? - Navigate to "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ESET" and delete the key (subfolder) "ESET Security". - Navigate to "Computer\HKEY_CURRENT_USER\Software" and delete the key (subfolder) "NVIDIA Corporation".

Great, thanks for testing. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/016580b88f9f9495a424e2fc69f51942519484fc https://github.com/MoscaDotTo/Winapp2/commit/ca593aac40ea63f7296a548aae5a5235cb54137d Winapp3.ini update: https://github.com/MoscaDotTo/Winapp2/commit/e21a5fe87a47841460008a340b8ef181a0a1baed Edit: Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/d2316d85226b54e9b39e610f3dcf07004b9091c3

Yes, such a check would be helpful. But please note that wildcards are allowed before the pipe symbol (in the path). Wildcards should therefore only be checked after the pipe symbol.

The use of the semicolon (;) is not always invalid. If wildcards are also used, it may be used. Please see example 5: https://www.ccleaner.com/docs/ccleaner/advanced-usage/ccleaner-ini-files/how-to-exclude-items-from-ccleaners-cleaning.

- Run "Notepad" as administrator (via the right-click menu). - Use "Open" and navigate to the CCleaner installation folder (C:\Program Files\CCleaner). - Open the file "winapp2.ini". - Copy the entry [Caprine *]. - Paste it at the end of the file and save it. - Start CCleaner and the new entry should appear.

Caprine is obviously based on Chromium. Here is an enhanced entry: [Caprine *] LangSecRef=3022 DetectFile=%LocalAppData%\Programs\caprine Default=False FileKey1=%AppData%\Caprine|*-journal;LOG;LOG.old|RECURSE FileKey2=%AppData%\Caprine|Network Persistent State FileKey3=%AppData%\Caprine\*Cache|*.*|RECURSE FileKey4=%AppData%\Caprine\blob_storage|*.*|RECURSE FileKey5=%AppData%\Caprine\Caprine\logs|*.* FileKey6=%AppData%\Caprine\logs|*.* FileKey7=%AppData%\Caprine\Session Storage|*.*|RECURSE FileKey8=%LocalAppData%\caprine-updater|*.*|RECURSE Can you please test this for possible side effects? Thank you very much.

Have you ticked the cleaning rule System > Clipboard? Cleaning the clipboard can cause problems on a terminal server.

Thanks for the updated entry and the suggestions. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/af19741e2843548b28282451d731b608d7885148 https://github.com/MoscaDotTo/Winapp2/commit/8603eb24e2effdac2524218c9f438c9b4cbef932 https://github.com/MoscaDotTo/Winapp2/commit/908656de85d0c29c856714164f0abbb139adbc27 Winapp3.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/8797dcc4fec56e1fb2df643169ea0dd1ff62559b https://github.com/MoscaDotTo/Winapp2/commit/c7107785e386e7937d833bb43e6575e7582eedc2

Thank you for the revised entry. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/213687ed9cb3ab9cdfbc40fcfd1b955383f966ef Winapp3.ini update: https://github.com/MoscaDotTo/Winapp2/commit/8caf484888c1624ff0a8266777a1508bfeba3017