Cumulative June Update Corrupted BCD on SSD. Any fix?

Railtech said:

Your attachment of the USB drive did the trick as that device has both UEFI and non-UEFI boot loader files. This triggered the MBR boot to become available. My guess is the update should have restarted even though you selected update and shutdown because restart was required. Because that did not happen it left your PC boot applications in an unstable state and they defaulted to UEFI boot which resulted in your troubles.

Yes, but I tried using the USB Drive last night and didn’t have the non-UEFI option. That’s the part that stumps me. Not that I am complaining! :)

- - - Updated - - -

Well it’s broken again but in a new way this time. I get a black screen with a flashing underscore in the top left on boot, and if I go into the BIOS and try to boot from the recovery media the same thing happens. I can’t even get into the recovery menu anymore. In booting from the USB I will eventually get the Windows logo on the screen for a split second and then after another few minutes the screen goes black.

- - - Updated - - -

Okay, so I fixed it a second time. I had to turn off UEFI in the motherboard and set boot to “legacy only” because it kept reading the USB drive as UEFI. How do I make sure that doesn’t happen again

- - - Updated - - -

Okay, I’ve isolated the problem now, and it’s a weird one. For some reason, the computer believes that my new USB Audio Interface (Audient iD4 mkii) is a boot drive. When I have this plugged in and try to boot the computer up, the computer gives me a black screen with a flashing underscore for a few minutes before it tells me that there is data missing from the boot media. When I unplug the interface, the computer fires right up.

In the BIOS, the only drive in the boot order is the SSD, as far as I can tell. So… ???

@obesechess,

Sorry for delay in getting back here, life got in the way.

UEFI bios use firmware stored in NVRAM to store setup configuration and boot information for both UEFI and non-UEFI booting.
You might be able to remove this USB audio interface from the UEFI and prevent your issue. Before you attempt that though, did you install drivers for this device or did you just let Windows install drivers for you? If the latter Windows update may have decided that your device was a mass storage device and therefore boot capable. If that sounds like you then removing the device boot entry from UEFI should work but you should first install the OEM drivers for the device. Installing the correct drivers will likely fix the issue for you without mucking around in UEFI.

@Railtech - that's the weird part. I have UEFI disabled in the BIOS and I have all boot options in the BIOS disabled except for my SSD with my current build of Windows. I don't even see the interface in the BIOS. I downloaded the drivers from the manufacturer directly and have made sure they are current. Their customer support is completely stumped. Once I boot the computer up and plug the interface in, it works flawlessly.

Okay, as I said a UEFI bios stores ALL boot info in NVRAM regardless if UEFI is enabled or not so your situation is not weird at all.

Run the following command from an elevated command prompt and post the results here.

bcdedit \enum firmware