C:\ did not have its cluster tips erased because of the following error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
C:\$RECYCLE.BIN\S-1-5-21-748510194-217282370-3783705229-1000\$RD96SV5.tmp\MFT_DIR\0\1\1\3\2 did not have its cluster tips erased because of the following error: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
C:\$RECYCLE.BIN\S-1-5-21-748510194-217282370-3783705229-1000\$RS08PRZ.tmp\MFT_DIR\0\0\2\4\5 did not have its cluster tips erased because of the following error: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
C:\Boot did not have its cluster tips erased because of the following error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects\SystemIndex\SystemIndex.Ntfy21.gthr did not have its cluster tips erased. The error returned was: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
C:\Users\AppData\Local\Temp\IswTmp\Logs\FFApi.swl did not have its cluster tips erased. The error returned was: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
These are some samples of the errors I receive. Are these errors of any importance? If so, what would you recommend in order to solve them? The recycle bin errors have me curious.
Another question I have is that I'm wondering if when Eraser ends with the disk space error and I have to manually remove the files; is it as effective as if the process had finished completely, besides the MFT problem, is it still effective in terms of overwriting the freespace and the cluster tips, making them irrecoverable?
My third question is in relation to cluster tip failures; are my previous questions in any way related to them? I ask because I've noticed that on other free space wiping programs, it automatically fails when it attempts to wipe file slacks but Eraser at least gives an attempt at doing it and is probably successful unless my previous questions are of any serious concern. I'm running on Windows Vista Home Basic; if that's of any help.
Thanks for your help and for the great program!
C:\$RECYCLE.BIN\S-1-5-21-748510194-217282370-3783705229-1000\$RD96SV5.tmp\MFT_DIR\0\1\1\3\2 did not have its cluster tips erased because of the following error: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
C:\$RECYCLE.BIN\S-1-5-21-748510194-217282370-3783705229-1000\$RS08PRZ.tmp\MFT_DIR\0\0\2\4\5 did not have its cluster tips erased because of the following error: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
C:\Boot did not have its cluster tips erased because of the following error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects\SystemIndex\SystemIndex.Ntfy21.gthr did not have its cluster tips erased. The error returned was: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
C:\Users\AppData\Local\Temp\IswTmp\Logs\FFApi.swl did not have its cluster tips erased. The error returned was: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
These are some samples of the errors I receive. Are these errors of any importance? If so, what would you recommend in order to solve them? The recycle bin errors have me curious.
Another question I have is that I'm wondering if when Eraser ends with the disk space error and I have to manually remove the files; is it as effective as if the process had finished completely, besides the MFT problem, is it still effective in terms of overwriting the freespace and the cluster tips, making them irrecoverable?
My third question is in relation to cluster tip failures; are my previous questions in any way related to them? I ask because I've noticed that on other free space wiping programs, it automatically fails when it attempts to wipe file slacks but Eraser at least gives an attempt at doing it and is probably successful unless my previous questions are of any serious concern. I'm running on Windows Vista Home Basic; if that's of any help.
Thanks for your help and for the great program!