System Encryption Pretest failure
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
When initiating the pretest I inuitially received an error message:
Access is denied
Source: VeraCrypt::File::Write:694
I rebooted the computer and tried again and received a different error message:
Access was denied by the operating system.
Source: VeraCrypt::Elevator::ReadWriteFile:174
In both cases I was logged into Windows 10 as administrator.
Second error message
My feeling is that the root cause of this is the same as what you were experiencing before. Before, VeraCrypt couldn't access the backup boot loader in C:\ProgramData\VeraCrypt. Without a full stack trace I can't see if those are the files that VeraCrypt is now showing access-denied errors on, but it may be so.
So the first thing I would do is look at the directory C:\ProgramData\VeraCrypt and check out its permissions. Look at its Advanced Security Settings and check out the owner and effective permissions for yourself, the administrator user and the administrators group.
Failing that, then I am at a bit of a loss. Without a full stack trace I can't tell exactly where in the setup process the error is coming from, so I can't tell exactly what object is triggering it. In this, VeraCrypt's error messages are lacking. They give the exact source location where the error happened, but, as you see, it doesn't tell you what it was trying to write to when the error occured.
Do you have an anti-virus with some sort of monitor that prevents certain things? Or, on the other end of the spectrum, there is some malware I've seen that puts in a root kit that tries to protect itself by preventing writes to places like EFI partitions, boot blocks and so forth. That's a bit far in left field, but in the range of possibilities here.
If none of this triggers ideas, then I would attempt to use VeraCrypt in a non-system-encryption capacity to see if you run into this issue elsewhere. Start with creating an encrypted file container, and move up to an encrypted non-system partition (even a USB stick here will do). I'd be interested to see if you have any issues with VeraCrypt using elevated privileges the an encrypted non-system partition.