Jump to content
CCleaner Community Forums


Experienced Members
  • Posts

  • Joined

  • Last visited


0 Neutral
  1. Would it be possible to provide more explanation of this change? Adobe Flash Player is still listed under the CCleaner Applications. Should be leave it checked, unchecked or ignore that setting? How do we provide persistence in our Flash Player settings? Do we need to use CCleaner to save a specific cookie (what's the name(s) of the cookies supposedly listed in the Cookies to Delete list? I don't see any Flash Player specific cookies listed there). Sorry, but I got lost trying to figure out what was changed in CCleaner and what I'm supposed to do about the change to either purge or keep my Flash Player settings. Thanks. Update: I'll try to explain my findings since I did not receive clarification from the developer. Subsequent to the above finding, I found on the CCleaner Multimedia Applications list that Adobe Flash Player was not checked. After checking that item and running the CCleaner Analyze function, I noticed many more items marked for deletion. These items are Flash settings files. Apparently some of these files or the contents of some of these are being listed in "Cookies to Delete" when the Adobe Flash Player option is unchecked and then when Run Cleaner is executed, those items listed remain. However, when the Adobe Flash Player option is checked and then when RunCleaner is executed, the "Cookies to Delete" list is emptied. I'd still appreciate an explanation as the documentation doesn't deal with this change yet. The names of the Flash Player "Cookies to Delete" don't match up to the list of items in the Analyze list even when they are the only items being analyzed. Nevertheless, there is some connection between the two but it's not clear what that connection is.
  2. **Revised** For non-admin users, CCleaners's "Cookies to Delete" list is not being purged but the cookies on that list are being deleted as confirmed by IECookiesView from NirSoft. So, this is a new bug in this version 2.19. I have confirmed that this bug does not exist in version 2.18. For non-admins, CCleaner Cleaner settings, Windows Tab, Internet Explorer, the only item checked for those users is Cookies. In IE8, all users, I've set the Browsing History Delete to NOT delete cookies prefering instead to have CCleaner selectively delete cookies with its Save list. For non-admins, CCleaner preserves the cookies on the Save List after cleaning during the current session AND preserves those same cookies after a system restart. This is so in versions 2.19 and 2.18. The user's CCleaner settings are also preserved even when the CCleaner application is uninstalled and reinstalled by an administrator. For admin users, I've set CCleaner to clean ALL Internet Explorer items and also to save two cookies: google.com and doubleclick.net. During a session, cleaning will remove all but these two cookies. However, when the system is restarted, those two cookies are removed even though CCleaner does not identify in its Analysis that they will be removed. So, this is definitely a bug in the new version and the behavior is different than that of non-admin users! However, I have now confirmed that this bug also exists in version 2.18 but I had overlooked it because I rarely use the administrative profile. After uninstalling version 2.19 and reverting to version 2.18 I can report that the behavior is the same for both versions. The deletion of cookies on a system restart that were on the CCleaner Save list is confirmed in version 2.18 and 2.19. For non-admins only, the persistence of cookies listed (from current and prior browsing sessions) on the CCleaner Cookies to Delete list AFTER a cleaning is confirmed only in version 2.19. This bug did not exist in version 2.18.
  3. Before the installation of CCleaner v2.19, I checked each of my user's CCleaner configurations for accuracy and inclusion of specific cookies and files/folders. Each user on the CCleaner computer has their own registry settings. WinXP SP3 IE8 is installed with the following settings for the Browsing History Delete: Preserve favorite website data: No Temporary Internet Files: Yes Cookies: No History: Yes Form Data: Yes Passwords: Yes InPrivate Filtering Data: No If you set Cookies: Yes, IE8 will wipe out your cookies regardless of your CCleaner settings so setting IE8 so it preserves cookies allows CCleaner to selectively remove cookies. Users on our CCleaner equipped system include an administrator and two power users. Only the administrator has full access and results from CCleaner actions. Those without administrative rights may not have access to remove files. For example, power users can't remove all the Temporary Internet Files so CCleaner's actions in this regard leave files untouched. To overcome this, we allow IE8 to remove the Temporary Internet Files. The lesson here is to know what application has the rights to carry out your wishes. CCleaner and IE8 have different actions and rights and you will need to analyze these to get them assigned correctly. Before you update your CCleaner, you should run a batch file to capture each user's CCleaner settings. The batch file looks like this: @echo off rem This batch file exports (regedit /e) CCleaner current user settings rem from the registry to a regedit version 5 file, CCleanerSave.reg with username prepended regedit /e %USERNAME%-CCleanerSave.reg "HKEY_CURRENT_USER\Software\Piriform\CCleaner\" Look at what this file saves and you get an idea what CCleaner settings are placed in the registry so you can manage those settings better. A text file of commands for restoring the settings is attached to this post. I use NirSoft's IECookiesView application as an aid in testing where cookies are involved. But this application cannot save and restore cookies which would be a useful utility to have. It will save a text version of the cookies which is informationally interesting but doesn't resurect deleted cookies. My results: I had some problems with the new version of CCleaner but I had backups of my CCleaner settings and cookies so I simply uninstalled CCleaner and reinstalled it and it seems to work well. I would be interested in the CCleaner developer being more clear on exactly what changes were made in the new version 2.19 with regard to IE8. I think transparency in letting users know some detail of exactly what was wrong and how it was corrected would provide users with more confidence in the product and our ablilty to use it. Thanks for all the work on this fine product! CCleaner_RestoreSettings.txt CCleaner_RestoreSettings.txt
  4. Mike, I don't believe NT4 SP6 is supported by Microsoft any longer. Therefore, the programming for CCleaner would likely not support unsupported operating systems. Check this link: http://support.microsoft.com/gp/lifewinfaq
  5. Eraser will do exactly what you need it to do. DBAN is great for rebuilding systems from scratch. You only need to wipe one time, however. In fact just use DBAN defauts for those times you want to start all over with a fresh drive, OS, applications, etc. Eraser, on the other hand, erases files, folders and/or free disk space. You will need to learn and understand how it works to be effective. Understand that when Windows deletes a file, nothing happens except the file name is removed from view and the space occupied is marked as available. So for your cleaning, you need to ask youself what you want to clean and why. To prevent casual review of your browsing history, use Eraser to delete directory entries and you're done. Takes a few minutes. If someone is likely to get to your hard drive and try to recover files, use the Wipe Free Space option along with deleting directory entries and, while you're at it, clean the cluster tips if you have a few hours. Seriously, though, this whole cleaning thing isn't what it's cracked up to be. With IE8 it's even more complicated. Your InPrivate browsing files get deleted which means the files are still there and Recuva can see and recover them. So much for InPrivate. The only way around this is NOT to allow Windows to delete anything. That way CCleaner can be switched to do a secure delete, delete (and rename with Z's) and overwrite. But you've got to educate yourself on how to tell Windows NOT to delete files. If you allow any of those IE files to be deleted by Windows, you will need to use Eraser and/or a combination of Recuva and Eraser to get rid of the files and the directory entries. Watch out for IE's Advanced setting Empty temporary files on exit. It's not the default but lots of user's check it. If you do, Windows deletes the files but leaves them exposed and available for recovery. Any time you think you've wiped out your browser traces, think again. Log on as an admin, run Recuva and see what you've left behind. Cleaners could get paranoid about all this. There is no way to do private browsing short of installing VMWare server with a separate OS then targeting it's temp file for a nuke session with Eraser. InPrivate is the least of the privacy options. It simply is not private but it does delete the files automatically. It should be called AutoDelete (Recover with Recuva).
  6. I've been running IE8 on WinXPProSP3 with CCleaner. With administrative rights, the index.dat file gets cleaned properly on the reboot. But for users without administrative rights, that's not the case. Those users can't clear out their cache index. The files themselves are cleared but not the index. You can see this in action when you use Nirsoft's IECacheView utility. Run an IE8 session as a user without administrative rights then close the browser. Open IECacheView and you'll see the contents of the cache for the logged on user. There's a column on there called Missing File the files will all say No. Then run your CCleaner to wipe those files. It will also suggest that the index.dat will be scheduled for deletion but that doesn't happen unless you have admin rights. Anyway, after CC runs, go back and refresh IECacheView and you'll see in the Missing File column, the files say Yes indicating the cached files are gone but the listing is there because it looks at the index.dat file. Now reboot, log on as the same non-admin user and check the status of the cache with IECacheView. The index file listing is still there. If you follow these steps for a user with administrative rights, after you reboot and log on as admin and check the cache with IECacheView, the cache will be clear. So how to clear the cache of users without admin rights? Log on as an admin and use 7-Zip to navigate to the user's Temporary Internet File folder and clean it out. I recommend this rather than Windows Explorer because 7-Zip can find the folder even when the Explorer Files option is set to hide system files. Otherwise, to use Explorer, you'd have to turn off the hide, delete the folder in question and turn on the hide (for safety). I'd like to be wrong about cleaning out those IE index.dat files but I've done some extensive testing and I believe this problem is documented in the CCleaner help as a known limitation. There is another issue with IE8 that has not been addressed and that is the new content in two new file folders: C:\Documents and Settings\USER\IECompatCache and C:\Documents and Settings\USER\IETldCache. I don't know if these are getting cleaned or not.
  7. Indeed! The necessary checkbox is located at: Cleaner > Advanced > Wipe Free Space. The documentation has since been updated to reflect this and is located at: http://docs.piriform.com/ccleaner/using-cc...free-disk-space which describes not only this checkbox to activate the feature but another located under Settings to select the drive which will be subject to the free space wipe. I ageee that we would like to see some brave souls run this option on some test systems before we jump in and test on our production systems. I don't have the luxury of an extra computer so I'll wait patiently for others to post.
  8. Wipe Free Space Drives Documentation Missing from FAQ, Documentation and Tour. Granted it's a new function although it would be useful to have some background help with the function. On my WinXP SP3 system, I could not verify that the function actually ran. I don't know if it is supposed to run when CCleaner runs or if it's a separate function that can be run standalone. There appears to be nothing more than a checkbox for the drive whose free space is to be wiped. With that C:\ box checked and with admin rights, I run the CCleaner Analyzer option and it does not indicate it will do any more than its normal cleaning. There is no indication a free space wipe will occur. When Run Cleaner is begun, it takes the normal time (10 seconds) and reports the normal cleaning results but no results relating to a free space wipe. The only conclusion I can make is that free space wipe isn't functioning. However, that doesn't explain the windows errors another user reported when using the CCleaner free space wipe. So, what am I doing wrong? I installed version 2.17.853 on top of the previous version 2.16. My reference point with free space wiping is Eraser which pops an "are your sure" warning before starting, allows several levels of wipe and reports back after a usually lengthy (hour) free space wipe. I don't see any of that with the free space wipe in CCleaner. I must be missing something key to the function and would appreciate some feedback.
  9. When CCleaner Option, "Run CCleaner when the computer starts" is checked, and the options are NOT stored in an INI file, an entry is created in HKCU\Software\Microsoft\Windows\CurrentVersion\Run. This would suggest the option should be titled, "Run CCleaner when the current user (who sets this option) logs on." On multi-user home systems, I've had several folks tell me that CCleaner is not running even though the "Owner" set it to run "when the computer starts." It would be useful to have a CCleaner option to clear all the user profiles according to either a master profile or as set by each user but I suppose that would be too complicated? Otherwise, perhaps the wording of the option could be updated in a future release.
  10. Cookies to save (keep) are in the each individual user's registry at: HKEY_CURRENT_USER\Software\Piriform\CCleaner\CookiesToSave You can use reg.exe (it's in C:\WINDOWS\system32) after reviewing how it works (see KB310516) to update the registry.
  11. Actually, the cookies to keep are in the user's registry at: HKEY_CURRENT_USER\Software\Piriform\CCleaner in an entry called, CookiesToSave You can export this to a file. You'll want to do this for each user account on the computer if you're re-imaging. Otherwise, if you're just rebuiliding one user profile, export just that user's registry settings.
  12. Hotfix, Security, OS Updates no longer listed. CCleaner under Tools, Uninstall, Programs to remove Environment: Windows XP Pro SP2 all updates and hotfixes applied Last Microsoft Security Update: January 8, 2008 Last complete listing of CCleaner Tools\Uninstall Programs to Remove: January 10, 2008 Last CCleaner program update: Ver file date January 17, 2008 installed January 18, 2008. CCleaner Configuration (see the attached ini file content) Cleaner\Windows: Hotfix Uninstallers is NOT checked Cleaner\Applications: ALL of the items are checked Registry\Registry Integrity: ALL of the items are checked Note that these settings have been in effect for over a year without issues. Problem: The Windows Add and Remove Programs listing and CCleaner's Tools\Uninstall, Programs to Remove listing are usually a mirror of one another. On January 28, 2008 I noticed both listings were abbreviated and both were missing the Hotfixs, Security updates and OS updates for Windows Media, XP, IE7. Restoration of the CCleaner registry backup from the last cleaning on January 10, 2008 did not restore these hotfix and update listings. It's possible Microsoft slipped in an undocumented automatic update (certainly none were documented in Windows Update) but more likely is the new version of CCleaner as that's the only update made between the last known good configuration and the current state. I do tech work for a living and pay close attention to my system. Would appreciate MrG taking a serious look at this. Let me know if you need the winapp, winreg and winsys.ini files submitted. It's not a critical issue since the updates are installed and can't be uninstalled without damaging the system anyway. All the original uninstall folders and contents are intact in C:\Windows.
  13. The Run (In Start Menu) is not functioning as expected in CC 2.03.532. The run commands are cleared only on logoff and/or shutdown/startup. It would be useful, if possible, to have the Run commands cleared in the current session as well. Environment: WinXP Pro SP2 all updates applied. Problem exists for admin and non-admin users. I do not recall this being an issue with previous versions. 12/5/2007
  14. IE7 running on WinXP Pro with SP2 (and all updates applied) includes a Browsing History Delete option on the Tools, Internet Options, General tab. Use the Delete All to clean up index.dat files although the "All" will also wipe cookies you may have set to save with CCleaner. Use the individual cleaning options, except the cookie cleaner, to leave your favorite cookies. To see how this IE7 cleaning differs from CCleaner's, download Process Explorer from Sysinternals (http://www.microsoft.com/technet/sysinternals/default.mspx). With Process Explorer running, start IE7. In Process Explorer, show the lower pane (Control-L) and use the View option to set the Lower Pane View to display DLLs. Once you're set up, highlight iexplore.exe (Internet Explorer) in Process Explorer. In the lower pane, after a brief delay, you'll see lots of entries. Scroll down to the index.dat entries. There will be several. You can double click any one of them and on the Strings tab see the content of the selected index.dat file. The first thing you notice is data you would prefer not to be there including history, cookie data, etc. depending on which index.dat file you're examining. When you run CCleaner, the content of index.dat files doesn't change (until perhaps you reboot). However, if you use the IE7 Delete All function (keeping IE7 and Process Explorer open) you can go back and immediately, by opening them with Process Explorer, see what clean index.dat files look like. I prefer the real-time deletion of IE7 but I like the convenience of CCleaner. So I use CCleaner for a single click wipe of the Temporary Internet Files and browsing history (but not the corresponding data in the index.dat files) to solve browser problems caused by these files. Then I use the IE7 deletion options for my session.
  • Create New...