When trying to launch veracrypt-x64.exe in a Windows 10 recovery environment, I sometimes get the Application Error shown in the attached pic. It doesn't seem to matter much if VC Portable is incorporated in the recovery environment (i.e., copy the VC Portable folder into the WinRE ISO prior to building the rescue media) of if VC Portable is accessed from a USB flash drive, although the error does seem to be more consistent when trying to run the app when it's embedded in the recovery environment (VC rarely runs ok in this situation). Using a USB stick, if I launch the recovery environment 10 times, VC might run from the USB stick half of those attempts.
Any ideas on what might be causing this or how to test or get around it?
Does this issue happens only with latest 1.24 version or does it happen also with previous version 1.23?
I don't think this issue is caused by VeraCrypt code directly, and maybe it is happening because of external system dll that we load but it is difficult to know without debugging.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
v1.23 works. Tried it two ways in the recovery environment.
1. launch VC portable from USB flash drive
2. launch VC portable that I built into the recovery environment
Thanks for suggestion to try an older version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When trying to launch veracrypt-x64.exe in a Windows 10 recovery environment, I sometimes get the Application Error shown in the attached pic. It doesn't seem to matter much if VC Portable is incorporated in the recovery environment (i.e., copy the VC Portable folder into the WinRE ISO prior to building the rescue media) of if VC Portable is accessed from a USB flash drive, although the error does seem to be more consistent when trying to run the app when it's embedded in the recovery environment (VC rarely runs ok in this situation). Using a USB stick, if I launch the recovery environment 10 times, VC might run from the USB stick half of those attempts.
Any ideas on what might be causing this or how to test or get around it?
Does this issue happens only with latest 1.24 version or does it happen also with previous version 1.23?
I don't think this issue is caused by VeraCrypt code directly, and maybe it is happening because of external system dll that we load but it is difficult to know without debugging.
I was using v1.24, but I'll try v1.23 as well as a few older versions and report back, thanks.
v1.23 works. Tried it two ways in the recovery environment.
1. launch VC portable from USB flash drive
2. launch VC portable that I built into the recovery environment
Thanks for suggestion to try an older version.