I owe you a beverage of your choice!!!!!!! Your video and extremely clear steps, just saved me having to rebuild ***HOURS*** worth of work on a VM in Virtual Box! Thank you! Thank you! Thank you, for making this video and publishing it!!! :-) :-) :-) This was a config for the VB appliance for 'Home Assistant'. I changed 'Debian' to 'BOOT' and 'grubex64.efi' 'bootx64.efi'. I created 'startup.nsh' file, saved it; and the system boots just like it did immediately after the install. Somehow, I created the failure myself, in trying to move the .vdi file from one filesystem to another. Everything was working until I did that. I was to the point of starting over from scratch, until I watched your video. My system now boots again. I'll work on how to *properly* move the .vdi file to the new filesystem (Windows drive); after I've made more backups and notes. THANKS AGAIN!!!!!!!! :-)
Thanks man. When i was thrown into the EFI shell for the first time I was so confused. Your video made it very clear what is going wrong and how to fix it.
Worked like a dream. After restoring windows 10 backup to virtualbox machine using clonezilla, I was left with GRUB> prompt (because I had dual boot setup with Ubuntu when clonezilla backup was done). Booted using windows 10 recovery disk tried to run the three bootrec commands. First bootrec /fixmbr worked, but for /fixboot it was 'access denied'. Ended up renaming the BCD file to BCD.old, then recreating it using 'bcdboot' command. Then tried to run bootrec /fixmbr and bootrec /fixboot commands, however, still 'access denied' on bootrec /fixboot. So, ran 'bootsect /nt60 C:' Rebooted, and I was left with the SHELL> prompt. Followed your video. Instead of the Debian directory I cd'd to Windows directory. In there there were two .EFI files. When I typed the first and hit enter there was an error, so typed the second filename and hit enter. Windows started booting. Shutdown, then started machine again, and it started straight into Windows. I didn't have to edit/create the startup file. Great video. Well explained.
Thank you very much. I always thought my installation was not supported by UEFI until I found your video, never knew I could actually move on from that linux shell, I thought was a dead-end. I didn't even have to watch your full video and was able to fix my boot issue. Thanks :)
i type in cd EFI and it says "Directory 'FS0:\EFI' was not found. i tried again with an iso and it now says "cd: 'FS0:\EFI' is not a directory, i was trying to run macOS X Mavericks
OTB, thanks for taking the time to make this video. I was having issues with stability for a home automation server running in a VM, and this did the trick. So simple when you take the time to explain it!
I absolutely adore scholar minds like you. Without all the pseudo scientific talk to imitate knowledge, you make people understand it. I have struggled with regenerating the EFI boot system, whilest it was just a few lines to edit. Thank you so much!
DITTO! Hello? Is this thing on? Can you hear the words that are coming out of our mouths? LOL. Seriously though...i get the following error when doing 'ls' ls: File Not Found - 'FS:\' Any help? Thanks.
@@kojam1 the problem you are probably facing when trying to start is: No windows 10 iso. download from here and follow a turtorial or something. Link: www.microsoft.com/en-us/software-download/windows10 download the multimedia tool
Hello OldTechBloke, you've made my day. Thank you a lot!! I had been scratching my head for almost one week until I saw your video on youtube. I'm looking forward to seeing more of your videos. See you soon. God bless you
thank you so much, for people after me. If you did an image of your linux system tried to mount it on a virtualbox machine and you can't getr it to boot, this is the solution.
Wouldn't work for me unfortunately. I'm running Windows 10, VirtualBox 6.1, Ubuntu 20.04. When I include EFI the error screen appears. When I turn EFI off the VM fires up via "Headless Start" only. My VirtualBox experience has been a rocky one. Thanks for the vid OTB!
Hours of googling, solved from this video. If anyone is looking to boot Acronis True Image from bootable media in virtual box, the solution for me was creating an iso from the USB I had, then enabling EFI, setting up iso as optical disk, changing boot order so optical disk is first, running into the issue described in this video, and following the solution described.
There is a way to avoid dropping to 'startup.nsh' script. Just copy the bootloader program (in the case of grub it's going to be grubx64.efi) to '/EFI/BOOT/BOOTX64.EFI'. The VirtualBox's UEFI Shell will pick it up automatically. Thank you!
In UEFI shell I have only BLK0: BLK1: BLK2: in mapping table. There is no FS alias. VM created at laptop and I am moving it to destop pc. VM working fine in laptop VBox. Linux in question is ALT Linux. I have Slackware VM created at same laptop. Moving to desktop pc was smooth.
for those who are facing file not found option.. First, you have to understand what the brother was doing. He went to "fs0:\EFI\debian\grubx64.efi". But everyone here does not have that in that same directory. It might be in fs(1,2,3,4,...): . So now we have to find the directory where EFI is present with "fs0:>ls" command if not try "fs1:>ls" and so no....
Help Please Once i got to to the EFI Directory and hit list i got only the parrot directory 4,096 bytes, debian or boot show0 bytes, in other words theyre not even there, how can i fix this? This install was made on Virtual Box btw
Right Now...even I faced the problem and tackled it. Actually some installations does not contain the debian directory.. instead some just contain the BOOT directory...and contain the bootloader named " BOOTX64.EFI" (In my Directory yours might be different)...We have to just type it case sensitive as in your system (remember very important) even if one letter with case sensitive(small or capital ) doesn't match the bootloader or any directory...then it will always show 'directory not found' or 'command not found'...So even to open boot directory I had to write ' cd BOOT'( in capital as written in my file) or otherwise I would fail to open.... So just as simple as ....If no debian(case sensitive) directory just find out there should be boot(Case sensitive) directory and just open it with 'cd' and write the same ditto letters in your next command eg:-BOOTX64.EFI (in my Directory)....And Your OS will boot Definitely 😄😄
hi otb greate video. is it possible to start in the efi shell with a bootable usb? for example to mount a preinstalled win10 with live kali linux on the bootable usb?
BHAI mere laptop me ek problem aa rhi hai me apni c drive ko gpt we MBR me convert kr RHA that to uske baad restart ka option aya mene restart kr dya jab WO restart hua to usme uefi KI screen aa rhi hai or boot me option me bhi surf main option aa RHA hai air an mera laptop khul nhi raha please help me please.please.please.
You just made my life a few weeks ago and I haven't had the time to say thank you. So thank you!
You’re welcome
I owe you a beverage of your choice!!!!!!! Your video and extremely clear steps, just saved me having to rebuild ***HOURS*** worth of work on a VM in Virtual Box! Thank you! Thank you! Thank you, for making this video and publishing it!!! :-) :-) :-)
This was a config for the VB appliance for 'Home Assistant'. I changed 'Debian' to 'BOOT' and 'grubex64.efi' 'bootx64.efi'.
I created 'startup.nsh' file, saved it; and the system boots just like it did immediately after the install.
Somehow, I created the failure myself, in trying to move the .vdi file from one filesystem to another. Everything was working until I did that.
I was to the point of starting over from scratch, until I watched your video. My system now boots again. I'll work on how to *properly* move the .vdi file to the new filesystem (Windows drive); after I've made more backups and notes.
THANKS AGAIN!!!!!!!! :-)
You’re very welcome. I’ll have a Guinness if we ever meet 😁
Thanks man. When i was thrown into the EFI shell for the first time I was so confused. Your video made it very clear what is going wrong and how to fix it.
You're welcome!
Worked like a dream. After restoring windows 10 backup to virtualbox machine using clonezilla, I was left with GRUB> prompt (because I had dual boot setup with Ubuntu when clonezilla backup was done). Booted using windows 10 recovery disk tried to run the three bootrec commands. First bootrec /fixmbr worked, but for /fixboot it was 'access denied'. Ended up renaming the BCD file to BCD.old, then recreating it using 'bcdboot' command.
Then tried to run bootrec /fixmbr and bootrec /fixboot commands, however, still 'access denied' on bootrec /fixboot. So, ran 'bootsect /nt60 C:' Rebooted, and I was left with the SHELL> prompt. Followed your video. Instead of the Debian directory I cd'd to Windows directory. In there there were two .EFI files. When I typed the first and hit enter there was an error, so typed the second filename and hit enter. Windows started booting.
Shutdown, then started machine again, and it started straight into Windows. I didn't have to edit/create the startup file.
Great video. Well explained.
quick update: to boot Windows type 'bootmgfw.efi'. It's in the EFI/Microsoft (or EFI/Microsoft/Boot - don't remember exactly) directory
Thank you very much. I always thought my installation was not supported by UEFI until I found your video, never knew I could actually move on from that linux shell, I thought was a dead-end.
I didn't even have to watch your full video and was able to fix my boot issue. Thanks :)
Glad I could help
i type in cd EFI and it says "Directory 'FS0:\EFI' was not found.
i tried again with an iso and it now says "cd: 'FS0:\EFI' is not a directory, i was trying to run macOS X Mavericks
same problem ;/
Same problem
Same problem
same problem
@@Leonardo-qe1on same problem. Any help?
OTB, thanks for taking the time to make this video. I was having issues with stability for a home automation server running in a VM, and this did the trick. So simple when you take the time to explain it!
Glad it helped!
Thankyou OTB, my HomeAssistant VM stopped working since updating VB yesterday. Works perfectly using your method, saved me a lot of grief!
You are both a gentleman and a scholar- thank you kindly Sir. Very easy to follow and incredibly useful.
Terrific! thanks old bloke, being one myself, and learning virtualisation it is not always the esaiest of concepts to grasp but I am doing it.
Glad it helped!
Thank you so much, been fighting this for a few days. You saved me countless days rebuilding my virtual box.
Glad it helped!
Thank you! This was exactly my problem and you showed the solution without a bunch of nonsense surrounding it.
You're welcome
This channel needs WAY more subs!! Can’t say thanks enough!!!
Thanks mate, we are getting there
I absolutely adore scholar minds like you. Without all the pseudo scientific talk to imitate knowledge, you make people understand it. I have struggled with regenerating the EFI boot system, whilest it was just a few lines to edit. Thank you so much!
Thanks for this vid mate. Was having this problem with Parrot Security in Virtualbox. Worked like a charm.
Glad it helped
Not an error window, per se, just unusual. That was the perfect solution! Thank you.
Hey it says fs0: is not a valid mapping?
DITTO! Hello? Is this thing on? Can you hear the words that are coming out of our mouths? LOL.
Seriously though...i get the following error when doing 'ls'
ls: File Not Found - 'FS:\'
Any help? Thanks.
@@kojam1 the problem you are probably facing when trying to start is: No windows 10 iso.
download from here and follow a turtorial or something.
Link: www.microsoft.com/en-us/software-download/windows10
download the multimedia tool
@@feelinglucky2452 Thanks so much. I forgot to mention. I found MacOS vmdk and am trying to create a macOS vm.
Need ttooo
@@ronmeister9000 I think my previous answer should still work, so try that out!
This was a bugbear for me. Thankyou very much. It saved me having to rebuild a VM I'd sunk several hours into.
thank you so much! ("don't panic", but I was really panicked... thanks once more!)
That was extremely helpful! I thought I had a bad .iso at first. Thank you sir!
You've just made my day. I was struggling to export an appliance and was facing this error all the time. Thanks's a lot
oldtech in my computer efi is not show if i type list
THANK YOU!!! Sir, you are a legend you literally saved my entire system.
Hello OldTechBloke, you've made my day. Thank you a lot!! I had been scratching my head for almost one week until I saw your video on youtube. I'm looking forward to seeing more of your videos. See you soon. God bless you
thank you so much, for people after me. If you did an image of your linux system tried to mount it on a virtualbox machine and you can't getr it to boot, this is the solution.
Excellent sir
This is we called experience expert
directory"FS0:\EFI\Debian' was not found
FS0:\EFI\Parrot
Great video that I have seen online and straight forward. Worked perfect for me. Cheers
Thanks it worked for me. My new arch guest was not booting. Solved it with your video.👍
Welcome 👍
THANKYOU UNCLE YOU SAVED MY DAY I WAS PANINCKING BEFORE WATCHING OUR VDEO BUT AFTERTHAT IT HELPED ME
THANK YOU
YOU MAY LIVE LONG
Wouldn't work for me unfortunately. I'm running Windows 10, VirtualBox 6.1, Ubuntu 20.04. When I include EFI the error screen appears. When I turn EFI off the VM fires up via "Headless Start" only.
My VirtualBox experience has been a rocky one. Thanks for the vid OTB!
Thanks a bunch! I'm getting Parrot OS set up and encountered the same issue. This worked like a charm. Appreciate it!
Glad it helped!
one of the best explaining Videos on youtube.
Thank you very much :)
You're very welcome!
Thanks friend! I will start to learn Parrot Os in Virtual Box. Your solution really works, sorry but my English isn't good :( Thanks again!
Glad I could help
Thanks man! It works!!
Thank you for the video! Regards from Spain!
Excellente amigo. You're a lifesaver
worked perfectly thanks i wish i had seen this before re-downloading and reinstalling about 3 times
Muchas gracias después de 3 veces que vi el vídeo entendí la solución. Saludos desde México.
Thank you!!! I've been stuck for a week. everytime I removed the cdrom drive from my boot menu it came to this screen
Hours of googling, solved from this video. If anyone is looking to boot Acronis True Image from bootable media in virtual box, the solution for me was creating an iso from the USB I had, then enabling EFI, setting up iso as optical disk, changing boot order so optical disk is first, running into the issue described in this video, and following the solution described.
Brilliant! Thanks so much. This was just what I needed.
You're very welcome!
Thanks a ton I was stuck in Shell in UEFI.
Glad it helped
As always a brilliant concise video!
Thank you kindly!
There is a way to avoid dropping to 'startup.nsh' script. Just copy the bootloader program (in the case of grub it's going to be grubx64.efi) to '/EFI/BOOT/BOOTX64.EFI'. The VirtualBox's UEFI Shell will pick it up automatically.
Thank you!
could you plz elaborate to me.. i dont know much of this field sir
I did exactly the same, but after BOOTX64.EFI gave me unsupported command error, do you have any Idea how to solve it?
Many thanks for the tip. Luv the vids, keep em coming. Btw new subscriber here.
Many thanks :-)
In UEFI shell I have only BLK0: BLK1: BLK2: in mapping table. There is no FS alias.
VM created at laptop and I am moving it to destop pc. VM working fine in laptop VBox.
Linux in question is ALT Linux.
I have Slackware VM created at same laptop. Moving to desktop pc was smooth.
you are a hero! God bless you good sir
Really appreciating, thanks a lot. :)
No worries!
Thanks! I've fixed same problem with macOS Catalina!
You're welcome!
for those who are facing file not found option..
First, you have to understand what the brother was doing. He went to "fs0:\EFI\debian\grubx64.efi". But everyone here does not have that in that same directory. It might be in fs(1,2,3,4,...): . So now we have to find the directory where EFI is present with "fs0:>ls" command if not try "fs1:>ls" and so no....
Brother?
a biiigggggggg thank you i've looked for everywhere and finaly i found this video ....
My problem is that it DOESN'T want to start from the virtual DVD that I am trying to install from, not after installation.
>w
What is Debian? I have mac OS X
when i put edit startup.nsh it says access denied
Hey boss when I get to cd Debian it says cd: Target directory not found can you help?
looks like it wasn't installed in efi mode. Did you tick the efi box?
Is Debian the OS you're installing? Type 'ls -a' to see available files and directories
they still have not fixed it yet. Thank you for a video.
Awesome fix, thanks for teaching!
for OS windows 10 ,what do you it ; on type FS0 : the message next : is not a valid mapping
Great work, can you make this for MAC OS to? Please
Never tried VB in mac, but I'll make a note and see what I can do
Ahh! Thanks mate!
Worked for me also, thanks for sharing!
After i Click "cd EFI" its said (FS0:\EFI is not a directory.
I successful found my way to the "cd Efi" but i got a cd efi not found. Please help
My MacOS Monterey on VMware workstation pro 16 keeps restarting because there’s a problem. It says kernel panic. May you help please. Thank you.
good job man worked with me thanks
it didnt work as expected . error is not a valid mapping
Thanks so much for your tutorial
You’re welcome
help i can't type :
Type : with "ñ"
@@sicmundus5081 thx
You are awesome! Thanks very much for your video :)
Thank you
thanks alot for the help, i found your video and was able to boot the system
Brilliant, glad to help
Thanks this helped me out resolve this error
Excellent! thanks!
Thanks very much from Cuba
Welcome!!
Too many arguments or is not a directory.have a Install macOS Mojave app file in shell .help
I dont found any fs0:
It shows fs0: is not a correct mapping
Plz help me
Have you unmounted the iso?
Thank you sir! Really usefiul one!
Thanks so much. Great instruction.
it says "file not found" for ls, cd EFI and cd Debian. Help
Ive got a grubx64.efi is not recognized as an internal or external command, operable program or script file.
Can you see it in the terminal?
OldTechBloke yes, I’m able to change directories and run grub, saving that as the startup.nhs script threw that error.
after my command: ls it shows the error: file not found 'fs0:\'
there is no efi directory
Thought this might help me booting ventoy multi-usb but fs0 doesn't appear in list is not a valid mapping.
After typing ls it says “ls: file not found - ‘FS0:\’”
Help Please
Once i got to to the EFI Directory and hit list i got only the parrot directory 4,096 bytes, debian or boot show0 bytes, in other words theyre not even there, how can i fix this?
This install was made on Virtual Box btw
If there's nothing in the directory it's likely the install wasn't efi. Are there any other directories in EFI?
Just cd into the parrot directory. And there you'll find grubx64.efi.
on the first step it keeps saying, "'fs0' is not a correct mapping"
fs0: remember the colon !
I try to follow your steps it shows fs0: is not a correct mapping
That's weird. what distro have you installed?
@@OldTechBloke I have got same problem
I installed Kali linux
Same Here Man Please someone help
When I typed cd Debian it said target directory not found
I tried typing cd Boot too but that did not work either, please help
Right Now...even I faced the problem and tackled it.
Actually some installations does not contain the debian directory..
instead some just contain the BOOT directory...and contain the bootloader named " BOOTX64.EFI" (In my Directory yours might be different)...We have to just type it case sensitive as in your system (remember very important) even if one letter with case sensitive(small or capital ) doesn't match the bootloader or any directory...then it will always show 'directory not found' or 'command not found'...So even to open boot directory I had to write ' cd BOOT'( in capital as written in my file) or otherwise I would fail to open....
So just as simple as ....If no debian(case sensitive) directory just find out there should be boot(Case sensitive) directory and just open it with 'cd' and write the same ditto letters in your next command eg:-BOOTX64.EFI (in my Directory)....And Your OS will boot Definitely 😄😄
@@ankitnishad3320 thank you so much
i tried the second one and it said access denied
i got EFI 1.10 on my screen it didnt let me us the cd Debian part
hello, when i tried edit startup.nsh is showing edit option is access denied , how to rectify could you please help
Awesome!!! Thank you!!
Any time!
I don't have any directory as Debian what should I do.....please help me out..
Great tip, thanks!
Upon edit startup.nsh it says access denied
hi otb greate video. is it possible to start in the efi shell with a bootable usb? for example to mount a preinstalled win10 with live kali linux on the bootable usb?
Yes it is but there’s a lot of fiddling involved. Look at my ventoy video
Oh thank you so much! I was able to solve my issue :D
Glad I could help!
Thanks!! you are the best!
Thank you
BHAI mere laptop me ek problem aa rhi hai me apni c drive ko gpt we MBR me convert kr RHA that to uske baad restart ka option aya mene restart kr dya jab WO restart hua to usme uefi KI screen aa rhi hai or boot me option me bhi surf main option aa RHA hai air an mera laptop khul nhi raha please help me please.please.please.
Helpful but my VM for windows vista just didn't wanna do anything.
grubx64.efi won't run for me it keeps saying "Command Error : Unsupported". Can anyone help me?