Why is VC messing with Windows EFI?
@Bootrec Why is VeraCrypt messing around with the Windows EFI folder? On installation, VeraCrypt is installing its own EFI boot folder. This is, of course, fine and to be expected. What is not to be expected is the fact that VeraCrypt isn't just installing its own EFI folder but reaching into other EFI /fixboot access is denied folders to put its bootloader in them too. It is going into the Windows EFI folder, renaming the old Windows EFI bootloader, and then putting its own bootloader in the Windows EFI folder.