0 Byte Files don't get deleted
Started by belinda frisch, Apr 25 2007 10:09 AM
12 replies to this topic
#1 OFFLINE
Posted 25 April 2007 - 10:09 AM
hi folks,
just updated to CCleaner v1.39.502. now files with the size of 0 bytes don't get deleted anymore (e.g. 0 byte files in the temp folder, or in any custom folders i set). v1.38.485 had no problem to delete those files so i stepped back to this. any explanation or workaround for v1.39.502 to get all files deleted?
thanks in advance
belinda
just updated to CCleaner v1.39.502. now files with the size of 0 bytes don't get deleted anymore (e.g. 0 byte files in the temp folder, or in any custom folders i set). v1.38.485 had no problem to delete those files so i stepped back to this. any explanation or workaround for v1.39.502 to get all files deleted?
thanks in advance
belinda
#2 OFFLINE
#3 OFFLINE
Posted 25 April 2007 - 02:07 PM
I have also had this issue with the new version - would not delete 0byte files in content.IE5 as reported HERE.
I have tried the previous version and it did delete the 0byte files so definitely something not quite right with the new versions handling of some 0 byte files.
Belinda, do you have secure deletion enabled? If so try cleaning without secure delete enabled to see if those 0 byte files are deleted and let us know what happened. The secure deletion method was changed in this version, perhaps that could be the problem (I can't check this now as using the old version removed the files that the current version was missing).
I have tried the previous version and it did delete the 0byte files so definitely something not quite right with the new versions handling of some 0 byte files.
Belinda, do you have secure deletion enabled? If so try cleaning without secure delete enabled to see if those 0 byte files are deleted and let us know what happened. The secure deletion method was changed in this version, perhaps that could be the problem (I can't check this now as using the old version removed the files that the current version was missing).
#4 OFFLINE
Posted 25 April 2007 - 02:20 PM
Ok, I have just recreated this issue and can confirm it is the secure deletion that is causing this issue. 0 byte files are not removed with secure deletion enabled but ARE removed if secure deletion is turned off.
Hopefully this can be fixed soon.
Hopefully this can be fixed soon.
#5 OFFLINE
Posted 25 April 2007 - 05:29 PM
Andavari, on Apr 25 2007, 12:15 PM, said:
Version 1.39 still deletes 0 byte files on my system, I just tested it with six of them.
Same here.

All the crap is detected and cleaned as usual, except index.dat files.
Not solved neither installing the previous version
@JDPower
I don't use secure deletion
Guide in italiano per CCleaner - Recuva - Defraggler - Speccy
#6 OFFLINE
#7 OFFLINE
Posted 25 April 2007 - 08:17 PM
I use secure deletion and get the same bug
zero kb files dont get deleted
zero kb files dont get deleted
#8 OFFLINE
Posted 26 April 2007 - 12:10 AM
JDPower, on Apr 25 2007, 09:20 AM, said:
Ok, I have just recreated this issue and can confirm it is the secure deletion that is causing this issue. 0 byte files are not removed with secure deletion enabled but ARE removed if secure deletion is turned off.
#9 OFFLINE
Posted 26 April 2007 - 02:20 AM
same problem here, only secure file deletion is bugged with 0 byte files.
#10 OFFLINE
Posted 26 April 2007 - 10:47 AM
Same problem here, in addition the message "CCleaner has encountered a problem and needs to close.." etc always appears, with any secure delete mode.
#11 OFFLINE
Posted 26 April 2007 - 01:16 PM
Confirmed on my PC too.
Using secure deletion the zero-byte files aren't deleted.
IMO would be nice add at this forum a pinned topic showing all the "known bugs".
Using secure deletion the zero-byte files aren't deleted.
IMO would be nice add at this forum a pinned topic showing all the "known bugs".
Guide in italiano per CCleaner - Recuva - Defraggler - Speccy
#12 OFFLINE
Posted 26 April 2007 - 02:11 PM
Hi all,
The problem has been isolated to the secure delete code and a fix is in the works.
MrG
The problem has been isolated to the secure delete code and a fix is in the works.
MrG











