Decryption fails? - Not Integrity Protected

[Tech Support]

Apr 30, 2020, 4:34:20 PM gpg: WARNING: message was not integrity protected
Apr 30, 2020, 4:34:20 PM gpg: decryption forced to fail!
Apr 30, 2020, 4:34:20 PM gpg: encrypted with ELG key, ID 5DA941FA92F890DD
gpg: encrypted with 2048-bit ELG key, ID BDxxxxxxx85, created 2009-08-26
"xyz@test.com>"
gpg: WARNING: message was not integrity protected
gpg: decryption forced to fail!

The file is decrypted successfully. The original file is archived successfully. But that error makes the job look as unfinished, so the option to delete the source file after completion fails.
Then the next run tries to reprocess the same file because it was never deleted and we are getting duplicate files.

[Tech Support]

1) This error is because encryption was done with an older key that did not support integrity protection. This causes the encrypted file to be less secure. Newer Automize\AutoKrypt versions uses GPG 2.x which flags this error. Older versions used GPG 1.x which allowed this.
2) The correct solution is to use a newer key to encrypt the files.
3) Unfortunately, there is nothing that can be done currently in the decryption task to fix this.
4) If decryption task exit code > 0, you can use a delete task separately to delete these files which were not deleted, or move them to another folder using a copy task.