Messages 001 to 010

The destination was not completely decrypted because some encryption data is missing.

Disk Recoup™ could not access the Windows® registry because of what could be an internal Windows® error.

There is no more computer memory for the program to continue. Use the Windows® Task Manager to determine if Windows® has used up all available memory. Close unnecessary applications to free up more memory.

The sector could not be decrypted because the encryption data is missing.

The sectors could not be decrypted because the encryption data is missing.

Disk Recoup™ is hung and must be restarted. The computer may need to be rebooted. See "Time and patience"

The specified device could not be found. This can happen when you resume a copy operation and the original source hard drive is not found. The drive may have been physically disconnected from the computer or it may have gone offline due to hardware errors.

A low-level disk read operation failed. This error is typical when reading a faulty hard drive. The program should continue to copy other parts of the disk.

The specified session file lacks a required verb-value pair. The file may be corrupt or was created by an older version of Disk Recoup™. A session file has the extension "drs".

Disk Recoup™ will stop if too many errors are generated in a short time interval. This measure it to prevent the program from going into an "infinite loop", generating excessive errors that may severely affect Windows®.