You can, but it's more than a warning. VeraCrypt has a signed kernel driver, which has higher requirements. You'll need to boot into a special Windows mode and disable Driver Signature Enforcement.
replyAfaict, you can't disable driver signature enforcement permanently without disabling secure boot.
replySecure boot is an anti-feature in most of the landscape anyway. Sure, if you have a distribution under your control or influence it could theoretically be a benefit. But you need to not be stupid or naive here.
replyYou can also roll you own encryption if you are not stupid and naive. Probably a question of self-reflection.
You also get a huge watermark that says "Test Mode" that takes up the entire screen (not kidding)
replyThree lines of text in 12-point font in the corner which can be covered by a window is hardly “the entire screen.”
replyThey changed it recently.
replyhttps://learn-attachment.microsoft.com/api/attachments/f8eac...
Not the OP you responded too, but what the hell! I have not really used windows in a while but that's absurd. That text is massive just for an unsigned driver.
replywow, didn't know about this, i developed some drivers and had this test mode enabled to debug some aspects of it, but now it is almost unusable with this on screen.
replyThat's the same argument which ends win 90% of screen real estate covered in ads.
replyOkay this is some bullshit.
replyNote that signatures are not revoked retroactively when a certificate is revoked. You can still install previous releases.
replyWith all the bugs and potential security flaws that are there and not fixable.
replyI don't know what to tell you, man. If you don't want bugs then don't use computers.
reply