I have a Quantum Byte mini pc running win pro with the latest OS (updated today)  I created a rescue media usb today and when trying to verify that the usb rescue drive was ok, the PC no longer would boot. Upon investigation, The windows boot manager is no longer available to select in the BIOS manager. The only thing that happens when power is applied is there is a shell prompt. The rescue USB is also not option that is selectable in the BIOS boot menu ( the rescue usb drive does not show up at all). The manufacturer said I needed to start over and reformat the drive. Is there a second approach that does not involve reinstalling everything on that PC. The Quantum PC is a runs a 16 bit UEIF. When I created the usb i indicated i wanted to include boot drivers.
Any thougght on how to be this thing to bbot?

Creating a Rescue Media flash drive doesn’t change anything about how your PC boots under normal circumstances. Did you maybe select Windows Boot Menu as the build target at one point? If so, THAT will alter the Windows Boot Manager configuration on your actual hard drive, but that’s supposed to give you a menu allowing you to choose to boot Windows normally or boot into Rescue from files cached on your internal drive. Maybe something went wrong with that process? Although even if that’s what happened, this is the first report I’ve seen of an issue like this. But if you can get your Rescue Media flash drive to boot, you may be able to use the Fix Boot Problems wizard to fix this. In terms of making that happen, if you have a UEFI system, instead of looking for your flash drive in the BIOS Setup, press whatever key activates the one-time boot menu. Some UEFI systems only list “registered” bootloader paths in the BIOS Setup, and temporarily attached flash drives wouldn’t be registered into the firmware the way OSes installed onto internal storage are. (That said, I’m not sure how Windows Boot Manager would be missing. Even if Rescue Media Builder’s change to the Windows BCD didn’t go the way it should have, that shouldn’t have removed Windows Boot Manager from the firmware entirely.)

I did not change any of the defaults during the rescue media creation process, other than I checked the box a "check for devices missing driver during boot" and  selected the windows RE type of rescue media to create. The version of RE was updated and the process seemed to go smoothly and completed successfully. I have never tried to verifying the drive in the past so I thought I would give it a try. Bad decision.I will hunt around to see/find out if the BIOS will support the boot once process. I'll report back tomorrow

You may want to check if your BIOS has switched itself from UEFI to Legacy or UEFI+Legacy. I've had a lot of issues with booting that came down to Windows somehow switching my BIOS over to support legacy and then not booting. Once I found where to change the setting in the BIOS back to UEFI only everything started booting properly again.

+x

 

stubbie - 17 August 2020 7:41 AM

You may want to check if your BIOS has switched itself from UEFI to Legacy or UEFI+Legacy. I've had a lot of issues with booting that came down to Windows somehow switching my BIOS over to support legacy and then not booting. Once I found where to change the setting in the BIOS back to UEFI only everything started booting properly again.

great, I'll check that out, But after way too much time and consulting with the manufacturer, I'm going to chalk this up to a hardware issue. Just weird timing  it happened when i was testing the macrium rescue drive, but bad things happen all the time
thanks for the help