Error: Module 'Monitor' power on failed. Failed to start the virtual machine.

[Kaonashi42]

Hello,

Edit:

I did install Valorant before having the problem.

So I have been trying to create virtual machine with VMware workstation 15 pro and was not able to power it on.

Here is the message I get when i use "power on this virtual machine":

This virtual machine failed to switch to 64 bit mode. This failure might be due to a lack of available memory on the host.

Module 'Monitor' power on failed.

Failed to start the virtual machine.

I am using:

- Ubuntu LTS 18.04 iso

My computer has:

- Windows 10 Education

- 16Gb RAM

- More than 100Gb of free space (hard disk)

- Motherboard: an asrock phantom

- CPU: amd ryzen 5 3600x

- Antivirus: Windows defender

I have tried:

- Rebooting

- Updating windows (normal updates)

- Keeping the default parameters while creating the vm

- Limiting the RAM to 250mb

- limiting the hard disk to 1Gb

- Checking that SVM and SMT are enabled for virtualization in the Bios

- Using VMware workstation Player 15, same issue

- Using virtualbox with the same configuration, it is working

- enabling/disablings Windows Hyper-V

- Disabling windows defender my firewalls

Here is my vmware.log file:

https://easyupload.io/e9r0n7

Here are the last lines if you do not wish to dl the entire file:

2020-04-19T19:23:13.805+02:00| vmx| I125: Host AMD-V Capabilities:

2020-04-19T19:23:13.805+02:00| vmx| I125: SVM Revision:           1

2020-04-19T19:23:13.805+02:00| vmx| I125: ASIDs Supported:        32768

2020-04-19T19:23:13.805+02:00| vmx| I125: Nested Paging:          yes

2020-04-19T19:23:13.805+02:00| vmx| I125: SVM GMET:               yes

2020-04-19T19:23:13.805+02:00| vmx| I125: LBR Virtualization:     yes

2020-04-19T19:23:13.805+02:00| vmx| I125: SVM Lock:               yes

2020-04-19T19:23:13.805+02:00| vmx| I125: NRIP Save:              yes

2020-04-19T19:23:13.805+02:00| vmx| I125: TSC Rate MSR:           yes

2020-04-19T19:23:13.805+02:00| vmx| I125: VMCB Clean Bits:        yes

2020-04-19T19:23:13.805+02:00| vmx| I125: Flush by ASID:          yes

2020-04-19T19:23:13.805+02:00| vmx| I125: Decode Assists:         yes

2020-04-19T19:23:13.805+02:00| vmx| I125: Pause Filter:           yes

2020-04-19T19:23:13.805+02:00| vmx| I125: Pause Filter Threshold: yes

2020-04-19T19:23:13.805+02:00| vmx| I125: Monitor_PowerOn: HostedVSMP skew tracking is disabled

2020-04-19T19:23:13.805+02:00| vmx| I125: Loaded crosspage: .crosspage. Size = 4096 bytes.

2020-04-19T19:23:13.805+02:00| vmx| I125: vmm64-modules: [vmm.vmm64, vmce-vmce.vmm64, viommu-none.vmm64, vprobe-none.vmm64, hv-svm.vmm64, gphys-npt.vmm64, callstack-none.vmm64, swstats-none.vmm64, gi-none.vmm64, gmm-none.vmm64, ahci-ahci.vmm64, !ahciRegs=0x0, !ahciShared=0x1000, !e1000Shared=0x1c00, !vmSamples=0x2480, !theIOSpace=0x24c0, !ttGPPerVcpu=0x8800, {UseUnwind}=0x0, numVCPUsAsAddr=0x1, {SharedAreaReservations}=0x8840, {rodataSize}=0x20915, {textAddr}=0xfffffffffc000000, {textSize}=0x8b65e, <MonSrcFile>]

2020-04-19T19:23:13.805+02:00| vmx| I125: vmm64-vcpus:   1

2020-04-19T19:23:13.818+02:00| vmx| I125: Module 'Monitor' power on failed.

2020-04-19T19:23:13.818+02:00| vmx| I125: VMX_PowerOn: ModuleTable_PowerOn = 0

