You may have misunderstood. The remnants in my case were note kept by the USN journal but more likely one of the MFT copies, as Joel said, since no USN journal exists on the tested partition. Wiping the free-space and also including non used MFT should clear these references. I am not sure what...
What else would make a second copy of a file if not the USN journal? There are no indexing services active nor is there an "$Extend\$UsnJrnl:$J:$DATA" anywhere on the partition. Fsutil says the same thing. I went on and created a journal and deleted it to make sure the error message "The volume...
The file system is NTFS.
So the USN Journal is the problem? Wouldn't it be possible to have Eraser do a sector search itself for the copy and wipe it on restart or via raw disk access? I have no idea of the technical aspects and how Eraser would write to disk going around the OS but to me it...
I've done some testing myself now with similar results. But you have to search for the test strings before the wipe as well. If I copied the file containing the strings "fresh" over to the test partition it would be there always twice. After running Eraser on that file it seems that it indeed is...
Before doing that I wanted to make sure of that it indeed is a bug. Looking a bit closer into the issue I found that the task document which was created with beta3 has the option "When finished" field set to blank on some files, which is not the case with newly created task docs. Assuming that...
From what it looks right now, Eraser is shutting down my computer when finished deleting files that were listed in a Task Document. None of the files are locked, they are deleted without problems and a very short moment after the last file is gone, the computer will begin to shut down.
This...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.