Sorry to hear that. So, you’re saying the file in question resides on a local fixed hard drive? It’s pretty much unheard of that an AxCrypt file would be damaged like it appears to have been on a fixed drive.
Did something unusual happen in the vicinity of the last update of the file? Perhaps a forced reboot by Windows, a power outage, a crash or anything unexpected that could cause a file not to be completely written to disk by AxCrypt?