cppcryptfs: all versions and old releases

This release adds a native ARM64 build.
This release requires Dokany 2.3.x. It will not work with Dokany 1.x.
https://github.com/dokan-dev/dokany/releases
There is no installation program for cppcryptfs. Just save it somewhere (could be on your desktop) and run it from there.
The executables are signed by the developer and are for 32/64-bit Windows 7 and higher.
The 64-bit x64 version (cppcryptfs.exe) requires 64-bit Windows. The 32-bit x86 version (cppcryptfs_32.exe) will run on either 32 or 64-bit Windows, but it is recommended to use the 64-bit version of cppcryptfs on 64-bit Windows. The ARM64 version (cppcryptfs_arm64.exe) requires 64-bit Windows and an ARM processor.
You can rename the 32-bit version or the ARM64 version to cppcryptfs.exe after downloading it if you wish.
The binaries are signed with the developer's Open Source Developer code-signing certificate. Unfortunately, unless software signed with this type of certificate is really popular and downloaded a lot, Microsoft still treats it with suspicion and will probably throw up a warning dialog when you try to run it. If you click "More Info" and then "Run Anyway", it will run. This warning will not happen on subsequent runs.
Alt text

This release adds a translation of the GUI into Chinese Simplified by @yfdyh000.
This release requires Dokany 2.3.x. It will not work with Dokany 1.x.
https://github.com/dokan-dev/dokany/releases
There is no installation program for cppcryptfs. Just save it somewhere (could be on your desktop) and run it from there.
The executables are signed by the developer and are for 32/64-bit Windows 7 and higher.
The 64-bit version (cppcryptfs.exe) requires 64-bit Windows. The 32-bit version (cppcryptfs32.exe) will run on either 32 or 64-bit Windows, but it is recommended to use the 64-bit version of cppcryptfs on 64-bit Windows.
You can rename the 32-bit version to cppcryptfs.exe after downloading it if you wish.
The binaries are signed with the developer's Open Source Developer code-signing certificate. Unfortunately, unless software signed with this type of certificate is really popular and downloaded a lot, Microsoft still treats it with suspicion and will probably throw up a warning dialog when you try to run it. If you click "More Info" and then "Run Anyway", it will run. This warning will not happen on subsequent runs.
Alt text

This release includes localization work and a Russian translation of the UI contributed by @nbb1967. Supporting a new language now involves only making a copy of a .rc2 file and translating the UI strings in it. Others are encouraged to contribute new translations.
This release also contains a fix by @monkberry71 for removing an erroneous Raw64 setting that was being added to config files if a filesystem with Plaintext filenames was being created.
This release requires Dokany 2.3.x. It will not work with Dokany 1.x.
https://github.com/dokan-dev/dokany/releases
There is no installation program for cppcryptfs. Just save it somewhere (could be on your desktop) and run it from there.
The executables are signed by the developer and are for 32/64-bit Windows 7 and higher.
The 64-bit version (cppcryptfs.exe) requires 64-bit Windows. The 32-bit version (cppcryptfs32.exe) will run on either 32 or 64-bit Windows, but it is recommended to use the 64-bit version of cppcryptfs on 64-bit Windows.
You can rename the 32-bit version to cppcryptfs.exe after downloading it if you wish.
The binaries are signed with the developer's Open Source Developer code-signing certificate. Unfortunately, unless software signed with this type of certificate is really popular and downloaded a lot, Microsoft still treats it with suspicion and will probably throw up a warning dialog when you try to run it. If you click "More Info" and then "Run Anyway", it will run. This warning will not happen on subsequent runs.
Alt text

This release was built with Visual Studio 2026. Previously VS 2022 was used. There were no code changes.
Also, the Dokany it was built with was updated to the latest version 2.3.1.1000.
This release requires Dokany 2.3.x. It will not work with Dokany 1.x.
https://github.com/dokan-dev/dokany/releases
There is no installation program for cppcryptfs. Just save it somewhere (could be on your desktop) and run it from there.
The executables are signed by the developer and are for 32/64-bit Windows 7 and higher.
The 64-bit version (cppcryptfs.exe) requires 64-bit Windows. The 32-bit version (cppcryptfs32.exe) will run on either 32 or 64-bit Windows, but it is recommended to use the 64-bit version of cppcryptfs on 64-bit Windows.
You can rename the 32-bit version to cppcryptfs.exe after downloading it if you wish.
The binaries are signed with the developer's Open Source Developer code-signing certificate. Unfortunately, unless software signed with this type of certificate is really popular and downloaded a lot, Microsoft still treats it with suspicion and will probably throw up a warning dialog when you try to run it. If you click "More Info" and then "Run Anyway", it will run. This warning will not happen on subsequent runs.
Alt text

This release is mainly to fix a bug where cppcrytfsctl was not displaying Unicode characters (issue #206).
Also, Dokany has been updated to the latest version 2.3.0.1000.
This release requires Dokany 2.2.x. It will not work with Dokany 1.x.
https://github.com/dokan-dev/dokany/releases
There is no installation program for cppcryptfs. Just save it somewhere (could be on your desktop) and run it from there.
The executables are signed by the developer and are for 32/64-bit Windows 7 and higher.
The 64-bit version (cppcryptfs.exe) requires 64-bit Windows. The 32-bit version (cppcryptfs32.exe) will run on either 32 or 64-bit Windows, but it is recommended to use the 64-bit version of cppcryptfs on 64-bit Windows.
You can rename the 32-bit version to cppcryptfs.exe after downloading it if you wish.
The binaries are signed with the developer's Open Source Developer code-signing certificate. Unfortunately, unless software signed with this type of certificate is really popular and downloaded a lot, Microsoft still treats it with suspicion and will probably throw up a warning dialog when you try to run it. If you click "More Info" and then "Run Anyway", it will run. This warning will not happen on subsequent runs.
Alt text

This release is for fixing issue #191.
This release requires Dokany 2.2.x. It will not work with Dokany 1.x.
https://github.com/dokan-dev/dokany/releases
There is no installation program for cppcryptfs. Just save it somewhere (could be on your desktop) and run it from there.
The executables are signed by the developer and are for 32/64-bit Windows 7 and higher.
The 64-bit version (cppcryptfs.exe) requires 64-bit Windows. The 32-bit version (cppcryptfs32.exe) will run on either 32 or 64-bit Windows, but it is recommended to use the 64-bit version of cppcryptfs on 64-bit Windows.
You can rename the 32-bit version to cppcryptfs.exe after downloading it if you wish.
The binaries are signed with the developer's Open Source Developer code-signing certificate. Unfortunately, unless software signed with this type of certificate is really popular and downloaded a lot, Microsoft still treats it with suspicion and will probably throw up a warning dialog when you try to run it. If you click "More Info" and then "Run Anyway", it will run. This warning will not happen on subsequent runs.
Alt text

There are no changes other than using a newer Dokany version (2.2.0.1000).

This release requires Dokany 2.2.x. It will not work with Dokany 1.x.

There is no installation program for cppcryptfs. Just save it somewhere (could be on your desktop) and run it from there.

The executables are signed by the developer and are for 32/64-bit Windows 7 and higher.

The 64-bit version (cppcryptfs.exe) requires 64-bit Windows. The 32-bit version (cppcryptfs32.exe) will run on either
32 or 64-bit Windows, but it is recommended to use the 64-bit version of cppcryptfs on 64-bit Windows.

You can rename the 32-bit version to cppcryptfs.exe after downloading it if you wish.