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.

▲

HauntingPin 9 hours ago | parent | next [-]

Afaict, you can't disable driver signature enforcement permanently without disabling secure boot.

▲

nslsm 8 hours ago | parent | next [-]

You also get a huge watermark that says "Test Mode" that takes up the entire screen (not kidding)

▲

DHowett 4 hours ago | parent [-]

Three lines of text in 12-point font in the corner which can be covered by a window is hardly “the entire screen.”

	▲	nslsm 4 hours ago \| parent [-]
		They changed it recently. https://learn-attachment.microsoft.com/api/attachments/f8eac...

▲

raxxorraxor 8 hours ago | parent | prev [-]

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.

▲

fluoridation 6 hours ago | parent | prev [-]

Note that signatures are not revoked retroactively when a certificate is revoked. You can still install previous releases.

▲

bluGill 6 hours ago | parent [-]

With all the bugs and potential security flaws that are there and not fixable.

	▲	fluoridation 5 hours ago \| parent [-]
		I don't know what to tell you, man. If you don't want bugs then don't use computers.