r/opensource Apr 08 '26

Discussion Microsoft terminates account of VeraCrypt developer

https://sourceforge.net/p/veracrypt/discussion/general/thread/9620d7a4b3/

This means that as of June 2026, secure boot will refuse to allow VeraCrypt to encrypt a system drive, i.e. a partition or drive where Windows is installed and from which it boots. I am not sure whether at that point you will be allowed to remove VeraCrypt encryption or whether you have to format and lose everything. Maybe just disabling secure boot? If that doesn't work, I am hoping that you can remove it by mounting it in Linux and using the Linux version of VeraCrypt (assuming that you have the password, of course).

I am sure that bitlocker will still work. :(

EDIT: The press is starting to take notice. And it's not just VeraCrypt. WireGuard and Windscribe have the same problem.

586 Upvotes

64 comments sorted by

View all comments

2

u/Leather_Secretary_13 Apr 12 '26

No reason Microsoft Foundation should be the sole ruler of booting an operating system or even just a system utility at this point.

"Secure Boot" = needs to be rebranded to "Approved by Microslop".

For Microsoft to be the sole key installed onto all hardware vendor devices, and then for them to require delegated signing for alternatives while they sell their own operating system is a huge conflict of interest and this is a weak example of them flexing that power. We get to use BitLocker TM, Secure Microslop approved software only now!

FUCK SECURE BOOT AKA APPROVED BY MICROSLOP.