I think it's time the devs gave some direct input regarding the problems you guys are having with CCleaners Wipe Free Space feature.
I can only comment on the feature in Windows, but one thing I have just confirmed is that Wipe Free Space does the job in two entirely different ways, depending upon how it's launched, and I don't know if this is the same with your Mac version.
If WFS is launched via "Options\Settings", with either normal or secure file deletion, and the "Wipe MFT Free Space" is unchecked, the wipe is done with the creation of one file, which grows to the size of your free space and is then deleted ...
If "Wipe MFT Free Space" is checked in the above, the following method is used.
If WFS is launched via "Tools\Drive Wiper", then the wipe is done with the creation of a folder carrying a multi-digit number, containing other folders, containing lots of files, and all carrying names with variations of Z's ...
... and in both cases, if the process is stopped before completion, the single file, or single folder and files are automatically deleted. I stopped the process before completion with both methods above, and the file/folders did delete instantly.
So if this isn't happening with your Macs, you need to look for either a single numerically named file, or a similarly named folder containing the stuff shown above. I have no idea as to whether the Mac has dual options like this, and if not, which method it may be using.
As I mentioned in one of the other threads, there are freeware programs out there which enable you to seek out and display every file and folder in every location on your computer, which will help hopefully in finding where your free space has gone.
http://alternativeto...t/?platform=mac
And this copied and pasted from one of the other threads ...
One final thought, and the Mac users on here may be able to enlighten us on this point ... I'm wondering if the Mac has a service running similar to "Volume Shadow Service", (System Restore) which makes shadow copies of any files it considers as being modified, which includes file/folders being moved around by defragging.
This in the recent past has unknowingly (to the folk who weren't aware of this), eaten up drive space of comps running Vista and Win7.
In the meantime, I will point the devs to this thread as it does appear that WFS is not working as it should.
Hope that may help.