The shell is to UEFI what DOS is to legacy BIOS. When you start it normally a list of mappings are generated and asks if you want to run the nsh file which is the equivalent of .bat in DOS. Unless you put something in there it's usually not there so just gets ignored anyway if you haven't pressed esc in time.
In the BIOS set usb legacy support and enable CSM if not enabled already. For good measure you can disable C-States but shouldn't be necessary. Plug in your Windows DVD and boot but use the BBS key to select the device. The Bios Boot Selection key on my Asrock is F11, you might need to check your manual for yours. There should be 2 options for your DVD, one with UEFI: prefix and one without. Select UEFI:XXX. Note the DVD takes a long time to boot so be patient. If you are still not getting to the installation screen with repair option you could try downloading W10 to bootable USB with the Windows media maker and try that.
https://support.microsoft.com/en-au/help/15088/windows-create-installation-media
Shell is to UEFI what DOS is to Legacy BIOS....
Perfect analogy. I understand this totally now
I still have an old 486 machine because of how much I loved those days.
USB Legacy support is and has been enabled. I have tried both enabled and disabled though.
I have also tried booting to the Windows DVD.
For my board it is also F11 to enter the boot selection menu.
I selected the UEFI option of my ODD.
As soon as the dots start spinning, a few seconds later, they stop and the computer hangs the same way it does when it attempts to boot the OS drive, or the Win 10 USB.
Whatever it's trying to do at that moment is the issue it seems, because when I attempt booting to Acronis USB or CD, they both hang after "Loading drivers..._" shows up and I bet it's trying to do the same thing at that moment that makes it hang.
Yeah, what
@Dufus said. Make sure 'Fast Boot' is disabled, if it's enabled.
Fast boot is disabled.
Although I have tried the Fast option before.
I vote critical BIOS option setting was cleared/reset/modified on flash and has overlooked. Double check all BIOS settings. He fact that you can neither boot your ODD nor your NVMe tells me it's a setup issue and likely not a hardware issue or OS corruption problem.
That's what I'd think too, however note that this happened before any bios change was made.
It literally happened after I booted to the shell from the USB stick... then restarted to go into the bios in order to reset/default it and then flash the modded bios.
But instead of going into the bios, I decided to just try to reboot the computer normally after it booted to the shell because all of the text that came up kind of freaked me out and I didn't know what was going on. I wanted to make sure the computer was still fine.
After looking at the printed instructions again, I realized all the shell text was normal... but then I looked up and saw that my spinning dots weren't moving (windows loading).
It's only then that I started troubleshooting everything... flashing modded bios, flashing old bios, flashing factory new bios, going into shell with modded bios and attempting the mod, unplugging hard drives, odd, usb, disabling cores, swapping ram sticks, etc...
It's a really odd set of circumstances and timing that leads me to believe it may be the bios chip.
But i surely won't be surprised if my memory for some reason is playing tricks on me and I may have changed something beforehand that screwed something up.