This sort of sounds like some type of virus might be involved. A couple of years ago I had one that changed the name of one of the boot files and stopped the system from booting. That was before Windows 8 but if you gave something permission, it might have been able to change something.
I'm not saying that it's not possible that I have a virus, but I am a bit OCD about it, so it's unlikely since I run regular daily scans, deep weekly scans, and am very careful about what I do on the internet.
Did you check and make sure a Windows Boot Manger entry was the primary boot device in the bios? If it is trying to boot directly to the hard drive, it will not fine an OS.
I am not sure how to do this...can you please tell me how?
Not really a good assumption since the Drive number is basically set by the connection to the Motherboard. The Drive priority is set in the bios, and the OS could be on either one, but probably not the empty one, if it is empty. If as drive shows as uninitialized, something has been removed from the drive's configuration data and Windows cannot read it. It may not be empty, so be careful. As an example, a drive cleaned with diskpart will show as uninitialized and the following is what Diskpart will do to a GPT configured drive.
This makes me feel a bit better and I'll tell you that I am trying to be very cautious because I do not want to do more damage and risk losing anything more. I believe that I haven't done any troubleshooting that would change anything (only looking for information to help so far).
I will have to do some research to see if there might be a way to recovery data from an uninitialized drive. There may be some third party utilities which would recreate the drives configuration, but I am not aware of one right now.
As far as the original thread and the locked drive message, I have not seen that and do not know of specifics circumstances involved in such an event.