pudelein

There is an almost trivial discrepancy in the latest version number for Recuva! No problem for humans, but it is for some computer applications. The context menu Properties page for the executable recuva.exe shows the version as 1.29.0.492. However, the Recuva website says that the latest version is 1.29.492 [without the extra ".0"]. The new CNET TechTracker software stumbles on this, regarding the two versions as different. Clear to me, but hard for machines. Neglecting the ".0" part may in fact not be a generally reliable strategy, I fear.

Thanks to all of the above posters! I had also overlooked the addition of Flash cookies to CCleaner's working subjects. Checking the Adobe Flash Player box took car of the issues altogether.

I am experiencing the same cookie removals issue with CCleaner 2.19.900. In my case, there are 18 cookies listed by CCleaner in the "to be removed" column and this column does not change when the cleaning operations are carried out. However, these are not current cookies in any of IE7, Firefox 3.0.10, or SeaMonkey 1.1.16. They do not appear in my FF3 profile in either of the files "cookies.sqlite" or "cookiesnew.txt". They look to me like old, maybe very old, cookies from sites that have been visited in the past, but not in the last few days (e.g., oprah.com). I don't see any other very likely locations in my FF3 profile, however.

I have the same issue; it can occur with a variety of folder names: I have seen Dc1, Dc2, and Dc5 today in various tests. Some rather tedious setting changes and reboots of my system [Windows XP SP2 fully patched with CCleaner 1.39.502] narrows things to the following combination of things: the CCleaner option "Secure file deletion" must be selected (I use "Simple Overwrite"); there must be contents in the Recycle Bin, although the number of items seems not to matter much (not thoroughly explored! Too tedious!); and CCcleaner must be run at startup (that is, with the /AUTO option). Changing any of these elements avoids the error message. This makes it pretty clear that only the cleaning of the Recycle Bin is involved and that the error involves the secure file deletion step. But it also occurs only at boot! Perhaps this is enough to get a "fix"! Best luck to Mr. G.

As the OP on this thread, I can now report somewhat more definitively on the subject. There are several points, though, as follow here: 1. The latest AVG Free version is 7.5.4 (as of today). It is available for downloading, but not yet pushed to users of the older version. 2. Current users of AVG Free 7.1 will receive "a special dialog within the next few weeks", presumably with special rules for an upgrade, rather than a new total download, or how to preserve settings, or whatever. This is a rough version of what is on the AVG site. 3. Support for AVG Free 7.1 will end in January 2007. 4. CCleaner will not clean AVG Free 7.1: the path to the program files in winapp.ini is wrong for that; presumably the new AVG version will (in essence) correct that. I think this may be enough to terminate this thread.

I have just downloaded and installed the newest CCleaner 1.34 and tested it. I note with interest that it supposedly removes something from Grisoft AVG. However, from the winapp.ini file, the path to the Grisoft material seems to be different from the Free version that I use (AVG Free 7.1.408, dated 10/18/2006); so maybe it is a Paid version 7.5? It would be nice if CCleaner was clearer about this! Cheers!

It occurs to me to ask if the OP knows that the distribution file ccsetup133.exe is the one that contains Yahoo toolbar. He could check by downloading ccsetup133_slim.exe and trying that instead. It would be quaint if the issue were actually in that toolbar!

Thanks to Hazelnut for that link about controlling System Restore Points in Windows Defender! I was getting two or three each day from WD and occasional notices that SR was running out of space even. I implemented the fix (that is, defining DisableRestorePoint) and since then I have had just one such and that not from WD. Very useful tweak imho. There should be a controlling option in WD itself (like there is in Registry Mechanic, for instance).

This thread is still rolling, apparently! I have a more permanent, though nontrivial, solution to the issue of ZoneAlarm logs being cleared (or not!) by CCleaner. My initial issues (cf OP) were solved by the simple expedient of dumping ZAV and retreating to ZAFree, using AVGFree as antivirus. Worked fine for awhile, but at some ZA 6.5 release, resource consumption became intolerable. I have now also dumped ZAFree and will not use ZA products in future, as long as an alternative is available. My current firewall choice is Comodo Personal Firewall (Google it!). Currently version 2.3.3.33Beta. This is also free. It is rule-based, which makes it a little geeky for some, but the product is well-designed and the support is prompt and effective. It does log things it wants to log, but the user controls the maximum log size, so CCleaner can leave it untouched withut issues. The current Beta should appear as a stable release fairly soon; check their forum. CPF Rocks!

I have just downloaded and installed CCleaner 1.30.310 (slim) and tested it. Looks great except for one point, namely, the overly thorough cleaning of the Windows Defender logs. WD had run a scan on my system at noon today (about 3 hours ago) and the log file for this was among the executed members. I believe it would be very much better to respect the optional 48-hour delay in removing such files. Meanwhile, I have disabled the WD log cleaning for now. Edit: additional information. Further to the above, I should point out that Windows Defender reports the results of its last scan on the "home page". If the logs have been cleaned by CCleaner, this report cannot be made. The "last scan" is then reported as "unknown". I have not seen a report from a scan that finds "issues", but I suppose it would also be lost if present, not a good thing!

