If you are new to the VMware workstation and virtualization process, you may see a lot of error messages during the configuration. Don’t worry, almost all newbies go through the same situation and finally tackle down every issue they are facing.
Today we are dealing with one of the common and primarily occurring errors on VMware workstation. While you start learning a virtual machine, you have to load an operating system on the workstation. But while booting the OS, you might get some errors. EFI VMware Virtual SCSI Hard Drive No Media Error is one of the common among them and most people still don’t know how to fix it.
Please have a look at how to fix this issue in a few steps.
How to Fix EFI VMware Virtual SCSI Hard Drive (0.0) No Media Error?
Have a look at how this error message comes on your screen. You start your VMware work station and load an operating system in it. Say for example Windows 10 client OS. You continue setting up the virtual machine and finishes the basic configuration like hardware specification, hard disk location, etc. However, once you start the VMware, you will see a black window like below.
Attempting to start up from:
–> EFI VMware virtual SCSI Hard Drive (0.0)… No Media.
–>EFI VMware Virtual SATA CDROM Drive (1.0)… No Media.
–> EFI Network…
You can’t do anything at this moment and after a few seconds, you will see a blue screen window like below.
You won’t be able to boot from any of the Boot Manager devices like SCSI Hard Drive, SATA CDROM Drive, Network or from Internal shell.
Again when you select the Boot Normally option, it will end up in the black screen and show unsucessful message instead of “No Media” as we see earlier.
Attempting to start up from:
–> EFI VMware virtual SCSI Hard Drive (0.0)… unsuccessful.
–>EFI VMware Virtual SATA CDROM Drive (1.0)… unsuccessful.
–> EFI Network…
>>Start PXE over IPv4.
How to Solve EFI VMware Virtual SCSI Hard Drive (0.0) Unsuccessful Error?
It is pretty easy to fix this issue. By default, your VMware system is using UEFI settings to boot the operating system. However, some operating system might use the old BIOS settings to boot successfully. So you need to change firmware type from UEFI to BIOS.
Step 1:- Go to the settings of your VMware.
Step 2:- There you can see the options tab. Click on that.
Step 3:- Navigate to the bottom and you will see “Advanced” option and click on that. There you will see firmware type. By default, it will be UEFI. Change it to BIOS and click OK. Now start your virtual machine and you will be able to load windows operating system without any errors.
Conclusion
VMWare by default loads an operating system in UEFI mode. Sometimes, this configuration creates issues for loading the operating system especially Windows 10. So all you have to do is to change the firmware type from default UEFI mode to BIOS mode.
Do you have any other suggestions to add here? Please comment below.
Gracias. Tengo el problema de que en el directorio ” Muy Computer” no me aparece los subdirectorios de Windows server ni Windows 10. Aparecen solo los ejecutables de Vmware y Vmware share.
Hola Jinson. Te comento que ya logré cambiar en Windows de UEFI A BIOS, osea ya resolví que no aparecía el directorio de Windows aunque el Windows server no aparece y no se sí por eso la en le ejecución del Vmware se detiene y dice que NO ENCUENTRA EL SISTEMA OPERATIVO QUE ES MI NUEVA DUDA. AGRADEZCO SU ATENCIÓN.
Hello, when I select ‘Options’ I cannot see ‘Advanced’ , what can I do?
Thanks for the tip, It worked.