Jump to content

APMichael

Experienced Members
  • Posts

    984
  • Joined

  • Last visited

Posts posted by APMichael

  1. 6 hours ago, siliconman01 said:

    So you are suggesting that the code be....which looks good to me for Winapp2.ini.  It does look like there is a "permissions" issue, however, that prevents CCleaner from actually cleaning out these files.

    Strange! On my systems CCleaner removes all font cache files without any permission issues.

     

    4 hours ago, Andavari said:

    Why risk cleaning the Font cache at all?

    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.

  2. 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

  3. 4 hours ago, siliconman01 said:

    Modified entry:  [Nvidia *]
    ...
    FileKey7=%CommonAppData%\NVIDIA Corporation\NvFBCPlugin|logError.txt;LogNvFBCPlugin.txt;LogPluginError.txt
    ...

    Thank you for your modified entry.

    Wouldn't it be possible to use "log*.txt"? Or are there any important "log*.txt" files?

  4. 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.

  5. Quote

    DCBC2A71-70D8-4DAN-EHR8-E0D61DEA3FDF.ini

    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.

    16 hours ago, SMalik said:

    Right, the help files can be deleted without any issue, but this location does not belong to any Microsoft Office version.

    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:

    office2010_help.jpg

  6. 13 hours ago, SMalik said:

    ...
    Changed the order of the Filekey's
    ...

    Thank you for the revised entries.

    Please use the alphabetical order to avoid errors with Winapp2ool. Thank you!

    13 hours ago, SMalik said:

    ...
    Removed %LocalAppData%\Microsoft Help|*.*
    ...

    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.

  7. I think we can remove the following Chrome entries, because CCleaner cleans the folders by now:

    [Extensions State *]

    cc_chrome_extensionstate.jpg

    [GPU Cache *]

    cc_chrome_gpucache.jpg

    [Session Storage *]

    cc_chrome_sessionstorage.jpg

    If you find more "duplicate" entries, please report them. Thanks!

  8. 2 hours ago, SMalik said:

    ... Changed LangSecRef from 3021 to 3023
    [CyberLink Media Cache *] ...

    24 minutes ago, siliconman01 said:

    Should change the following Cyberlink items to " LangSecRef from 3021 to 3023", eh??
    [CyberLink Install Files *] [CyberLink Downloader *] [CyberLink Crash Files *]

    Yes, thanks for the hint.

  9. 2 minutes ago, SMalik said:

    That is better.

    How about CyberLink Media Cache?

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

    And many thanks for your revised entries.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.