Augeas
-
Posts
4,542 -
Joined
Posts posted by Augeas
-
-
It's been suggested before, and usually given the thumbs down as there are empty folders that might be needed for an application to run, CC would have to scan the whole disk to look for them (and could be several hundred gb), and the risk of my system doesn't work any more posts is too great.
-
You can either include individual files (if there is anything else in the folder you wish to keep), or specify the folder to wipe out the entire contents of the folder. Someone might have a tweak to just do *.tmp files, but it's not something that I've ever done.
-
Is it just me?
At the moment, yes.
-
You can include a folder or specific file to be cleaned in the Include section (remember to tick Custom File in CCleaner/Advanced). If you include a folder then all files in that folder will go, no matter how vital or not they are.
-
Am I the only person who has ran into this issue?
Well, two hours between posts is not really enough time to start worrying, especially as most of Europe is still asleep. The search function will show others who have noticed this.
when running the wipe free space function on the CCleaner it is placing large files onto my C drive and literally flooding it. One alone is using 191 GB and the other is using 29.3 GB. I tried to delete them...Filling your disk with large files is how CC, and most disk washers, work. Are you trying to delete them when CC is running? If you are you shouldn't be. CC will fill the disk and then delete all the large files, leaving you with a disk completely overwritten with zeroes. CC wipe free space is something that really should be left to complete on its own.
If CC has finished (and it will take some time depending on the size and state of your disk) then these files should be relatively straightforward to find - they all have large junk names, live in the c directory, and have a create date of CC run time - and should be deletable. If not post back here, now that we've had our breakfasts.
-
Well, I looked at my Layout.ini file with its endless list of old and sometimes non-existant files, and decided to put it to the sword. I just right clicked and sent it to the recycler. I rebooted, and the start time was even faster than usual, about 45 secs (I'm on XP). But Layout.ini wasn't there. That was about four hours ago. I've had my dinner and watched a film, and now I'm back on the pc. Layout.ini has reappeared on its own in the prefetch folder, exactly the same 203 kb size, with a create time of 18.57 today, and appears to contain the same horrendous list of tat I was trying to remove (the deleted version is still in the recycler). It includes hundreds of fonts, system restore logs, temp int files, browser favourites, and some files that were deleted a long time ago. All the stuff that have sweet fa to do with speeding up the pc. Where did it come from?
This is a little off topic, but a puzzle none the less.
-
Try Recuva normal scan and sort the results on last modified date, and look at files with the date of CCleaner deletion. Or search on filename, the recycler renames deleted files to Dcnn.ext in XP and $Rnnnnnn.ext in Vista. If you find anything recover them to a flash drive.
-
It's only 'old' prefetch data (no, I've no idea what old means) so it would have minimal if any impact on performance. By the state of my Layout.ini file I don't think that CC touches it, more's the pity.
-
Hmm. $Extend\$UsnJrnl appears to be an NTFS file that isn't used by Windows and is disabled by default in XP (but not in Vista), but can be enabled and accessed by applications. I don't seem to have one. It apparently logs file changes (when enabled) and is used by indexing and bizarrely by Windows Live Messenger (definitely not on my pc). It's also apparently a sparse file, which I haven't quite managed to grasp, perhaps having entries in the MFT but no actual space allocated. There are reports of applications showing huge space allocations falsely.
If it is enabled then applications such as defaraggers can cause it to grow, but it should return to a more modest size - a few mb - after a reboot. Although explorer doesn't show metafiles it certainly counts the space used in its reports.
I'll pass on part two this time in the evening.
-
When stuff is deleted it leaves the entries in the master file table (that's what Recuva uses to list what's deleted) available for other newly created files to use. The MFT probably uses some sort of first available entry algorithm to choose which entry to use, so the most recent entries (i.e. the files most recently created and deleted) are the most likely to be reused. If some event happens on Jun 13th, say a sys restore point, new application download or update, Windows update etc it could wipe out (or resuse) a whole chunk of MFT entries. Thus the gap between May 30th and June 14th.
-
Wipe free space will overwrite unused space and leave all existing data and system files untouched, so you would have to remove your data, and non-O/S applications, manually, which is a pain. Do it in reverse order, get rid of the data and applications and then run CC wipe.
Your best plan is a destructive wipe, such as Dban, and then a fresh install, but you will need a Windows disk. Or use a free Linux O/S and Gui. Or let the new owners sort out the O/S.
-
There's no particular reason, from Recuva's point of view, why lnk files are found and not the originals. Files deleted to the recycler are renamed to Dcnn.ext in XP (nn is an ascending number) and $Ixxxx.ext and $Rxxxx.ext in Vista (xxxx is random chars). I think that the $R files contain the data.
-
I can't see this working unless CC had a list of every temporary file that every application ever written might create. If PC Translater keeps ini files in the temp int files folder then it's very poor programming. Many users clear temp int files on browser close, as they are quite entitled to do so.
-
It will not affect any live files, just free space on your disk. Whether or not you use it is up to you to decide as it takes some time, it isn't a forensic wipe, and it looses its effect as soon as you start using the pc to view or create files again. But you may have a compelling reason.
-
Only the system drive is cleaned with the normal CC functions. I would think that that's because there are named system or application files installed by default on the system drive. There is no way of telling whether any similarly named files on non-system drives are suiitable for cleaning or not. CC doesn't handle non-default installations. Files and folders on non-system drives can be included in CC's cleaning, but the entire file or folder is 'cleaned', not just temp files.
-
Yes and no. It's best to have a look at the Piriform documentation, at http://docs.piriform.com/
-
Edited - Answered elsewhere....
-
Cheers, Mike. I don't actually know how delete sys rest points work, just guessing. We need some clarification from the developers. Can you see the contents of your System Volume Information folder (I can't)? If so you could perhaps see if the folder relevant to the restore point is deleted or not when you do a CC delete. Or perhaps someone else who has access could try this.
Take care in those trucks.
PS We have some stony faces too, mostly MP's fine tuning their expenses.
-
Do you mean that after a wipe free space you can still see the file names using Recuva? If so then this too is a valid operation, CC wipe free space does not (as far as I know) overwrite file names in the master file table. The test is whether what you recover is actually the original file.
-
Morning Mike (4.50 am post, where are you?). I don't think there's anything missed. I wonder if the Remove Restore Points function is not quite what we might have assumed it to be? In the Piriform documentation ( http://docs.piriform.com/ccleaner/using-cc...-restore-points ) the emphasis is on security. There is no mention of recovering any space. Although I only removed a couple of points when the facility became available, to see how it works, I seem to remember that it took no time at all. I'm on XP and a restore point is around 50 mb: there would have been a reasonable amount of whirring and grinding to delete that. On Vista there would be several times more to remove.
So, does CC just remove restore points from the restore point table/logs? Maybe removing the actual data selectively is too complex or dangerous, or simply not possible?
-
If the error message says that c:/$MFT is corrupted then you appear to have a problem with the master file table, possibly the slot holding the CC file name. I would suggest that you presevere with chkdisk (I can't really grasp what what you're saying about running chkdisk). Or try some simple attempts to fix the problem. Try to rename CC to CCleanerbad.exe and then do a fresh install. The proper solution, at least the first step, is to get chkdisk running cleanly.
-
That's strange. If you right click on say, Old Prefetch data, what do you see? I get Analyse, Clean, and in a separate box at the bottom of the list Restore default state. I'm on 20.920, I can't remember when this came in, quite recently. You should be getting this: I'm on XPHSP3, do other Vista users see this option? It doesn't seem the sort of thing to be O/S dependent.
-
Right click on setting, select Restore Default State.
-
Just do it, then.
Question on CCleaner delete
in CCleaner
Posted
If you have left the default settings then this should be quite safe and beneficial (just click Run CCleaner).. Steer clear from registry clean until you are more confident.