pwillener

CCleaner 2.18 was just released a few days after IE8, with IE8 support included. However, there were a few bugfixes for IE8 in later releases of CCleaner. I suggest that you install the latest version of CCleaner and see if the problem persists. See also if this article helps with the 0x80070002 error: http://support.microsoft.com/kb/910336/

I did not give any "advice"; I just asked what anti-virus & anti-spyware the poster had installed.

Can you tell the error code with which these updates fail? Go to http://www.update.microsoft.com/, then click on Review your update history. Click on the icon to find the error code(s).

removed malware advice

most likely it is not a "her" most likely the user has been disabled from logging in

Do we have this patch (PM flood control) installed: http://forums.invisionpower.com/topic/2829...p;#entry1794928 ? I have received the same PM spam on numerous other forums; these guys are very active with their scam. They won't be stopped just by a user deletion; they will sign up as 'Judith' or whatever. (The sign-up and post IP address usually is 196.207.192.198, and the contact address is always something at Yahoo UK. And as we know Yahoo, they absolutely refuse to close these scam email accounts!)

There are always small fluctuations due to Windows and other services' I/O on the Windows install drive; the 65KB you mention may be typical. However, 22GB (CCleaner claim) vs. 155GB (actual freed space) is a huge difference - that is 700% of what was expected! I think Alan is right to be curious about this enormous difference.

Alan, just to give some more thoughts about the "slack space" theory, do you know the cluster size of your C: drive?

I am also curious about that. It appears as if CCleaner reports far less than it actually frees up; could it have something to do with the phenomenon called "slack space"? (Slack space being the unused parts of the clusters that files occupy.)

You may be (partially) right; the doc at http://docs.piriform.com/ccleaner/introduc...em-requirements states that "CCleaner will run on any PC running Microsoft Windows 98 or later." .NET Framework 2.0 installs on Win98, but later versions 3.0 and 3.5 require XP or higher.

My guess is compatibility with older Windows systems. I don't think .NET Framework can be installed on Win9x systems.

I have never lost any CCleaner settings, and I don't use the .INI file. I always install over the existing version; this does keep the current settings.

I ran Defraggler (in debug4 mode) today, starting with 2% fragmentation. It finished within 3 hours. 3 hours still seems long to me, but it is not the original problem (50 hours). I wonder if it is something to do with running Defraggler for the first time? Since the Diskeeper and Defraggler methods are so very different, maybe - even though it is showing only 1% fragmentation, it has a lot to do for the initial defragmentation? I may also need to mention that I use the "Quick Defragmentation" method wit Diskeeper - which does not defragment free space.

Yes, it is an older computer, which serves me well in most respects. Specs: Operating System Windows XP Professional Service Pack 3 System Model Dell Computer Corporation OptiPlex GX260 Processor 2.25 gigahertz Intel Pentium 4 8 kilobyte primary memory cache 512 kilobyte secondary memory cache Memory 1022 Megabytes Installed Memory The HD on which the C: drive resides is an IDE\ST3200822A (200GB). The "crazy" partitioning layout resides on 3 HD drives, and is due to historical/legacy reasons, as well as current needs. I cannot imagine that having a few more partitions than normal would influence program behavior. But I will start a debug defrag this evening, so hopefully Piriform will find out what's taking so long...

Thank you, 'romanoff', for your PM. I will run Defraggler in debug mode next time, and send you the logs. (Just to show other forum members that Piriform has contacted me about my observations.)

And after 50 hours - defrag complete. Still 5 fragmented files, 30 fragments, and a total of 6.4 billion I/O. And... the pagefile has not been moved! Here my options How do I actually get certain files moved to the end of the partition? (Tried to look up help & docs at http://docs.piriform.com/defraggler, but all I get is "Could not contact back-end site".)

48 hours after it started... 71% complete, 6 fragmented files, 33 fragments, 6,140,000,000 I/O. What is it doing...?

Now, 20 hours later, 13% is defragged. 2,600,000,000 I/O have been performed, and the thing still runs using near 100% CPU. If it continues on this rate, it will take 11 days to complete...

This is the first time to use Defraggler - I usually use Diskeeper on a daily basis. I tried Defraggler because I want to use it to move some files (pagefile.sys) to the end of the C: partition. However, it takes extremely long! The C: drive is 1% fragmented, but after 4 hours the defrag process is only 4% - see attached image. Is it normal that Defraggler is that slow? [Defraggler 1.10.143 on Windows XP-SP3] P.S. just checked Task Manager; so far it has done 375,000,000 I/O, running at near 100% CPU usage.

Just add the quoted lines to the existing winapp2.ini file.

The image that you show is on the Filehippo download page, and the highlighted area seems to be part of the Google Ads section. Filehippo is an independant download provider, and CCleaner or Piriform has no influence on their content or layout.

No. Most likely you have a problem with a device driver. Was there a module name written under the 0x000000D1 error code (something ...sys)? P.S. also, what is your Windows version?

Installing a Service Pack always poses a slight risk; it is therefore highly recommended to take a full backup of your system before the install. Installing a Windows Service Pack on a malware-infested computer poses a very high risk! Make sure that your system is 100% malware-free before proceeding. Run CCleaner (not the registry cleaner part) before installing the SP to clean up as much unneeded data from your HD or partition as possible. Defragment your HD or partition before the SP install; this will likely speed up the installation process. I don't think that you will need to worry about corrupt registry entries or device drivers if you follow these simple steps.

Or use the Windows Installer Cleanup Utility to remove all traces from the previous installation. After that you should be able to install the software again.

Look at the Processes tab, to see if anything uses very high CPU.