DjLizard

Ahem... he means, run CCleaner twice after closing your browsers. If it still persists, empty your cache in Firefox by using Firefox's Tools>Options>Privacy>Cache>Clear. Then don't run CCleaner while Firefox is open anymore. (I'm too buggered to do this, so I simply told CCleaner not to clean Firefox's cache anymore )

you're

It does go to the default browser. At least, for me. ShellExecute() automatically knows this (and that's what I assume MrG uses for that link)... so to prove or disprove this theory, go to Start, Run, and type http://www.CCleaner.com and see which browser opens.

The package installer doesn't even modify any system files (just adds more files to your system, doesn't replace anything) and that's why it doesn't ask you to reboot after installing KB898461. The files from this KB go here: %windir%\System32\PreInstall\WinSE\WXP_%lcid%_v1 and contains the following files: ? Update.exe.ref ? Updspapi.dll.ref ? Spuninst.exe.ref ? Spcustom.dll.ref ? Spmsg.dll.ref ? Spupdsvc.exe.ref I'm not sure how this relates to NTOSKRNL, but you can either ignore the download by unchecking it and telling Windows Update not to show it again, or stop replacing NTOSKRNL. Start patching it with a better utility: http://www.bootxp.net/ It's not really read-only. All folders get an unremovable 'read only' attribute. According to Microsoft, it allows explorer to determine whether the folder is a regular folder or a system folder [as in a special folder, like My Documents, My Pictures, Fonts, etc]. The files inside can be without 'read only', but the folder will stay that way. This is 'by design'. You are still able to delete and rename the folder normally, despite the 'read only' flag being present. About the files that come back, that sounds really weird. Let's verify your NTFS journal is accurate: Start, Run, FSUTIL DIRTY SET C: and then reboot. Scandisk will then run and verify NTFS integrity.

Bump... take note of this! http://forum.CCleaner.com/index.php?showto...findpost&p=7143 Remember that old chestnut? Could it be that these two things are related in some way?

I didn't ask you. At any rate, first `undeletable files/folders' was said, then folder. It doesn't matter though, you're not Newhotness.

google toolbar

You guys aren't getting it. There's a problem. Third party programs should NOT be used, because this behavior shouldn't be happening to begin with. Don't Eldemannen this thread up! At any rate... I want to know about your ntoskrnl problem first (because the first question's answer is more complicated)... what are youusing to patch ntoskrnl, or is it the kind of hack that gives you an already patched ntoskrnl? You could possibly be mixing versions, triggering Windows' QFE to think you need a KB patch. Lemme know about what software you're using, and what exact boot theme you applied, etc. What kind of file are you creating? When you delete it, it comes back? How is that possible... Are you throwing it in the recycling bin or fully deleting it? Next time you anticipate this will happen, click on your desktop once and hit F5... refreshes your desktop -- will make SURE it's gone. Is system restore turned on? Do you have some kind of weird utilities like Norton Systemworks? Some kind of recycling bin protector? Other odd programs? This is peculiar. Do you get an error if you try to delete a file and it fails? What's the error? etc.

I've had this kind of roughness with WinMe + CCleaner as well. Not much we've been able to do to sort it yet. And during an issues scan, even! My WinMe crash experiences were only when doing a file cleanup... never had an issues crash yet... Hmm. Does it go partially through the issues scan before it dies? Try stopping the issues scan partially through, removing what it finds, then starting it again, over and over. Maybe you'll narrow down to a few entries that are causing it.

Thread necromancer. jotti is better.

ok deja vu.. I could have SWORN I just read about this somewhere else (wink wink). You may want to watch out about cross- and double-posting.

Makes sense. Thanks for the link. Right-on about the complacency. Everyone's grown accustomed to using google... little do most know how much google really filters out of the results.

About manual: It's not a firewall, so blacholing an IP involves manually adding the IP to the database. (The program is designed to block 300+ million IP addresses that belong to spammers, P2P robots, US-government watchdogs, spyware sites, rogue advertisement sites, and more) About stateful: It's not a firewall, so it doesn't deal with packets on an 'if-then-else' basis. It discards either all, or none, of the packets from a given IP address. It's not really that advanced for a user. A user can turn it on and forget about it, really. Until they have a problem connecting to a certain IP... then they have to turn off PG to see if PG is blocking it. PS: If you use PG, you have to unblock my website. DjLizard.net's IP belongs to a range that used to belong to scammers/spammers/spyware peddlers, but since those kinds of people are fly-by-night, as soon as they got IP banned in the major lists, they left. Then comes some unfortunately soul (me) who has to deal with the fact that I'm on a banned IP range, all because of someone who was using the IP only for a few moments. IP blocks get bought and sold all the time, and blocklists really wreak havoc on those transactions. :/

Updated my site: released Dial-a-fix alpha v0.2, for public testing.

http://forum.CCleaner.com/index.php?showto...indpost&p=10969

Not a big leap. That's milliseconds you're talkin' about. 22ms to 1000+ ms would be almost a bad thing. Repeated 1000+ ms would be a very bad thing. 2000+ ms would be very bad.

Actually, this problem seems to be happening to several people who are running operating systems prior to Win2k (WinMe/98, etc), and it's not related to the run-times... something in CCleaner internally has changed. MrG will need to do some 9x testing I'm sure. PM MrG and ask what you need to do in order to assist on stomping out this buggie.

It's a new feature... it no longer spews out a giant list of IE's deleted files, it consolidates it into one line that tells you the grand total of the IE-file removal, so the log is much more brief.

Here's some basic information: #1 - `Issues` is not about files [unlike the rest of CCleaner], it's about registry entries. #2 - When you remove orphaned registry entries, those entries orphan some more entries that were depending on them. It is very normal, and a good thing. Simply continue running `issues` scans until it is out of finds.

Do Wordpress, like me :>

Yeah, we know you did, ya friggin' terrorist.

it's a bot, or an idiot.

Those signatures usually cause quite the unnecessary comotion, and as such, are usually banned on most popular forums.

Use an escrow service, that's what they're for.