It has been a long time since I wrote the first post above! I suppose you are referring to the file tvDebug.log which can grow enormous over time. I control mine as follows: I use a folder C:\Program Files\Local to house personal executables. You can use any folder in your PATH instead. I attach a script, tvDebug.txt, which I use. It explicitly refers to my folder, but is easily edited for any other. Rename it to tvDebug.bat, edit as necessary. You will also need a zero-length file in the same folder named "tvDebug.log". Create this by opening Notepad and then storing its blank contents under this name. I run the script at startup every time I boot the machine. My tvDebug.log is never very large; currently less than 10 kB. Good luck! tvDebug.txt tvDebug.txt

I am also grateful to Mr. G for fixing CCleaner: Windows has traps for evan the most wary users sometimes! On other points made in the last few posts, I note that $hf_mig$ contains only files from hotfixes. It does not contain anything from Service Packs (SP2 in particular), thus greatly reducing the labor for those needing manual repairs. Actually, from what I have read here and elsewhere, my suspicion is that most of us are rather unlikely to ever need the items in that folder, and maybe Bill Gates will come out with SP3 this Spring and remove the necessity. My backup file only had some 47 (I think it was) subfolders, not including those from the February Patch Tuesday exercise. Can that be all that there have been since SP2 arrived?

CCleaner already seems to manage FF cookies just as I want! After closing Firefox or IE, although not Opera, open CCleaner; select Options; then Cookies. Now find new cookies that you want to save in the left-hand column, highlight them, and use the adjacent arrow to move them to the other (save) column. Works like a charm.

Thanks to everyone in this thread for the heads-up about the $hf_mig$ folder! Like at least two or three have mentioned, I found this folder missing, but luckily had a backup dating from before the most recent update of CCleaner and could recover it as of early February. Only the most recent set of patches is missing.

Here's another ote for TreeSize. Works great.

This folder is not handled automatically by CCleaner, I believe. It can grow quite large. I have added it to my "Custom Folders" and have experienced no problems as a result. I believe the 48 our limit applies here also.

Is it possible that the real issue here is that brotherS is using an English localization of CCleaner with a German localization of Win2K? The German folder names in Andavari's answer are merely translations of the English lines just above. I don't know if a German localization of CCleaner is available, but if not, perhaps it should be.

There might be some advantages in adding regular expression parsing to CCleaner cookie and other sections, but it won't work very well for forums. I have something like 8 forums in my cookie lists: 1 "forum.*", 1 "forums.*" and six that don't use the word at all, like "castlecops", for instance. Designing regular expressions that will cover large groups of cookies is almost certainly very tricky or impossible.

On my Windows XP Home SP2 system, under my own administrator-class account, there is a folder Local Settings\Temp which is not cleaned by CCleaner. I know that I can add it to CCleaner if I wish. However, before doing this I wanted to solicit opinions on the value of the apparent trash remaining therein. It is currently about 11.5 MB and seems to be full of leavbings from installing Firefox extensions (.xpi files) and other detrirus.

You may be right! Text editors (like yours, Notepad, etc) show nothing useful. However, I can view my Opera cookie file with Filesnoop, something I got some years ago from PC Magazine. I use it constantly to look at files of any kind: it makes either something like an old-fashioned hex dump, a text file, ot one formatted per the extension. I attach a screenshot that displays my cookies.

Although CCleaner now cleans out Opera cookies, if allowed to, it unfortunately ignores the list of exceptions (CCleaner Options | Cookies). It ought to respect the list in the same was that it does for IE and Firefox cookies. I have had to uncheck Opera Cookies to prevent unwanted deletions!

I am using OpenOffice .org 2.0: I agree that it is great, especially the price! I have spent a little time looking for something that CCleaner (also great and the same price as OO.o!) could get its claws into. There is a file C:\Documents and Settings\ {username}\Application Data\OpenOffice.org2\user\temp. In the above, {username} represents a user account name. Nothing is in mine at the moment and I don't know how it is used, but it could be an entry point. I agree it might be nice to give OO.o the same treatment as MS Office.

On the Windows tab, do one of the following: 1] UNcheck Advanced; or 2] be sure that User Assist History is unchecked. Mosat of your other items shoul be chcked.

I reported a couple of days ago that ZoneAlarm Antivirus protects itself against CCleaner's attempts to remove its log file (C:\Windows\Internet Logs\ZAlog.txt in Windows XP). ZA Pro and ZA Security Suite do this also. It is also true of ZA Free. All of these defenses seem to have appeard in the latest versions 6.0.667.000 of these products. Unlike its more costly brethren, ZA Free does not signal what is going on, but the file does not disappear. There is a now an option under Overview | Preferences that is checked by default: "Protect the ZoneAlarm client". The protection does not extend to old logs, however, nor to tvDebug.log.

A new version of ZoneAlarm with Antivirus (ZAV) was announced this morning: version 6.0.667.0. Unlike the previous version (6.0.631.003), it now protects itself against CCleaner (and presumably similar programs) by not allowing it to mess with ZaLog.txt! A tentative solution is to make CCleaner a "Trusted" application. This seems to allow CCleaner to clean out the file in question. Apparently ZA Plus, Pro, and Security Suite all have this feature. I have no idea whether ZA free has similar "ideas". I do not know whether the restriction applies to old ZA logs, which are mostly the ones needing removal. It does not apply to tvDebug.log, at least when it is dealt with by a .bat file as discussed elsewhere in this forum. Thought folks would be interested in this situation! Added note: Making CCleaner a "Trusted" or even a "Supertrusted" application does not allow it to delete the ZAlog.txt file.