Forums Bugs & issues invalid distance code

This topic contains 3 replies, has 2 voices, and was last updated by  Deniyalraja V 2 weeks, 3 days ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #14653 Reply

    Henry Liao

    One of my files suddenly had this error:  “[inflating: invalid distance code]”

    I upgraded to the latest Windows version 2.1.1585.0 but the error persisted.  I tried decoding to recover partial data but the temporary file is deleted as soon as this error is encountered.  I found another reference to this error in the forum but the suggested actions there (turn on debug) doesn’t exist in my version.  Any thoughts?

     

    #14658 Reply

    Deniyalraja V
    Moderator

    Hello Henry Liao,

    The error message indicates that the file simply is not an AxCrypt file – it checks the first 16 bytes for a unique value.

    Most often, this error occurs because the file is not produced by AxCrypt, but rather a different kind of file accidentally renamed to end with .axx.

    Another scenario is that it is a left-over after a previous decryption was interrupted at the stage where the original is overwritten. The most common reason for this happening is that the file was damaged because of early removal of a USB drive, or a disconnected network drive.

    If the file is actually damaged to this extent, no, it can’t be fixed. The data is just not there to decrypt it.

    But we have a feature called Check File. You can able to decrypt the corrupted AxCrypt encrypted files by navigating the menu File | Options | enable Debug from the AxCrypt app.

    Also we can generate a summary of file structure, to see whether the file was encrypted with AxCrypt or not.

    For the summary, you have to use the debug menu and then select the Check File menu option(Debug | Check File). Now you will be prompted to choose the files. Choose the AxCrypt encrypted file. Then AxCrypt will generate a summary of file structure.

    Just take a screenshot of the summary and send to us, to investigate the file status.

     

    #14659 Reply

    Henry Liao

    #14665 Reply

    Deniyalraja V
    Moderator

    Hello Henry Liao,

    If the file is actually damaged to this extent, no, it can’t be fixed. The data is just not there to decrypt it.

    But we have a feature called Try Broken File. You can able to decrypt the corrupted AxCrypt encrypted files by navigating the menu File | Options | enable Debug from the AxCrypt app.

    Now you can able to see the Debug the menu in the AxCrypt app. From the debug menu you have to select Try Broken File.

    Now you will be prompted for file selection. Select the corrupted encrypted file and then AxCrypt will try to decrypt the file. If successfully decrypted, then you can able to see the decrypted file in the location. Otherwise, AxCrypt can’t able to decrypt.

    After doing try broken file also, you are getting the same exception, then the file might be corrupted. Sorry to say, you can’t decrypt the same.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: invalid distance code
Your information: