>>it only erased the new version but not the old version which is still on disk in plain text.
Eraser only erases what it is told to erase. For temp files or deleted shadow copies we have the freespace erase option.
The NAS will not act as a standard file storage. Erasing freespace may not guarantee you erase the data on all individual disks in the NAS array. Your best option is to use something like truecrypt/veracryprt on the NAS as a container and erase that.
What happens if you reboot - is the mapping...
There are just too many variables to get an accurate estimate. you can get an initial estimate, then some windows process kicks off and doubles the time.
DBAN has the advantage in that it boots up in its own OS, thus is the only app accessing the disk.
When EFS encrypts a file, it copies its contents into a temporary hidden file. It then encrypts by blocks and writes the encrypted data into the original file. After the process is done, the temporary file is deleted. To guarantee erasure of the file you need to wipe the freespace and the file...
Probably your drive has a fault. Running eraser could have hit the bad sectors. Just by creating a new document would trigger the same effect. If you can attach the disk to another PC, you might be able to read the contents otherwise its time to use your backups.
I assume you have done the windows update? This sounds like an issue with your .NET install.
Have a look at this link http://blogs.k10world.com/technology/delete-net-cache-versions-server/
Might help but make sure you understand what you are doing.
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.