A few months ago, I bought a 500GB sata SSD to replace my 128 GB NVME SSD so that I could have larger storage for my windows drive without having to constantly make space in the 128. The 128 was my old boot drive, and the goal was the make the 500 the new boot drive. I duplicated the 128 to the 500, changed the boot priority in bios, and started my PC. It worked without any troubles. So for the past few months, I did not touch any data on the 128 just in case there was a problem with the new boot drive and I needed to revert to the original 128 as the boot drive. Keep in mind, both drives are essentially a duplicate copy, one just has more space, so they both should boot into Windows. The few months went by without any problems, so I decided to finally wipe the old 128 to make space for more video games for faster load times. I did this through the windows cmd prompt (followed a guide online), and it worked fine. I was able to transfer files on to the newly wiped 128, and windows was still running correctly. The only problems were a few programs were still referencing the old 128 as their install folder, so I just had to change the directory from the 128 to the 500 and all was fine. I shut down my pc for the night.
Here is when my problems arise. I launch my pc today and get the error BSOD "Recovery, Your pc needs to be repaired, a required device isn't connected or can't be accessed, error code 0xc000000e" then shuts down after a minute of being on that screen. Pressing F1 for the recovery environment does not work, the same with F8 for startup settings.
I used my alternate laptop to create a recovery USB device and was able to bring up the recovery options screen.
I tried the automatic startup repair: "Startup repair couldn't repair your pc"
Then I tried some command prompt guides:
bootrec /scanos works successfully
bootrec /fixmbr works successfully
bootrec /fixboot access denied
Okay, so I try looking up how to fix access denied and found this guide https://www.makeuseof.com/bootrec-fixboot-access-denied-windows/
I try and follow it, but I notice some differences from their screenshots of the volume list compared to mine. My volume 0, Ltr D, has windows on it. But the label is blank, and the info is blank. Compared to their screenshot, their label says Windows and info is Boot.
I tried to follow the guide to fix the /fixboot problem, but run into a problem in step 24 for the command "bcdboot C:\windows /s V: /f UEFI" where the command is unable to be ran. I think this does not work because my labels of my volumes is wrong and my pc does not recognize the bootable device.
So the problem at this point is: I have windows installed, /scanos is showing that I have Windows installed on a drive, and my pc recognizes that the drive is connected and working. It just seems that there is no communication to the pc that the windows drive should be the boot drive and there is just some error in the boot process.
Not really sure what to do that this point. I probably will install windows back on to the 128 just to be able to use my PC, but I know all other data drives work, and that windows is installed and worked while the other drive was wiped, so the issue is the boot process. I just wanted to avoid reinstalling Windows.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
