VMware Communities
Niko_H
Contributor
Contributor

Fusion 11 (mac mojave) findet BootCamp VM nicht mehr, attempt EFI IDE unsucessfully

Boot Camp Partition auf MAC (Win 10) funktioniert direkt gebootet nach wie vor!

Als Virtuelle Maschine importiert (also Boot Camp) bricht der Startvorgang ab, dass die "EFI VMware IDE nicht zu finden sind..." und landet im "BIOS".

Boot Camp auch schon als neue Maschine importiert, nach dem Update von sierra auf Mojave, leider kein Erfolg.

Hat Jemand eine Idee, wie das Problem zu lösen ist?

Danke

Niko

0 Kudos
5 Replies
nancyz
VMware Employee
VMware Employee

Hi Niko_H ,

Is your Boot Camp using legacy BIOS? Could you try the solution described in the following link:

VMware Knowledge Base ?

0 Kudos
Niko_H
Contributor
Contributor

Hi Nancyz,

I did excactly as described, the boot camp worked perfect while SIP was disabled,

but when finishing the "Boot Camp.vmdk" configuration the boot process aborted

displaying: "Configuration File is out of date, please gererate a new VM" (original: Die Konfiguration für Ihre virtuelle Boot Camp-Festplatte ist abgelaufen.)

Problem still remaining... any other solution?

thanks, Niko

0 Kudos
wila
Immortal
Immortal

Niko,

Perhaps a silly question, but did you delete the existing boot camp VM?

That step is most likely required for the steps outlined in the KB article to work.

For the record, as the bootcamp VM is sort of a "pointer to the real machine data", deleting the bootcamp VM does not delete any actual data.

IOW, deleting the bootcamp VM and recreating it is a safe thing to do.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
0 Kudos
Niko_H
Contributor
Contributor

Hi Wi.,

yes, the old boot-camp VM was deleted and after disabling SIP I created a new one following the

instructions. but with no success.

I also deinstalled the VMFusion by the deinstaller and installed it back completely new.

Any other idea to boot from windows and not from the EFI VMware "bios"?

Thanks, Niko

0 Kudos
haralds
Enthusiast
Enthusiast

Known issue. See fix here: VMware Knowledge Base

0 Kudos