Niles Patchernek - 2025-08-14

Current situation
I can't find any information about why the pretest failed:

My scenario

  • I'm trying to get VeraCrypt 1.26.26 working inside a Virtual Machine (Generation 2, GPT, Secure Boot disabled) using Hyper-V.
  • Authentication during the boot process works without any problems.
  • Windows 11 24H2 boots up without any problems.
  • The pretest failed.
  • I made sure the disk sector size was set to 512.

Feature request
Please write the exact reason why VeraCrypt thinks that the pretest failed. You can either write it in the dialog or in a log file.
I have no idea if the problem is on my end. If the current VeraCrypt implementation doesn't support this scenario, then maybe an error message with more specific information could help with finding a solution.