2020-04-19T19:23:13.818+02:00| vmx| I125: Vix: [mainDispatch.c:1163]: VMAutomationPowerOff: Powering off.

2020-04-19T19:23:13.819+02:00| vmx| I125: Win32U_GetFileAttributes: GetFileAttributesExW("C:\Users\X\Documents\Virtual Machines\Ubuntu 64-bit\Ubuntu 64-bit.vmpl", ...) failed, error: 2

2020-04-19T19:23:13.819+02:00| vmx| I125: Policy_SavePolicyFile: invalid arguments to function.

2020-04-19T19:23:13.819+02:00| vmx| I125: PolicyVMX_Exit: Could not write out policies: 15.

2020-04-19T19:23:13.819+02:00| vmx| I125: WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0

2020-04-19T19:23:13.819+02:00| WinNotifyThread| I125: WinNotify thread exiting

2020-04-19T19:23:13.822+02:00| vmx| I125: Vix: [mainDispatch.c:4215]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0

2020-04-19T19:23:13.822+02:00| vmx| I125:

2020-04-19T19:23:13.822+02:00| vmx| I125+ Power on failure messages: This virtual machine failed to switch to 64 bit mode. This failure might be due to a lack of available memory on the host.

2020-04-19T19:23:13.822+02:00| vmx| I125+ Module 'Monitor' power on failed.

2020-04-19T19:23:13.822+02:00| vmx| I125+ Failed to start the virtual machine.

I cannot seem to find any related issues or solutions that fits my problem.

Thank you in advance for any help provided.

[Rakinare]

You can disable Vanguard from their System Tray icon when you started your PC. This works for me 100% of the time. Ofc you have to do it on every system restart then and reboot your PC if you want to play Valorant.

[cdc1]

+1 to Valorant install causing the issue (specifically the Riot Vanguard anti-cheat component.) Turning Vanguard off every time I want to power-on my VMs is unreasonable for me, so I’d rather just not have it on my system at all.

I completely uninstalled Valorant and Riot Vanguard, and am now able to power-on my VMs.

[SaltySalt]

I had the same problem after installing valorant, same as you did. Their anti cheat software "Vanguard" blocks the execution of some services/ programs in the background, including some necessary services for running VMware virtual machines.

The solution I found on this site was to disable vanguard running this command in the cmd as an administrator: sc config vgk start= disabled

Then do a restart and you should be able to run your VM again.

Riot should fix Vanguard ASAP, it doesn't need to have kernel access.

Hope this works for you too.

[esuntp]

I had exactly same issue with my new computer with Ryzen 7 3700x CPU.

Finally I found the workaround on my system. the problem was when I had installed any services related to Hyper-V.

If you have Hyper-V or  security service that using Microsoft Defender Application Guard, remove them all and reboot you system.

That should fix your problem. I'm wondering if that Vanguard application might also uses similar virtualization service under the hood.

Good Luck,

[Sharfurer]

Hi! When I found this problem, I just disabled it in the VM settings:

• Virtualize Intel VT-x/EPT or AMD-V/RVI

• Virtualize CPU performance counters

https://i.imgur.com/ReInZOX.png

As I understand it, these options are needed for  Nested Virtualization

Everything works!

[noelmom]

Can confirm that I have Valorant installed, removing it resolved the issue.  Thanks.

[ivenkwan]

it resolved my problem

[tmcmil]

Had the same issue; Edit VM>Hardware Tab>Processors>Unchecking Virtualize Intel VT.. Worked in my case.

[pratapreddy97]

I had the similar issue, however this was because i had changed few settings in Windows.

just uncheck Virtual Machine Platform

Start button > settings > windows settings type "windows features"

[frank32]

This is nonsense

[frank32]

We want vmware to use the virtual machine platform. This is what they claim to be able to.

But it doesn't work. That "team-effort" between Microsoft and vmware lead to the point that one side broke it (Microsoft with an update). These interfaces can never be kept consistent. Also - vmware pretends to be 'smart enough# to detect that the virtual platform is enable. This is also not the case. Using hyperv and vmware together is a dangerous journey. I think I will stick to hyperv and drop vmware completely.