Firip

Sorry, but I'm not feeling comfortable with sending a complete debug log. But thank you for the info, I ran Defraggler in debug mode and basically it's the same thing that happens over and over until I pull the plug: [2010-03-30] [17:44:33.639] 00084 1 DefragVolumeSinglePassHelper::DefragInternal#1026 Fragment of unmovable file \$LogFile. Stop increasing potential free block [2010-03-30] [17:44:33.683] 00084 1 DefragVolumeSinglePassHelper::LayFileAt#243 MoveFileRegionWithMarking for file "E:\path\file1.txt" to 49753202, 0, 13094 finished (hr=0x80070026). Destination block is not free. [2010-03-30] [17:44:34.047] 01bc8 1 CVolume::UpdateDriveMap#340 Map generated in 0.05342 seconds. [2010-03-30] [17:44:34.859] 00084 1 DefragVolumeSinglePassHelper::DefragInternal#1026 Fragment of unmovable file \$LogFile. Stop increasing potential free block [2010-03-30] [17:44:34.890] 00084 1 DefragVolumeSinglePassHelper::LayFileAt#243 MoveFileRegionWithMarking for file "E:\path\otherfile.htm" to 49753211, 0, 13085 finished (hr=0x80070026). Destination block is not free. I have millions of those "Fragment of unmovable file \$LogFile" things in my debugfile. And the whole time the display said: Defragmenting (100%), 12 fragmented files (6,7 MB) in 24 fragments, 0% fragmented

When I defrag my 1.5 TB drive (on Win7 x64) Defraggler seems to to a good job (latest version). But after a loooong time, Defraggler finally reports 100% done... but is still working...somehow. The file display shows changing files as if Defraggler is working on them but these seem to be a set of about 50 files that rotate and Defraggler never stops. When I stop manually and check again for fragmentation I get only three files reported. Manually defragmenting per right-click does the job in seconds. So it seems there is a kind of loop that prevents Defraggler from finishing. Sorry for not being able to be more specific, hope that helps anyway.

Me again. As promised I checked my other PC. And indeed: in the CCleaner GUI the update checkbox isn't checked but in the ini-file the mentioned line above is missing (what causes the update check). So that seems to be a bug. I couldn't make the line appear by toggling the ini-checkbox but once I enabled the update check and disabled it afterwards the line was there.

Thanks for your quick replies! I stumbled over this due to an error with my local proxy software (proxomitron) which reports missing components while launching the CCleaner update page. I guess without the proxomitron problem I would never have noticed that. Actually, I already checked with autoruns but didn't find anything suspicious. Also I have that ini-setting checked and the update-setting unchecked (did that in the first install). I toggled that a few times and checked the CCleaner.ini afterwards. The corresponding line says UpdateCheck=0 I just had the idea to compare that with a Backup I made a few weeks ago, since I never changed that setting. And guess what? In the backupped CCleaner.ini the "UpdateCheck=0" line is missing. Which brings me to the thought that the setting wasn't properly saved when it was made. I will keep an eye on it the next days. Maybe the added line now prevents CCleaner from update-checking. I'll also check on my other PCs (same configuration). If there's the same problem, I'll report back.

I have set CCleaner to *not* automatically search for updates. Nevertheless, with each Windows-start the URL http://www.CCleaner.com/update is launched. How can I stop this?