Jump to content

PICPro

Experienced Members
  • Posts

    87
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

907 profile views
  1. I'm don't know what version of CCleaner that this changed. I'm pretty sure that those entries used to work as is. I recently installed Thorium browser on my WIndows 7 x64 computer to have a more up to date Chromium based browser. I added Thorium lines to the [Chromium ... *] entries in Winapp2.ini and that all went well, but when I tried to use the additional entries from Winapp3.ini, I noticed that the [Chrome ... *] entries didn't show in CCleaner's list event though the detects were satisfied. I found that both the entry name and the section name affected this and I am using CCleaner 6.16 at the moment. It is very weird indeed. Anyone else want to try it?
  2. I don't know if Archived entries.ini or Winapp3.ini are being maintained anymore, but here is something of note. I found it odd that these Winapp3.ini entries will no longer show up in CCleaner 6.16 when they are pasted into WinApp2.ini even though they are properly formatted: [Chrome Indexed Database Extended *], [Chrome Installer *], and [Chrome Local Storage Extended *] What I have found is that entries starting with "Chrome", or contain "Section=Dangerous Google Chrome" will not show up in CCleaner's list. Changing these entries to: [Chromium Indexed Database Extended *] Section=Dangerous Chromium (... rest of entry etc.) [Chromium Installer *] Section=Dangerous Chromium [Chromium Local Storage Extended *] Section=Dangerous Chromium [Chromium Software Reporter *] Section=Dangerous Chromium solves it and the entries then work correctly. It is very strange, but seems to be a quirk in CCleaner. WinApp3.ini and Archived Entries.ini are both affected.
  3. I agree that "Module Info Cache" should be deleted. I don't find any harm in deleting it. Since it may affect some aspect of the browsers that I don't use, hopefully others can test this too. Other Chromium based browsers have this file too. For for Vivaldi, the path is: %LocalAppData%\Vivaldi\User Data|Module Info Cache For Opera, the path is: %AppData%\Opera Software\Opera Stable|Module Info Cache OperaGX is similar. I don't have Google Chrome to test with. The file contains paths and filenames to many of the installed programs and Windows files. If you use a sophisticated text editor like Notepad++, and turn off the control and non-printing characters and set the text encoding, you can easily view the plain text portion of the file. Vivaldi recreates "Module Info Cache" when a non-private window is closed. Opera recreates the file when a URL is loaded, even in a private window. The newly recreated files were significantly smaller. Because this file may contain references to programs that have been uninstalled or files that may have been deleted, it represents a small privacy risk.
  4. xulstore.json is automatically regenerated if deleted, however, since the previous contents are lost that had view and position setting, the newly generated file has the firefox defaults like after a fresh install. The customization of the View->Toolbar settings are lost along with some window dimensions. It makes sense to delete it if it is corrupt, and then re-set things up. But this isn't something that you would want to clear when cleaning up cached items.
  5. Also xulstore.json in FileKey60 of [Firefox Caches *] in Winapp2.ini.
  6. There are a couple of issues in [Firefox Caches*] in winapp2.ini in version 290901. 1. "xulstore.json" has been included for deletion in the %AppData% profiles. Deleting xulstore.json causes the menu bar setting to be lost in Firefox, FirefoxESR, Librewolf, Palemoon, etc. and the status bar view settings in Palemoon. This file doesn't contain personal data or urls or other privacy related issues that I can tell. It is just for maintaining the toolbar presence and window locations. I think that xulstore.json should be removed from those lists (FileKey2, 8, 14, 20, 26, 32, 38) 2. Basilisk is included in the %LocalAppData% FileKeys (FileKey43, 44, 45). Basilisk is not included in the %AppData% FileKeys with the other browsers. Basilisk should be added back in here starting at FileKey7 and can have the same treatment the same as Palemoon. This browser is back in active development now for some time. Thank you.
  7. Thank you for updating! Just a note that in Version 230719 Winapp2.ini, in the main branch, that the entry of [OpenRGB *] is duplicated at line 14492 and 14497.
  8. Recent versions of the Opera browser for Windows have been making files with names like "session_4481fa2a-fdc4-459a-9d99-fb65644930ba.raw" in the StatsSessions folder of the Opera profile. A another new one is created at each program start and they build up to a lot of files after a while. CCleaner doesn't clean them. I haven't been able to determine the purpose or decipher the contents of these files to determine which Winapp2 Opera entry to add this entry but I think it is prudent to empty this folder from time to time. FileKey1=%AppData%\Opera Software\Opera Stable\StatsSessions|*.*
  9. Just a note for people using version 230316 that the "non-ccleaner" version of winapp2.ini still has the problematic [Windows Temporary Files *] so be careful and check.
  10. Were these files in the downloads folder? i.e. C:\Users\(username)\Downloads? Did you check any options under "Windows Downloads" in Custom Clean? CCleaner versions starting with 6.06 have this section: which selectively removes files from this folder. Personally, I think this is a terrible addition to ccleaner because for many people the downloads folder is long term file storage and this will remove these files. If file overwriting is turned on, then the files won't be recoverable either. Obviously one should always do an "analyze" first and check if there is any actions listed that aren't desirable. Still this section is rather dangerous. A stray mouse click could accidentally enable one of the line items and the next "Run Cleaner" click would immediately remove those files which aren't temporary or privacy related files. Most of the other things CCleaner removes aren't a big deal if lost, but this section directly removes a user's data files.
  11. In Winapp2.ini 20230301 there is: [Windows Temporary Files *] LangSecRef=3025 Detect=HKLM\Software\Microsoft\Windows FileKey1=%SystemDrive%\Documents and Settings\LocalService*\Local Settings\Temp|*|RECURSE FileKey2=%SystemDrive%\Documents and Settings\NetworkService*\Local Settings\Temp|*|RECURSE FileKey3=%Temp%|*|REMOVESELF FileKey4=%WinDir%\ServiceProfiles\*\AppData\Local\Temp|*|REMOVESELF FileKey5=%WinDir%\System32\config\systemprofile\AppData\Local\Temp|*|REMOVESELF FileKey6=%WinDir%\System32\config\systemprofile\Local Settings\Temp|*|REMOVESELF FileKey7=%WinDir%\SystemTemp|*|REMOVESELF FileKey8=%WinDir%\SysWOW64\config\systemprofile\AppData\Local\Temp|*|REMOVESELF FileKey9=%WinDir%\TEMP|*|REMOVESELF Filekey3 will remove everything from the %Temp% folder. This can affect running, active applications. CCleaner already cleans this folder (System->Temporary Files) for files older than 24h by default or can clean it fully if the user changes the setting. Because some web browsers make temp files in %Temp%, and sometimes leave them behind, there is an argument for cleaning some temp files sooner, but it is probably better to make specific %Temp% cleaning rules for the leftover files from the application of interest that one wants to remove when cleaning and add them to their own custom.ini file.
  12. version 220615 of Winapp2.ini had this entry: [WebRender Shader Cache *] LangSecRef=3026 Detect1=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\Mozilla.Firefox_n80bbvh6b1yt2 Detect2=HKCU\Software\LibreWolf Detect3=HKLM\Software\ComodoGroup\IceDragon Detect4=HKLM\Software\FlashPeak\SlimBrowser Detect5=HKLM\Software\Mozilla\Basilisk Detect6=HKLM\Software\Mozilla\Pale Moon Detect7=HKLM\Software\Mozilla\SeaMonkey Detect8=HKLM\Software\Mozilla\Waterfox DetectFile=%AppData%\Mozilla\Firefox FileKey1=%AppData%\Comodo\IceDragon\Profiles\*\shader-cache|*.*|RECURSE FileKey2=%AppData%\FlashPeak\SlimBrowser\Profiles\*\shader-cache|*.*|RECURSE FileKey3=%AppData%\LibreWolf\Profiles\*\shader-cache|*.*|RECURSE FileKey4=%AppData%\Moonchild Productions\Basilisk\Profiles\*\shader-cache|*.*|RECURSE FileKey5=%AppData%\Moonchild Productions\Pale Moon\Profiles\*\shader-cache|*.*|RECURSE FileKey6=%AppData%\Mozilla\Firefox\Profiles\*\shader-cache|*.*|RECURSE FileKey7=%AppData%\Mozilla\SeaMonkey\Profiles\*\shader-cache|*.*|RECURSE FileKey8=%AppData%\Waterfox\Profiles\*\shader-cache|*.*|RECURSE FileKey9=%LocalAppData%\Packages\Mozilla.Firefox_*\LocalCache\Roaming\Mozilla\Firefox\Profiles\*\shader-cache|*.*|RECURSE Unfortunately it seems to have been lost. When Firefox or its variants have hardware acceleration enabled, the \shader-cache folder starts filling up. If hardware acceleration is turned off, then Firefox doesn't make these files. I see that the IceDragon FileKey1 migrated to Archived Entries.ini but the rest doesn't seem to have been carried forward. I don't know if this should be added to [Firefox Caches *] or if this should remain a separate entry for those who don't like to clear the shader cache for whatever reason.
  13. Winapp2.ini used to contain this entry: [Opera *] LangSecRef=3027 DetectFile=%LocalAppData%\Opera\Opera* FileKey1=%LocalAppData%\Opera\Opera*|*.log FileKey2=%LocalAppData%\Opera\Opera*\application_cache|*.*|REMOVESELF FileKey3=%LocalAppData%\Opera\Opera*\icons|*.*|REMOVESELF FileKey4=%LocalAppData%\Opera\Opera*\logs|*.*|REMOVESELF FileKey5=%LocalAppData%\Opera\Opera*\temporary_downloads|*.*|REMOVESELF FileKey6=%LocalAppData%\Opera\Opera*\thumbnails|*.*|REMOVESELF FileKey7=%LocalAppData%\Opera\Opera*\vps|*.*|REMOVESELF FileKey8=%UserProfile%\.opera|*.*|REMOVESELF FileKey9=%UserProfile%\Downloads\.opera|*.*|REMOVESELF FileKey10=%UserProfile%\Downloads\Opera Autoupdate|*.log FileKey11=%UserProfile%\Opera Autoupdate|*.log RegKey1=HKCU\Software\Opera Software|Last CommandLine v2 This was the entry for the older Presto based Opera Browsers (up to Opera 12.18) which Opera last updated in 2016. I understand removing this from Winapp2.ini as obsolete, however this entry didn't migrate to "Archived entries.ini" with the other obsolete entries for people to retrieve the entries if they still need them. Since this program is still used by some people for its newsreader, RSS reader, email, chat client, etc, I think this entry should be put into Archived entries.ini for those who could use it. Presto based Opera is still supported in CCleaner in Winapp.ini for basic cleaning. Probably this entry should now be renamed to something like [Opera 12.x *], [Opera Presto *], [Opera Pre Chromium *], or something like that to avoid confusion with the new Opera browser that is quite different. Thank you.
  14. It is nice to see this project active again. I've been waiting to see what the revamped version all contains before adding more contributions. I really like how it turned out so far. Thank you. Running Vivaldi browser, adds a file, usually zero byte, to the root of the user profile called ".vivaldi_reporting_data", at least when installed in Program Files for all users on Windows 7 x64. I'm suggesting to add FileKey12 below to remove this file. [Vivaldi Telemetry *] LangSecRef=3033 Detect=HKCU\Software\Vivaldi FileKey1=%LocalAppData%\Vivaldi\Application\SetupMetrics|*|REMOVESELF FileKey2=%LocalAppData%\Vivaldi\User Data\*|Media History FileKey3=%LocalAppData%\Vivaldi\User Data\*|Network Persistent State FileKey4=%LocalAppData%\Vivaldi\User Data\*\Feature Engagement Tracker|*|REMOVESELF FileKey5=%LocalAppData%\Vivaldi\User Data\*\Network|Network Persistent State FileKey6=%LocalAppData%\Vivaldi\User Data\*\Site Characteristics Database|*|REMOVESELF FileKey7=%LocalAppData%\Vivaldi\User Data\*\VideoDecodeStats|*|REMOVESELF FileKey8=%LocalAppData%\Vivaldi\User Data\BrowserMetrics|*|REMOVESELF FileKey9=%LocalAppData%\Vivaldi\User Data\Crashpad|metadata FileKey10=%LocalAppData%\Vivaldi\User Data\Crashpad\reports|* FileKey11=%ProgramFiles%\Vivaldi\Application\SetupMetrics|*|REMOVESELF FileKey12=%UserProfile%|.vivaldi_reporting_data RegKey1=HKCU\Software\Vivaldi\BrowserExitCodes
  15. If you don't want the Explorer View settings removed, then don't remove them, but for some people it is a very good idea to remove them as they represent a privacy concern. The Explorer View Settings comes from a section in the registry known as the "ShellBags". Windows creates a ShellBag entry for each folder that is viewed in Explorer. There can be privacy concerns for many people if these are not cleared. Each ShellBag includes the full path, folder name, creation time, last access time, and last modification time for each folder. It also includes the last visited date and time for each folder. These are retained even after the folders are removed and ShellBag entries are created even for folders on external drives, network drives, and sometimes even search results. If you use a ShellBag analyzer program you will find this information for any previously viewed folders on the hard drive, network drives, removable media, etc.
×
×
  • Create New...

Important Information

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