Update Portable Version

[Mario Scotto]

I' m running VC Portable version 1.26.7 - I want to update to last version e.g. 1.26.20.
Are there differences between updating installed versions and this case?

[Enigma2Illusion]

For portable mode or PC installed VeraCrypt software, I would unmount any VC volumes.

I would assume for portable you merely extract or setup a new Traveler Disk using 1.26.20 version.

https://www.veracrypt.fr/en/Portable%20Mode.html

[Peter A Makris]

Very new to VC.
I'm running portable 1.26.14.
Downloaded 1.26.24 and extracted.
These files are missing: veracrypt.exe, format.exe, cat, sys, expander.exe.

Veracrypt.exe missing is causing the major problem as it is imbedded in a bunch of .bat files.
Any help would be appreciated.

[Gary Marks]

If you were using "veracrypt.exe" in your batch files, you were running the 32-bit executable. If you have a 64-bit capable system and don't want to change your batch files, you should be able to rename "VeraCrypt-x64.exe" of v1.26.20 (or later versions) to "VeraCrypt.exe" as a workable solution until you get around to changing your batch files. It won't affect how it runs internally, and it will still be programmed to call the other files correctly as needed. Don't rename any of the other files, just the main executable.

On the other hand, if you are still running 32-bit Windows. the latest version of VeraCrypt you can use is v1.26.15, as 32-bit support has since been retired.

[Peter A Makris]

Thanks, Gary!
You info worked perfectly.

Just a little curious: now that you let me know that I had been using the 32-bit version (in a 64-bit Windows environment), is there any issue with using the previous containers in 64-bit?

Thanks again for your timely help. I will follow up with your suggestion to update the batch files with the -x64 name. Regards, Pete.

[Gary Marks]

Hi Pete,

I may have been a bit hasty in suggesting you change your batch files to match the different name for the 64-bit VeraCrypt file. If a single change of the VeraCrypt executable filename makes everything work right, that certainly seems less error prone than changing multiple batch files. Plus, I use the installed version rather than the portable, and I just noticed that the installer names the main executable as "VeraCrypt.exe", but it is byte-for-byte identical to the "VeraCrypt-x64.exe" extracted by the portable version. So your singular act of renaming the executable seems like a sufficiently permanent solution unless there's something I'm missing.

As for compatibility between containers encrypted with 32-bit and 64-bit versions of VeraCrypt, there's no issues I've heard of, and containers are portable even to Mac and Linux machines as long as the internal file formatting is supported on both computers.