How to Fix Module Monitor mode Power on failed in VMware

We got an error message about the Monitor module not being enabled when we started a virtual machine in VMware Workstation. Due to this fact, the machine gives the subsequent error message when it attempts to start up.

It seems that this virtual machine was unable to switch to 64-bit mode at power on. A scarcity of RAM on the host machine can be the reason behind this crash.

"Monitor" power-on module did not succeed.

I was unable to launch the virtual machine.

What to do if VMware's Module Monitor mode power on fails is covered in this post.

What could be the reason why the virtual machine won't turn back on?

Hardware virtualization settings conflict, such as nested virtualization or Hyper-V, corrupted VM configuration files, or software conflicts are some of the reasons for a Virtual Machine not powering on. We will look at the reasons in detail in the section that follows.

Resolved VMWare Power On Module Monitor Mode Failed

If you are working with VMware and get into the problem of Module Monitor mode Power on failed, then you may try the fixes given below.

Disable Windows Virtualization Layers

Enable Hyper-V Enable the Windows Hypervisor and Virtual Machine frameworks.

Bring the VM back to active state by contacting the VM support team.

Now we can start the troubleshooting.

1. Disable Nested Virtualization

Nested virtualization can run a hypervisor inside a virtual machine, but if the virtual machine isn't set up correctly, several conflicts may arise. We would recommend disabling Nested Virtualization to let VMware Workstation use virtualization features of the hardware directly. Let me guide you through doing it once again.

For opening the settings of Virtual Machine, open VMware Workstation, right-click, and then select Settings.

Under the Processor tab, disable virtualization for Intel VT-ex/EPT and AMD-V/RVI.

Click OK to commit the changes.

Restart your computer to make sure the problem has gone away. If that doesn't work, try another option.

2. Disable Hyper-V

Microsoft has its own virtual machine utility called Hyper-V. By enabling it, VMware, the independent platform, will be unable to allocate system resources because it will be busy serving Hyper-V. Therefore, it's recommended that you disable this function. If you want to accomplish it, just follow the steps below.

Start the Run dialog with Win + R and enter the command below.OptionalFeatures.exe's executable

Locate Hyper-V in the list and uncheck the box and any associated boxes

On the previous page click OK, which will prompt the system to restart

After which you check whether the problem still occurs.

3. shut off the hypervisor and the virtual machine platform of windows platform

Windows Hypervisor and Virtual Machine platforms, when enabled, control the hardware virtualization components of the system. This makes it difficult for Virtual Machine to start up and VMware to utilize it. We will disable both features in this solution to ease the load on the hardware virtualization resources.

To open the Run Dialog box, press Win + R. Then, type appwiz.cpl and click OK.

Click the option to Turn Windows Features on or off, then scroll down the list for the Windows Hypervisor Platform and Virtual Machine platform.

Once you have made the necessary changes by unchecking both features, click the Ok button.

When you are done, turn the computer back on to see if the problem goes away.

Learn more about VMware Workstation BIOS by reading this article.

4. bring the virtual machine back into the system

The process of reimporting the virtual machine may help resolve issues caused by corrupted VMX files or other difficulties that may be related to configuration. A virtual machine importation will reset the settings, therefore clearing out any configuration conflicts between the host system and VMware Workstation.

Get VMWare Workstation up and running, then go to File > Open. Another option is to export the virtual machine by clicking Ctrl + O and then going to the location where it is saved. One case in point is: Exported virtual machine (VM) from Dashboard

Click Open once the OVF file is selected to open the Import Virtual Machine Wizard. Then, select the storage directory, fill in the name of the Virtual Machine, and click on Finish or OK. The import will start, and the result will be shown in the status bar.

The importing of the virtual machine will take some time, but once it is done, you can view it in the library.

5] Contact VM Support.

Finally, if none of the above alternatives is successful, VM support should be contacted for further help. They are better positioned to give personalized support and have the latest diagnostic tools at their disposal. For VM support, access the VMware Support Portal, support.broadcom.com, after logging in to your VMware account. Then attach comprehensive error logs to your support request, or chat or call them for immediate assistance.

We hope that with this you can solve the error when turning on the Module Monitor mode in VMware, without further ado: good luck, see you.