APMichael

For example, the "Windows.edb" file is the Windows Indexing database, and you can only delete it if you stop the "Windows Search" service.

Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/049566c47c4edb16f96ffa6fabdbfa95e3780142 https://github.com/MoscaDotTo/Winapp2/commit/a6ada37fc0bd5cbefc0549b7b0d2ecf28c1fdf9b https://github.com/MoscaDotTo/Winapp2/commit/15f4c4515b9c97e33cdb128e7a30db904ce6a17a Winapp3.ini update: https://github.com/MoscaDotTo/Winapp2/commit/a568a9c69d1283f839beeaf851f00738e3fc2e51

You should have one or more files (and/or a folder) with long apparently random names in C: with a creation date of the wipe and a big file size. If you delete them the free space should be back.

Many thanks for all the replies and the revised entries. Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/ffcdd07e5fcf30b773dd144372ba8b35c0786852 Winapp3.ini update: https://github.com/MoscaDotTo/Winapp2/commit/3fa0712f357afaba2c1d665fa540255c410f7183 Happy New Year!

Strange! On my systems CCleaner removes all font cache files without any permission issues. IMHO it is not riskier than cleaning other Windows related caches, as we will never know what Microsoft will change with the next feature update. Like SMalik, I never had any issues after cleaning the font cache. And I don't think anyone knows the correlations why the FileKey1 caused the boot issue on some systems.

Question: Piriform has removed the font cache entry from CCleaner because it could cause a boot problem (if fast startup is enabled). Should we add the FileKeys of this entry to Winapp2.ini? [Font Cache] FileKey1=%WinDir%\System32|FNTCACHE.DAT FileKey2=%LocalAppData%|GDIPFONTCACHEV1.DAT FileKey3=%windir%\ServiceProfiles\LocalService\AppData\Local|FontCache*.dat It seems that FileKey1 is causing the problem, so we could remove it: https://forum.piriform.com/topic/52857-version-540/?tab=comments#comment-300971

Thank you for your modified entry. Wouldn't it be possible to use "log*.txt"? Or are there any important "log*.txt" files?

You can use the following methods to add other browsers: 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://forum.piriform.com/search/?q=CustomLocation1=CHROME CustomLocation1=CHROME|C:\Users\<your user name>\AppData\Local\Epic Privacy Browser\User Data\Default

Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/42fdc7f9e54ff91b6aaa4536e729f97a73f1e063

Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/395d93fa1b7a13fa3a3f91b1ef36b4bea70b6e36 Happy holidays everyone!

It's really strange that Piriform still hasn't fixed the installer. The installer could run a simple command before copying the new files: TASKKILL /F /FI "IMAGENAME eq CCleaner*"

Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/a1777f00e6a3d31c27f831903e6e4c4840523927 https://github.com/MoscaDotTo/Winapp2/commit/012a355a5721b4d5b2f168035d35f7ba3eae3224 https://github.com/MoscaDotTo/Winapp2/commit/9d179e8a63dcbb0c6b81af35f0e38fc2236d903b

There is a known conflict with the MSI versions of Microsoft Office. Using the utility breaks the online updates for Microsoft Office. Unfortunately, the author of the utility never fixed this. The Click-to-Run versions of Microsoft Office are not affected.

Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/db57757c27f21e8a4c3559692560f50d143fd13a https://github.com/MoscaDotTo/Winapp2/commit/0e9d1d58737ef74f09712f9717f83c2b643da539

I think you misunderstood each other about the build-in entry. SMalik meant the FileKey and not the entry itself. I found the correct description of the file: https://forum.piriform.com/topic/32310-winapp2ini-additions/?page=31&tab=comments#comment-203981 I added a DetectOS to the entry now. The folder belongs to Microsoft Office 2010 (14.0). Microsoft Office 2010 creates the folder and the files when you open the "Help". I just re-tested it:

Thank you for the revised entries. Please use the alphabetical order to avoid errors with Winapp2ool. Thank you! Why should it be removed? It's just the cache of the old "(Office) Help Viewer" and doesn't break anything. The cache is always rebuilt.

Thanks for all the replies. Winapp2.ini updates: https://github.com/MoscaDotTo/Winapp2/commit/bd91aff7a2103ca015c4be5637bcbeee57cedffe https://github.com/MoscaDotTo/Winapp2/commit/abd3f9b74290796d1b117a1d3e8afb540920503b

I think we can remove the following Chrome entries, because CCleaner cleans the folders by now: [Extensions State *] [GPU Cache *] [Session Storage *] If you find more "duplicate" entries, please report them. Thanks!

Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/53eae0a67dc14d67d47945bf8d82f872a527ef5f

Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/10dcd9e909c93a53e196ab41f8c97028faba034c Winapp2ool.exe: https://github.com/MoscaDotTo/Winapp2/raw/976dd4c0885ba3d47e04330b062956dc2e8f5e75/Tools/beta/winapp2ool.exe

Yes, thanks for the hint.

Options > Smart Cleaning > Untick all options.

Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/662b2951e644649b9be3b6d5ce8beb747794ca61 Winapp3.ini update: https://github.com/MoscaDotTo/Winapp2/commit/f13dd8fff2289c27001138c1f9f53978d6f78214

I have compared your custom entries with the Winapp3.ini and have revised or added the entries.

Thank you for your quick reply. Sure, we can name the entry [CyberLink Media Cache *]. And many thanks for your revised entries.