Doug

Thanks again, Mounir. I can confirm that the changes worked for me as well.

Thanks Mounir!

Following up further. I did the following: On new and up-to-date Windows 11 23H2 virtual machine, I installed latest version 1.26.14 and then encrypted the system. After encryption I rebooted and then after logging back in, I installed, "upgraded", to previous version 1.26.7. In other words I downgraded the system. Finally, after rebooting, I initiated decryption of the system. Unlike when I initiated decryption with version 1.26.14, version 1.26.7 does what is expected and desired and actually decrypts...

After choosing to permanently decrypt the system partition/drive in a VM where I am testing the new release and proceeding through the encryption process and reaching 100%. I receive the following error dialog (screenshot attached) that says "Failed to set SE_SYSTEM_ENVIRONMENT_NAME privilege (error code Source: VeraCrypt::EfiBoot::DeleteStartExec:2650" I then clicked OK and then waited but I noticed that instead of a Pause button displaying, there was a Resume button, even though the decryption...

After choosing to permanently decrypt the system partition/drive in a VM where I am testing the new release and proceeding through the encryption process and reaching 100%. I receive the following error dialog (screenshot attached) that says "Failed to set SE_SYSTEM_ENVIRONMENT_NAME privilege (error code Source: VeraCrypt::EfiBoot::DeleteStartExec:2650" I then clicked OK and then waited but I noticed that instead of a Pause button displaying, there was a Resume button, even though the decryption...

Are there plans to update the VeraCrypt EFI bootloader to work with the new ARM-based PCs that hit the market this summer? I know I am starting to see people I work with buy these and at the moment I don't know what to advise them in terms of a good system encryption option. I would love though for VeraCrypt to be their option of choice. Thanks!

I used to have AuthorizeRetry set to 0 and this would not allow any retries of the password but I noticed with the most recent release of VeraCrypt 1.26.7 that the setting appears to be completely ignored. I have changed the value as follows 0, 1, 10 and the number of tries is always 4 before it will no longer allow attempts. I don't see any change in the code and it looks like the code does try to take into account this setting so I am at a loss as to what is happening. I have seen this both on...

Okay. I connected in using TeamViewer to the user's computer this morning. I'm not sure if the actual issue was whether my colleague was not specifying a PIM or if it was the fact that I used the backup header to mount but I did successfully get it mounted and I having the user backup all his data before I do anything else. By the way, it was VeraCrypt 1.23 and the error that I got (at least until corrected the PIM) was "MountVolume: 8299". Anyway, I think this issue is resolved now. Thanks for the...