The Dude

Thanks, John. That's not my exact problem though. I went ahead and decided to start clean by first reformatting the Drive B; I later planned to reformat Drive A. I installed a fresh Windows 10 copy over Drive B. During the install process, Windows 10 rebooted itself. To my pleasant surprise, I was presented with a choice: boot from Drive A or Drive B (the behavior I saw before attempting to encrypt Drive B). Drive A still works. It's a Christmas miracle! I now have both drives working properly, both...

Thanks, John. That's not my exact problem though. I went ahead and decided to start clean by first reformatting the Drive B; I later planned to reformat Drive A. I installed a fresh Windows 10 copy over Drive B. During the install process, Windows 10 rebooted itself. To my pleasant surprise, I was presented with a choice: boot from Drive A or Drive B (the behavior I saw before attempting to encrypt Drive B). Drive A still works. It's a Christmas miracle! I now have both drives working properly, both...

Hey Dictum, it sounds like you had a similar problem to me. https://sourceforge.net/p/veracrypt/discussion/technical/thread/749de49e53/ Reading your post here...are you saying it simply fixed itself miraculously? I'm unclear on how you got the thing to boot.

Oops...I did it again (something stupid with a computer, that is)! I've been caught off guard by recent developments in the tech world. Truly appreciate some assistance here so I can learn what I did wrong. I just built a new machine and was trying to replicate what I successfully did on my old one. Here is my old machine and what I used to do with it: -Gigabyte motherboard (forget exact type...purchased about 2014. I don't think it had UEFI, but I have no idea). -Drive A: Windows 7 on a SATA SSD...