Thank you for the reports. I have receive similar report on Github. This issue seems to be caused by the extra security checks in the installer to fix potential security issue that was reported. The current implementation seems to be too strict compared to the various possible permissions configuration. I analyzing this and trying to reproduce it. Meanwhile, I have removed the Windows installers (exe and MSI) and left only portable setup. Once I have better clarify, I will post an update and share...
Unix: fix encryption thread pool build with GCC 4.4
Windows: Update signed Windows drivers
Prepare VeraCrypt 1.26.30 release notes and resources
Tests: extend XML parser regression coverage
Windows: complete XML persistence fixes
Windows: preserve paths and escaped XML settings
Windows: prevent Unicode corruption in XML settings