Windows 10: Converted virtual machine from VmWare to Hyper V and get unrecoverable error when startup...

Hello I converted a Windows 11 virtual machine from VmWare to hyper V and converted the the virtual machine from vmdk to vhdx.When I start the virtual machine in Hyper V i get the error message VmWare Tools unrecoverable error: host-4500 I have attached a ScreenshotException 0x0000096 I tried to delete/deinstall VmTools but when I click on deinstall it didn`t work. I can also not delete the folder VmWare Tool.How can i remove this error message?Best regardsMathias

:)

 

Cannot turn off Hyper V, cannot run Virtual Box machines or VMWare machines

Since the latest update:

Edition: Windows 10 Pro

Verion: 1607

OS Build: 14393.222

I can no longer turn off Hyper V and thus cannot run Virtual Box machines or VMware machines.

When I attempt to turn off Hyper V and restart Windows as requested, Windows simply re-enables Hyper V.

Then when I try to run a Virtual Box machine, I get an error like this:

Failed to open a session for the virtual machine Centos 70.

VT-x is not available (VERR_VMX_NO_VMX).

Result Code:

Component:
ConsoleWrap

Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

When I try to start a VMware machine, I get this:

VMware Player and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Player.

But as I have noted, I am not able to turn off Hyper-V since the Anniversary Update.

Any suggestions would be greatly appreciated.

 

Installing a Virtual Machine in Windows 10

Step #1 is to decide which virtual machine software you wish to install.

The three most popular choices are:

• VirtualBox (from Oracle)
• VMWare Workstation Player (from VMWare); and
• Hyper-V (from Microsoft)

Once you've made your choice you can find detailed, illustrated instructions for installing each one on the internet.

As a personal suggestion: You might find it easier to use either VirtualBox or VMWare Workstation Player. Hyper-V is more complicated to setup.

Between VirtualBox and VMWare, I think you'll find VirtualBox more user-friendly, and it has the advantage of allowing you to create checkpoints - backups of your virtual machine - whereas to do that in VMWare you'll need to upgrade to their (expensive!)
paid version.

 

Issue with Generation 2 Hyper-V machines

Hello, thank you for reaching out to the Microsoft Community. I'm here to help with your questions or issues. Just note – this is a place where passionate Microsoft users help each other, we don't work directly for Microsoft.

As for your issue, the problem is that the Hyper-V SCSI controller driver, which helps your virtual machines talk to the storage, lives mainly on the Hyper-V host itself. It doesn't really communicate directly with Azure.

Think of it like this: the driver is the translator between your virtual machine and the storage it uses. When you move the virtual machine to VMware, the new host doesn't understand the language of the Hyper-V SCSI controller, so your virtual machine can't boot up.

Can you provide the exact error message or log entries you are seeing when the VMs fail to start?

I can think of a few things you can try to fix this:

Install the driver on the VMware host: See if you can find a way to install the Hyper-V SCSI controller driver on your VMware host. This might be a bit tricky, but it's worth a shot.

Change the virtual disk controller: Before you migrate, try switching the virtual disk controller in your Hyper-V settings from SCSI to IDE or SATA. These are more commonly supported and might work without the specific driver.

Convert your virtual disks: If the first two options don't work, you could try converting your virtual disks from the Hyper-V format (VHDX) to the VMware format (VMDK).

If you have any other questions, feel free to ask.