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.
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.
Afaict, you can't disable driver signature enforcement permanently without disabling secure boot.
You also get a huge watermark that says "Test Mode" that takes up the entire screen (not kidding)
Three lines of text in 12-point font in the corner which can be covered by a window is hardly “the entire screen.”
They changed it recently.
https://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.
Secure 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.
You can also roll you own encryption if you are not stupid and naive. Probably a question of self-reflection.
Note that signatures are not revoked retroactively when a certificate is revoked. You can still install previous releases.
With all the bugs and potential security flaws that are there and not fixable.
I don't know what to tell you, man. If you don't want bugs then don't use computers.