VMware Communities
ploxid
Contributor
Contributor

Erreur/error: "efi vmware virtual scsi hard drive(0.0) ... unsuccessful"

A tout les fois que j'essaie de créé une VM, j'ai ce message au lancement?

Each time I want to create a VM, I get this message during launch?

pastedImage_0.png

11 Replies
continuum
Immortal
Immortal

This means that you are trying to install from a CD or ISO which does not have the required files to boot via EFI-firmware.
Can you boot those CDs when you do not assign EFI-firmware ?


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
wolfye
Contributor
Contributor

I have the same problem. It shows this message and then goes to boot manager. But it won't install the os. It's Win10x64. What's the solution please?

kaimaster1
Contributor
Contributor

For this issue can resolve by change firmware type from "EFI" to "BIOS" on New create virtual machine and select "Customs" Untitled.png

hardboiled
Contributor
Contributor

Wrong! I've opted for install operating system later so I haven't got to that stage and it's still giving me that message.

0 Kudos
RDPetruska
Leadership
Leadership

Wrong! I've opted for install operating system later so I haven't got to that stage and it's still giving me that message.

Huh?  It doesn't matter what you've chosen during the create VM wizard, the only way you get this error message is during power on.  Don't know what you mean by "I haven't got to that stage" - it's the only way you CAN see such an error.

Is your installation/boot media connected at boot?  And, is it in fact, bootable?

0 Kudos
hardboiled
Contributor
Contributor

Is your installation/boot media connected at boot?  Yes it's a bog standard installation on a normal pc, and yes the media is VERY readable and being read for other installations on this pc.

I research this message through google and no one has come up with a satisfactory answer. I got so fed up with it I've had to switch to Virtualbox . Virtualbox worked instantly and this problem with VMware is only happening with windows10. Linux is fine.

0 Kudos
hardboiled
Contributor
Contributor

I've used the "custom" option not the recommended option where you get a chance to say where to boot from "EFI" is ticked as standard. Change this to BIOS.

I also created a ISO windows 10 file( I'm just telling you what worked for me)

Next, hardware compatibility is set to workstation 15 (default)  and changed the disk type for it to create to SATA not SCSI, let it do it's thing, and it fire up with no problems.

0 Kudos
isknurul
Contributor
Contributor

@kaimaster1

What you said that's correct but that option is not available in Vmware Player

Please see attached screenshot2020-02-02 01_28_30-Virtual Machine Settings.png

0 Kudos
BERAKNAHichem
Contributor
Contributor

Hello;

Thanks for the Help that worked immediately after changing the booting to BIOS.

Thanks

0 Kudos
jinsonkv
Contributor
Contributor

1.jpg

I also had the same issue while installing windows client OS. But there was no issue for installing windows 2019 Server version. After a lot of research,I understood that, it ws due to firmware type. Change your firmware type from UEFI to BIOS and you are ready to go.

Instructions here:- https://techiesvoice.com/efi-vmware-virtual-scsi-hard-drive-no-media-error/

0 Kudos
dariusd
VMware Employee
VMware Employee

Hi.  I'm one of the engineers who works on VMware's virtual machine EFI firmware.

VMware's virtualization platforms have supported booting Windows 10 x64 through EFI firmware for many years now.

If switching to BIOS "fixes" the problem, then your problem is that your Windows installation image is corrupt or has been modified in a way that makes it unbootable through EFI.  The files used for EFI boot are often at the very end of the disc image, so a truncated download will result in an image which can boot through BIOS but not through EFI.  Tools which modify the DVD image often do not safely handle the files required for EFI boot, resulting in an image which can boot through BIOS but not through EFI.

Please check the file size and MD5/SHA1 checksums of your Windows download against those provided on the download site... I expect that they will differ.

Thanks,

--

Darius

0 Kudos