VMware Communities
ericb99
Contributor
Contributor

Win10 Hyper-V role from the system before running VMware Player.

I'm attempting to launch an OVA image but I keep getting prompted with the following error. I'm not sure what else to try.

  • I checked windows Optional features, and Hyper-V is not installed.
  • I checked the Bootloader and Hyper-V is set to off
  • I also checked Device Guard and Memory integrity is set to off.

  Any thoughts?

See below for the various setting from the machine.

Installed Features (Hyper-V is not listed)

C:\WINDOWS\system32> (get-windowsoptionalfeature -online|Where-Object {$_.State -eq "Enabled"}).FeatureName

Printing-PrintToPDFServices-Features

SearchEngine-Client-Package

MSRDC-Infrastructure

WorkFolders-Client

Printing-Foundation-Features

FaxServicesClientPackage

Printing-Foundation-InternetPrinting-Client

MicrosoftWindowsPowerShellV2Root

MicrosoftWindowsPowerShellV2

Windows-Identity-Foundation

Microsoft-Windows-Subsystem-Linux

NetFx4-AdvSrvs

NetFx4Extended-ASPNET45

WCF-Services45

WCF-TCP-PortSharing45

NetFx3

MediaPlayback

WindowsMediaPlayer

SmbDirect

Windows Boot Loader

C:\WINDOWS\system32>bcdedit

Windows Boot Manager

--------------------

identifier              {bootmgr}

device                  partition=\Device\HarddiskVolume2

path                    \EFI\Microsoft\Boot\bootmgfw.efi

description             Windows Boot Manager

locale                  en-US

inherit                 {globalsettings}

badmemoryaccess         Yes

isolatedcontext         Yes

flightsigning           Yes

default                 {current}

resumeobject            {44ef138a-8ee4-11e9-9092-ea3869f25c6e}

displayorder            {current}

toolsdisplayorder       {memdiag}

timeout                 30

Windows Boot Loader

-------------------

identifier              {current}

device                  partition=C:

path                    \WINDOWS\system32\winload.efi

description             Windows 10

locale                  en-US

inherit                 {bootloadersettings}

recoverysequence        {44ef138c-8ee4-11e9-9092-ea3869f25c6e}

displaymessageoverride  Recovery

recoveryenabled         Yes

badmemoryaccess         Yes

isolatedcontext         Yes

flightsigning           Yes

allowedinmemorysettings 0x15000075

osdevice                partition=C:

systemroot              \WINDOWS

resumeobject            {44ef138a-8ee4-11e9-9092-ea3869f25c6e}

nx                      OptIn

bootmenupolicy          Standard

hypervisorlaunchtype    Off

Device Guard is off:

Annotation 2019-06-17 064553.png

Tags (1)
0 Kudos
2 Replies
xishengzhang
VMware Employee
VMware Employee

Hello, ericb99

Thanks for your posting.

Could you please let us know the error you encountered?

By the way, If a normal VM could be powered on successfully, then it should has nothing to do with hyper-v on host. Anyway, Please paste your error for further looking.

0 Kudos
DavidHochhauser
Contributor
Contributor

Did you ever get an answer to this? I have the same problem.

0 Kudos