UEFI Interactive Shell v2.2 mapping table

[HamzaRadwan2]

i have this error every time i open the virtual machine and idk how to fix it please help

im on Apple silicon

[conath]

This is not an error. It is what happens when you don't have an operating system installed in a UTM VM. I invite you to watch my tutorial video to learn about how UTM works (watch from beginning until 4:49), and read the Windows for ARM install guide on the wiki for more specific information.

[yazdaniit]

where is your tutorial video ?

[AngusC222]

@yazdaniit, Here is his video

[Rtoax]

I got same situation.

[shareef-dweikat]

Did you solve it?

[Rtoax]

参考我的：

[rongtao@ft-74 images]$ efibootmgr efiboot.img 
BootCurrent: 0001
Timeout: 3 seconds
BootOrder: 0001,0002,0000,0003
Boot0000* Setup
Boot0001* CentOS SCSI Device
Boot0002* UEFI Shell
Boot0003  UEFI BootManagerMenuApp

[conath]

this video guide might help

[MESOLONELY]

this video guide might help

Not work on step 6

[70599]

3:40 helped.

[garfieldnate]

@MESOLONELY I initially used the wrong version of virtio; you have to use the same 190 version that he uses in the video. I downloaded 240 and it did not work.

[CelineHarakee]

I got an error "Failed to lock byte 100" in this part... how can I fix it

[shareef-dweikat]

Any updates? I am facing this issue in my Debian VM on my MACOS Apple chip.

[conath]

Did you force-shutdown or -restart the VM using the toolbar buttons? This can corrupt the VM’s hard drive and lead to this screen. You can try booting the VM in console mode (Edit => Display) and then you can look for filesystem errors.

[debojyoti-majumder]

I am also facing the same issue.

[cpach]

FWIW I get this situation too, on a Macbook Pro with Intel CPU.

It has happened with VMs that worked fine for a while, and then this screen appears after booting.

It seems to occur after forcing shutdown of the VM. I’m guessing that the qcow2 becomes corrupted somehow?

[conath]

This is likely the problem. You can try booting the VM in console mode (Edit => Display) and then you can look for filesystem errors.

[goman64]

I resolved this issue on M1 Apple Silicon by disabling UEFI boot. Turn off the VM. Right-click and select Edit->QEMU and uncheck UEFI Boot under Tweaks.

I got the solution from this video which is about Virtualbox.

[alt-dna]

Thank you goman64, however, when I did that and re-ran the VM, it show as "guest has not initialized the display (yet)."

Please help!!

[eliazonta]

same issue :( some1 knows how to fix ?

[watermoon]

thank you very much, goman64，you save my life

[unclefive55]

not working the utm logo even didnt show.

[EvanClausen111]

very thankful!

[stuartofmine]

For me, that's because I downloaded the VHDX file but boot in ISO mode.

Just create a new UTM VM and set true for "import VHDX". Everything is OK now.

[stuartofmine]

[abiredavid]

This worked for me

[19KaliNoob87]

Create a new utm vm via VHDX? How do I do this

[xiaodaiweiwei]

I didn't find the setting button. How could I fix this problem?

[cOnGitHub]

Before the UEFI Interactive Shell Window appears, the following message is shown for a few seconds.

Press any Key as long as that message is shown and Windows Installation will start.

Of course I only noticed this solution after creating some new UTM VMs as proposed in this discussion ;-)

[toddy86]

To add to this, once you have pressed any key, you will receive this screen which won't change for a good couple of minutes. Be patient and the Windows setup will eventually start. Patience on this step was my problem! I thought it was frozen and not doing anything.

[bobmoff]

Thanks! This was the same issue as mine.

[18474475]

牛逼

[kongmunist]

Computer: M1 Macbook Pro
Trying to run: Windows 10 x64

I fixed this with two steps

1. I need to emulate x64 on ARM64, but I instead was used to clicking "Virtualize" (only allows native CPU architecture) on UTM New OS screen instead of "Emulate"
2. Disabling UEFI Boot / EFI Boot in the UTM options

[dt1930]

Wait, how do you disable UEFI Boot/EFI Boot in the UTM options?

[AndyVojambon]

This works for me:

• write "exit" in the interactive shell, then press enter
• then select Boot Maintenance Manager > Boot From File > Choose a Volume > EFI > <Your_VM_OS> > select the .efi file
• press enter and my VM start 🙂

[scratch-iiit]

After the Boot From File an empty screen with file explorer shows
Being done for Kali Linux though

[acertuche368]

I figured it out while trying to do the same thing:

As long as you selected an iso file then you must catch the option to boot from CD while the VM is starting up. Press any key and it will pull the ISO file and run it or else it will just skip over it and get you to the UEFI Shell.

[scratch-iiit]

kept pressing any key but still did not work

[svnv-svsv-jm]

Worked for me!

[wcy18]

uesfel!!

[mgleeim1]

worked..thankyouTT

[GulinaChukotaeva]

thank you very much worked

[AnotherWayIn]

which key is the 'any' key? sorry

[nicolas17]

[jsmayo]

Stumbled upon this after figuring out the solution loool. Just confirming that you need to 'press any key' to initiate the Windows installer. Before starting the instance if you look in configuration portion for the DVD/CD, you'll see the installer pre-loaded 😃

Also, here's a help link for any future readers: https://docs.getutm.app/guides/windows/

[rikikamano]

#3486 (comment)

awesome answer

[19KaliNoob87]

I keep getting 2.70 uefi error.

[Durian-p]

Try press enter repeatedly as fast as you can once you start the VM. I mean really really fast. This solve my problem.

[19KaliNoob87]

I got same situation.

I second this.