Jump to content

CCleaner not cleaning Temporary files


Recommended Posts

I'm using CCleaner portable on Windows XP SP2. I've noticed an issue with the System/Temporary files option. When I first run Analyze it shows a correct summary of the files to be deleted (files in Documents and Settings\user\Local Settings\Temp). Then, if I run Analyze again or hit Run Cleaner, the summary shows only a few files for cleaning/deleted. And indeed the files in the Temp folder are still there. The CCleaner will show the correct summary again only if I reboot the PC, but again, it won't clean the files. Am I missing something? :(

 

P.S. - I'm not sure since which version this issue occurred, but I think that it's there in all of the 3.x versions. I've attached two screenshots to this post, hope this helps :)

post-46360-0-44824600-1299915899_thumb.png

post-46360-0-98822000-1299915909_thumb.png

Link to comment
Share on other sites

I see a lot of ns???.tmp folders.

I get a few ns???.tmp files as a result of using many portable applications,

and they tend to be in use and un-deletable whilst the application is running.

Link to comment
Share on other sites

Only the first folders in the temp directory are visible from the screenshot, but there are definitely a lot of files that should be deleted and are not in use - like old setups, update packages and other stuff. The weird thing is that CCleaner cleaned all the files before (the 2.x versions). I'm posting two more screenshots from another PC, also with WIN XP SP2.

post-46360-0-97157700-1299936863_thumb.png

post-46360-0-65845500-1299936875_thumb.png

Link to comment
Share on other sites

I have no such problem using CCleaner v3.02.1343 (I tend to avoid being an "early adopter")

but I have been using SP3 for a long time.

 

Perhaps CCleaner series v3 is proven on SP3 but like other products is not quite compatible with mere SP2.

It may be appropriate to install SP3 whilst there is a residue of support for XP.

 

Has something else locked these items which survive CCleaner ?

Can you manually delete them ?

Link to comment
Share on other sites

Yeah, I can delete them, they are just temporary files. I'm deleting them manually for some time now, and with the new temp files is all the same. About the SP3, I don't think that it has something to do with this issue. I've installed all windows updates released so far, except SP3, but SP3 essentially is all this updates in one package. I've also tested the portable version on 2-3 PCs with XP SP2 and the result is the same - almost all the files in Documents and Settings\username\Local Settings\Temp are not cleaned at all, which is very frustrating because this is one of the simplest things that a file cleaner should be able to do :(

Link to comment
Share on other sites

Do you have a tick on CCleaner / Options / Advanced / "Only delete ... older than 24 hours" ?

 

Perhaps that should be unticked.

 

The file age is based upon the "Accessed" date - not "Created" nor "modified".

I am using the names shown when you view the properties of the file.

 

"Accessed" is NOT access to the file contents.

The instant Windows Explorer looks in the folder that holds the file it has been "Accessed".

 

There are many ways in which something can, without your knowledge, update the "Accessed" date

Link to comment
Share on other sites

Wow! That solved the mystery! I unchecked the option, and it seems to be working now - unfortunately I have no more temp files to try, but I think it will work because CCleaner found 20 files and cleaned 20 files, which is a step in the right direction :) I know about the problems with the file age on Windows, but I didn't know how exactly CCleaner decides whether to clean a file or not. Thank you very much for the help! I'll test again as soon as any new temp files appear :)

Link to comment
Share on other sites

  • 1 month later...

I had this problem as well (I'm using 3.06), but it seems that if you just run the Clean without running Analyze first it will work as well, without having to uncheck the 'only older than 24h' option.

It's probably caused by CCleaner accessing them during the analyze and accidentally updating the last accessed time.

Link to comment
Share on other sites

I had this problem as well (I'm using 3.06), but it seems that if you just run the Clean without running Analyze first it will work as well, without having to uncheck the 'only older than 24h' option.

It's probably caused by CCleaner accessing them during the analyze and accidentally updating the last accessed time.

What sort of Windows ?

 

XP Home has the feature that Windows Explorer modifies the "Date Accessed" of all the files its presents on screen when you view the contents of a folder,

BUT it only presents what it remembers from when first launched.

All instances of W.E. had to be closed before a new one could be launched to show the changes.

W7 Ultimate seems to have fixed this.

 

CC has always been able to analyze and list its targets without triggering this "Date Accessed" defect of XP,

I think it inappropriate to blame CC for this sort of malfunction in Windows.

 

I would suggest your A.V. took notice of the Analyze targets and actually accessed the contents to see if a virus was in them,

or it could be some instability in your Windows whatever that causes the O.S. to make an access.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.