siro

I use normally use veracrypt portable to load an encrypted file as a drive. After recently updating the portable binaries, veracrypt agent wouldn't load, claiming I have an older driver running (which I didn't). After mucking about in the directory, I directly double clicked the driver .inf file (stupidly thinking 'oh that will update the driver'). It asked to reboot, which I did, and now I'm in a boot loop. I did not encrypt my latop hdd. I do not see \EFI\VeraCrypt when mucking around the boot...

I use normally use veracrypt portable to load an encrypted file as a drive. After recently updating the portable binaries, veracrypt agent wouldn't load, claiming I have an older driver running (which I didn't). After mucking about in the directory, I directly double clicked the driver .inf file (stupidly thinking 'oh that will update the driver'). It asked to reboot, which I did, and now I'm in a boot loop. Apparently the driver mucked around with my bootloaning files, which I'm not sure how to...