Windows 10 Boots To Efi Shell

[Violette Taps]

VMboots to UEFI Interactive Shell instead of the OS. Exiting out of UEFI shell, I can manually boot into Windows via Boot Manager selecting UEFI Samsung SSD drive. In the BIOS I have tried deleting/changing boot device order so only the NVMe drive is in the boot sequence; however, these changes do not persist. Please see attached snapshots.

I'm also having this problem. In my case I'm passing through a PCIE usb controller with a separate unraid USB drive. I can boot from this if I select manually. I can change the boot order and save. "Continue" will boot correctly, but upon restarting the VM it boots back to EFI shell.

Appreciate the feedback - but I had already tried configuring EFI boot using bcfg. Still not persistent. Seems like this is related to passthrough specifically - perhaps because qemu can't see the device when the machine is starting?

What I mean is we're talking about devices passed through to the guest. In my case it's an entire USB controller, so the boot device isn't listed at all in the XML file. In that sense QEMU isn't aware of the boot device when it's starting the VM (even though the guest definitely sees it) Maybe the OVMF settings are being ignored/reset for that reason?

ok, understood, so no disk section in the xml, it's the same as my setup (only sata controller passthrough), not sure what's happening there..maybe you can try to delete ovmf_vars (and maybe ovmf_code) file and replace with fresh ones, sometimes the ovmf_vars caused me some issues that I solved by replacing with a fresh one, then if it still doesn't work, retry with the bcfg command.

I've recreated the VM multiple times, so multiple fresh vars files have shown the issue. Perhaps an alternative OVMF version might help - though messing around with the OVMS paths in my VM XML is what stopped me from starting the unraid VM service yesterday.

I have dumped my video cards bios per spaceinvader videos, i have tried seabios, ovmf, i have edited the XML every which way i can think of and am using the latest windows 10 ISO from microsoft. when using VNC i am able to create a windows 10 VM following spaceinvader instructions and boot into windows successfully, when passingthrough the GPU i get thrown into the UEFI interactive shell and typing exit and trying to boot from the boot manager does not work. I have tried multiple different bios files IOMMU is enabled, HVM is enabled, the card is in its own IOMMU group with the audio part of the card. at this point i have created well over 70+ VMs trying to get this to work can someone please offer some guidance as to what i am doing wrong. attached is the code for my current VM

First, your topology for gpu+audio is wrong, you have video on one bus and audio on another bus, hdmi audio and gpu video should be in the same bus, same slot, but different function (multifunction device).

After fixing this, if it still boots to the uefi shell, press esc multiple times when you boot the vm, see if in the boot options there is your hard drive and if it's not in first position, change its order to the top one.

I installed Windows 11 VM on a passthrough NVME drive and it keeps booting into the UEFI Shell. It seems like @jortan fixed this but I'm not 100% sure I understand the solution. I am pretty new to all of this. Am I having the same issue as you guys and if so what can I do to fix it? Any help would be appreciated!

I'm configuring Windows 7 Professional x64 to run a custom application as the shell, in "kiosk" mode. That is, replacing the default shell (explorer.exe) with my application and autologon as a specific user.

When I power on the machine, I see the BIOS screen, then a black screen (where the Windows logo would have been), then the user logon page flashes by quickly (during autologon), then it sits at a blank screen for several minutes.

The cursor is on screen but inoperable. And I'm fairly certain it's not my application, because when I run it in a regular desktop scenario, it starts very quickly. This is a bad experience for the user that's starting up the kiosk or may be approaching the kiosk after it's been booted, but before the application starts.

Or does anyone have any fancy ideas on tricking the user into thinking the kiosk is operating? (I don't know what else I have control over at this point in Windows kiosk startup... can I splash up a background image instead of the drab geen/blue screen?)

Be sure that there are no mapped drives unreachable from the place of your kiosk is installed. If you map a drive in your lab or test facility and try to access it from a place without network access, the login takes too much time until windows realize that the remote drive is unreachable.

Hello, I have a mini pc, it looks like a HEROBOX, the serial number is VS19057000342

The pc boots in shel version 2.6 mode black screen looks like linux, i cant start in windows, what can i do? maybe a bios flash, I typed exit and enter the bios but there is no option to flash the bios. I look forward to your help.

The bios is 5.13 Version 2.19.1268 (2019) ami. Thank you

Yes, only efi shell, like linux i think, i type exit and enter the bios, i tested options but nothing happens, always boot in efi shell, i tried to put a hdd 2.5 with windows 10 and nothing. if i put a usb with windows installation it boot from the pendrive but freezes. Thanks

"I am not sure if this is the same issue I'm having, but I started up my gaming PC yesterday with Bigbox set as the default shell and it boots to a black screen. No sound, I can see my cursor when I move the touchpad on my keyboard. None of my keyboard inputs, like Ctrl, Shift, Esc to bring up the taskmanager seem to work except Windows + P which brings up the project to screen window. Does anyone know how i can startup explorer.exe and undo the changes Bigbox made to the default shell? "

There is probably a command that I can type to boot from that prompt, but I don't know it. What works is to reboot using Ctrl+Alt+Del, then pressing F12 repeatedly until the normal GRUB menu appears. Using this technique, it always loads the menu. Rebooting without pressing F12 always reboots in command line mode.

If NOT - you have to go through the steps again an might have to repair or install grub again:

Please look at the "Boot-Repair"-tool from this article: -Repair (I had positive experiences with it, when previous steps wouldn't survive the reboot)

This is some funny thing happening to many PC dual booting with Windows 10. Happened to me and friends recently. Please note that I don't know why, I can only speculate this depends on some Windows 10 updates. As someone said, indeed this is due to the boot process not finding the root partition for some reason, so GRUB asks you to tell him where it is via CLI.

I ran into the same issue. And I found that sometimes when booting in windows 10 the boot order is changed. I have two SSDs in my laptop. One has ubuntu and grub and the other has windows installed. The boot order is sometimes changed when windows 10 updates and puts the windows SSD first, causing the system to always boot into windows. Recently it randomly changed it and I started seeing the system boot into the grub prompt. Once I changed the boot order in BIOS, the grub menu loaded normally.

Your Windows may be installed in UEFI boot mode and Mint in BIOS boot mode. The two modes are not compatible and you can only dual boot from UEFI/BIOS menu and may have to turn on or off UEFI or BIOS boot settings. Grub can only dual boot other installs in same boot mode as you booted grub. You can use Boot-Repair to convert a BIOS.

The same issue occurred on my dell laptop with windows 10 and Linux mint 19. So what happened was I was working windows and suddenly the hdd was missing from the disk list. Window was working fine since it was on ssd drive. After being confused for a while I wanted to make sure if the hdd was functioning so I run a diagnostic from the bios after it was done I restarted the machine and got my grub listing back.

After installing Linux Mint 19.1 the system would only boot to the grub rescue> prompt and displayed an error just above it indicating it could not find hd0. Thanks to this thread I accessed the BIOS and under "Storage/Storage Options" I changed the SATA emulation from AHCI RAID to Native Mode IDE and now the system boots up to the proper menu which allows me to choose my Linux Distribution and continue booting successfully.

3a8082e126