Update on bumping minimum Windows version requirements for VeraCrypt
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
Hi everyone,
I wanted to address some concerns and feedback I have received privately regarding the recent decision to update the minimum supported version of Windows for VeraCrypt 1.26.17.
First, I want to thank all of you for taking the time to share your thoughts and suggestions. Your input is incredibly valuable and helps guide the development of VeraCrypt.
Based on this feedback, I have implemented a change to lower the minimum supported version of Windows 10 to version 1809 (October 2018 Update). You can view the details of this update here:
https://sourceforge.net/p/veracrypt/code/ci/8dd4d0381dae330598f0240dd9ab813fc6e07dc4/
This adjustment should help accommodate more Windows 10 users while still allowing me to move forward with ongoing development. A new version with this change will be released soon.
The decision to update the minimum requirements was not easy. It was driven by the need to use newer Windows APIs and simplify the Windows driver code. Supporting older Windows versions significantly increases the complexity of maintaining the code, especially when new compatibility issues arise with newer Windows versions. Resolving these challenges often requires changes that break compatibility with older systems.
With limited resources and time, I must prioritize the long-term viability of VeraCrypt while maintaining its quality and security. While I would love to support older operating systems indefinitely, the constraints of time, funding, and complexity make this increasingly difficult.
I hope this post clarifies the situation and provides some insight into the decisions driving this change. I invite you to continue the discussion here so we can keep the conversation open and transparent.
Thank you for your continued support and understanding.
Although Windows 10 version 1607 isn't supported, it's the latest version (I think) to support running Windows 10 on an external hard drive. It's no longer an issue for me, but that version of Windows was significant for me for that reason. But I hope it will be easier for you to update VeraCrypt now,
I know this is 1 year old, but as nobody answered on this part and this is a sticky:
Even Windows 11 can be used on an external Hard Drive. You can - among others - use Rufus to create a "Windows To Go" which is Windows on an external Drive. Microsoft dropped official support, but it is still possible.
However, keep in mind that StandBy may be an issue, likely because the usb driver or the drive itself may be required before it is loaded/repowered. I don't think that "official" Windows To Go did not have such issues on the same hardware.
Last edit: bkjhkjgjjkk4 2026-04-10
I installed the new version 1.26.24 but it gives me the error that veracrypt requires at least Windows 10 version 1809 (October 2018 Update) to run.
I am running windows 10 pro 22H2 installed on 6-17-2020 OS Build 19045-5737
Can I get the older version back until this issue gets worked out. I have attached a screenshot of my version information
Not sure what happened, but here is the screenshot.
@markpiatt
Did you install using the VeraCrypt Setup 1.26.24.exe installer?
Did you disable your AV/Malware software before the install?
Are you using VeraCrypt System Encryption?
After you installed the 1.26.24 version, did you perform the required reboot?
Last edit: Enigma2Illusion 2025-06-08
I am away from the computer. when i get back, I will disable the av software, uninstall veracrypt, and try again.
@markpiatt
Be sure to install using a Windows account that has local Administrator privileges.
https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.26.24/Windows/VeraCrypt%20Setup%201.26.24.exe/download
All versions of VeraCrypt can be found at the link below.
https://sourceforge.net/projects/veracrypt/files/
Last edit: Enigma2Illusion 2025-06-08
@markpiatt
Is your Windows 10 Pro 32-bit OS?
Starting with VeraCrypt 1.26.18 version for Windows:
Hi there
I uninstalled veracrypt rebooted, disabled both the virus scanner and my firewall. reinstalled, rebooted, and I still get the same message. And yes, I am using 64 bit Windows 10 Pro.
Honestly I am not too worried about it since I mainly access the container from linux, but I had it installed on windows kind of as a backup in case my linux goes down for whatever reason. You can see in the screenshot that I do run 64 bit Windows 10 pro.
Hi @markpiatt
Did you install using a Windows Administrator account or an account with local Administrator privileges?
Strange. I am running Windows 10 Pro 64-bit 22H2 OS Build 19045.5854 and I was able to upgrade from 1.26.20 to 1.26.24 without issues.
6/10/2025 is the monthly MS patch day. I install all MS patches each month. Maybe Tuesday's patch will resolve the issue for you.
I am using a windows administrator account. I downgraded back to the version I was running before, which was 1.26.15. I am going to upgrade this computer to windows 11 soon, so thats another reason I am not too worried, plus I can access the containers from ubuntu.
Just for kicks, I tried 1.26.20 earlier and it fails. I need to check what the newest version is I can run, but I can not do it right now, doing some web design work for a client right now.
Last edit: Mark Piatt 2025-06-10
Hi @idrassi
Can you provide guidance to the problem Mark is reporting?
It appears 1.26.15 installs and runs without the error that VeraCrypt requires at least Windows 10 version 1809 (October 2018 Update) to run.
However, when Mark upgrades/installs either 1.26.20 or 1.26.24 causes the error that VeraCrypt requires at least Windows 10 version 1809 (October 2018 Update) to run.
CC: @markpiatt
EDIT: Mark, the issue should be reviewed since this may effect both Windows 10 & 11.
Last edit: Enigma2Illusion 2025-06-10
Ok, just let me know if there is anything I can do to help. I have also attached a screenshot showing I am using a windows administrator account.
Hi @markpiatt
Just to confirm that your Windows 10 OS is the only OS installed on the PC. Correct?
Also, you are not running the Windows 10 OS in a Virtual Machine environment. Correct?
Last edit: Enigma2Illusion 2025-06-10
I have 2 instances of linux running in virtual machines.
Windows is installed directly, not in a virtual machine.
Hi @markpiatt
Given that OS restriction was implemented in the production version 1.26.18 on January 20, 2025, you are the only person to report that their valid OS version is being rejected.
Hence, there is something unique about your environment or applications causing this issue.
I am using Windows 10 Pro 64-bit and I have never experienced the issue you are reporting when I upgraded to 1.26.18, .20 or .24 versions,
Can you think of what might be interfering with VeraCrypt?
Are you using a third party AV/Malware software? Maybe try disabling the software before using VeraCrypt after installation and the required reboot.
Last edit: Enigma2Illusion 2025-06-13
HI,
yeah, its an odd problem that seems to be related to something unique with my system. For the anti-virus I use vipre, but I have disable it along with its firewall and still have the issue. I also use Windowsblinds, which manipulates the Windows UI. I tried disabling that but still did not work. Over the years I have made some modifications to the registry, so maybe something I have done is causing veracrypt to think I am running an older version of windows. It would be interesting to know what version of windows veracrypt things I am running.
Also this Windows Pro was upgraded from Windows home addition, so I do not know if that had an effect.
My system is a busy system with a lot of software. Besides being involved with web design and software related to that, davinci resolve, various picture manipulation softwares, sound software etc, I also have specialized software related to private investigation work.
I am a technical contractor for private investigators. We deal with very sensitive information, That is why we use veracrypt.
Some of our software is windows only and some runs on linux. So for that reason, I run several different virtual machines with linux.
Anyway I was able to downgrade veracrypt to a usable version. If it ever stops working for me, I can use my virtual machines to copy data from the encrypted containers to my windows machine.
The latest version of veracrypt does work on my windows 11 laptop, so worse case scenario, I can open the container on the laptop and access that drive from my main computer.
Thanks for looking into it.
Hi,
I have successfully built all the required files and compiled VeraCrypt. However, when I try to run the resulting .exe file, I receive a message saying that this is a distribution package but the digital signature cannot be verified (genuine/authenticity issue).
I have already installed my certificate under "Trusted Root Certification Authorities" in the Local Machine store. I also updated the SHA-512 fingerprint in the VeraCrypt source code — replacing both gpbSha256CodeSignCertFingerprint and gpbSha256MSCodeSignCertFingerprint arrays with the correct values from my test certificate.
The entire solution was cleaned and rebuilt successfully, but the signature verification issue still persists.
🔧 Environment:
Windows 11
Visual Studio 2022 (Community Edition)
Could you please help me understand why this error still appears, even after updating the certificate and rebuilding the entire project?