Jump to content
CCleaner Community Forums


Experienced Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About PurpleHaze

  • Rank
  1. This could be the same problem I experienced. See http://forum.piriform.com/index.php?showtopic=45703 What are the similarities and differences with your problem?
  2. With CCleaner versions 5.10 through 5.14 on 3 PCs with Win8.1 x64, enabling "Run CCleaner when the computer starts" on the admin account results in the CCleaner taskbar icon running for 30 seconds. On a standard/limited account, enabling the same option results in the CCleaner taskbar icon running for 1 second. All 3 PCs have solid-state drives, and they are fast modern PCs. I use Firefox as my browser, but disabling the cleaning of Firefox did not change the 30-second slow down. Disabling Windows Defender and uninstalling all anti-virus software did not avoid the slow down either. My company's firewall prevents CCleaner from initiating internet communications (in case CCleaner is waiting for internet feedback). All CCleaner monitoring options are disabled. CCleaner v5.05 was last version I tested where Win8.1 x64 did not have the extra 29 seconds for admin account logon. On my Win7 x64 PC, all versions of CCleaner mentioned take 1 second on the admin account, just like the standard account.
  3. @nukecad - thanks for posting the solution that worked for you. Hope it helps many other CCleaner users. It didn't help me because I have Windows Defender turned off (not monitoring my computer).
  4. I am experiencing the same bug with CCleaner v5.13.5460 on the admin accounts of my x64 Win8.1 PCs. The CCleaner taskbar icon persists for 30 seconds after restart or cold boot. I have my firewall configured to block CCleaner's internet access (in addition to unchecking the "Automatically check for updates to CCleaner"). I wonder if CCleaner waiting for some internet access before a time-out.
  5. I find that the slow startup on the admin account doesn't always occur when signing out and then signing in. The consistent ways to reproduce the problem are a cold boot or restarting Windows.
  6. With v5.12.5431 on 64-bit Win8.1, I am seeing the same behavior as above with v5.10. I haven't tried Windows 7 yet. The 15-second persistance of the CCleaner taskbar icon on the admin account occurs even though there is no cleaning on Firefox (now v42.0).
  7. I continue to use v5.10 since forum members reported v5.11 is as slow or slower. I have SKIPUAC enabled, monitoring disabled and enable run/cleaning at logon. No anti-virus is running. IE is disabled and Firefox 41.0.2 is my default browser. Some observations... 32-bit Win7 shows the taskbar icon for about 1 second on the admin account and 0.5 seconds on the standard account at logon. This is about the same as CCleaner has always achieved on this PC. Thus, the bug may be limited to 64-bit Windows, On two PCs with 64-bit Win8.1, the taskbar icon takes about 15 seconds on the admin account and 1 second on the standard account at logon. Thus, the bug may be limited to the admin account. I have a CPU meter tray icon from System Explorer, and the CPU is less than 5% while CCleaner is displaying its taskbar icon for 15 seconds. Thus, the bug is not due to CPU loading and may be due to some timeout or waiting. Edit: removed false Firefox testing result.
  8. On the admin account in Win7, I want to clean the same types of files that CCleaner already cleans on a standard/limited account in Win7 when enabling the option "Run CCleaner when the computer starts". I now see three reasons to run the cleaner with limited rights on the admin account when the computer starts: 1. Avoid annoying and slowing down the admin user with a UAC prompt at each login 2. It is safer to clean only files accessible with limited rights because the user does not preview/approve the files to be deleted. 3. It is simpler and more visible to check an option in CCleaner than to read up on command line options and set up Task Scheduler.
  9. I propose to improve users' choice and understanding of CCleaner's action: 1. A separate checkbox under Firefox for DOM storage allows users to clean it without cleaning cookies. (I have cookies from my bank that I don't want to delete, and Firefox already has a mechanism for specifying which cookies are not deleted at the end of the session). 2. Showing the DOM storage file (webappsstore.sqlite) in the analysis details gives the user the choice of changing their mind about cleaning it, and it also alerts the user to the fact that some site created cross-session DOM storage. 3. Deleting webappsstore.sqlite (instead of vacuuming it) makes it easy for average users to understand that CCleaner cleaned it. 4. Deleting webappsstore.sqlite makes it easier to detect if CCleaner has a bug that prevents cleaning of DOM storage 5. Deleting webappsstore.sqlite reduces the average number of files on the hard disk, which increases backup speed. Note that Firefox does not re-create webappsstore.sqlite until some visited site creates cross-session DOM storage. So there is no penalty in Firefox startup speed in deleting it.
  10. Cleaning of registry keys does not apply here. Let's assume for now that CCleaner can clean more files with admin rights than with limited rights on Win7/Vista. As I said before, it sill makes sense to clean only items requiring limited rights at startup so as to avoid annoying the admin user. Or at least give the user the choice of whether the automatic cleaning at logon uses admin or limited rights.
  11. No, I don't want to sacrifice the security that UAC provides. Still hoping someone will answer my question. If there is no difference, then it is easy to implement my suggestion in the opening post. If there is a difference, then it sill makes sense to clean only items requiring limited rights so as to avoid annoying the admin user. Or at least give the user the choice of whether the automatic cleaning at logon uses admin or limited rights.
  12. My Firefox cross-session DOM storage file webappsstore.sqlite contains no cross-session info. When I used all the CCleaner v3.08.1475 checkboxes for Firefox v3.6.18, the data and time for webappsstore.sqlite did not change. Thus, I have no evidence that CCleaner cleans Firefox's DOM storage.
  13. Does anybody have a test web site that causes Firefox to update webappsstore.sqlite after closing? With this, I could test what CCleaner does. So far, I have only found sites that use session DOM storage, which does not cause an update to or creation of webappsstore.sqlite. Also, which Cleaner checkbox under Firefox/Mozilla on the Applications tab affects webappsstore.sqlite?
  • Create New...