Some users have been complaining that VMWare apps have been showing the following error message when trying to open a Virtual Machine.
Failed to lock the file
Cannot open the disk ‘C:\Users\<username>\Documents Virtual Machines Windows.vmdk’ or one of the snapshot disks it depends on.
Module ‘Disk’ power on failed.
Failed to start the virtual machine.
In this article, we are going to dig deep into the topic and see what you need to do if you are seeing Module Disk power on Failed on VMWare.
Before fixing the problem, we need to know what is it and what’s causing it. The problem is, some of the VMWare files are blocking your VM. Which is needless to say, won’t let you play the game. But the question is why is it blocking the Virtual Machine. To fathom this, we need to understand the mechanism behind VMWare.
When you open a Virtual Machine, some files are there to control the functioning of your machine. The files with the extension .lck are created as soon as the machine is turned on, and they make sure that multiple VMs can’t read or write to the disk.
Lock files are then instantly deleted as soon as you close the VM. This is done to ensure that it doesn’t interfere with any other service. However, in case of improper shutdown or crashes, these files are left undeleted on your system, which can cause the issue in question.
There are some other reasons and solutions that we will talk about hereinafter. So, without wasting any time let us go to the troubleshooting guide.
Fix Module Disk power on failed on VMWare
If you are seeing “Module Disk Power on Failed” on VMWare, then follow the prescribed solutions to resolve the issue.
- Delete Lock folders
- Troubleshoot in Clean Boot
- Reinstall VMWare
Let us talk about them in detail.
1] Delete Lock folders
As mentioned earlier, the workstation creates a Lock folder which is meant to be deleted as soon as you turn off your Virtual Machine. However, sometimes, you have to delete it manually. We are going to see how to delete Lock or .ilk folders manually. Follow the given steps to do the same.
- Power off your VM.
- Now, we need to go to your directory. If you know the path, just go there, if you don’t know, right-click on your VM and click Open VM directory. You will be redirected to a location in Windows File Explorer.
- Then delete folders with .lck folders.
Finally, restart your computer and check if the issue persists.
2] Troubleshoot in Clean Boot
There are a lot of apps that can interfere with your Virtual Machine. However, there is no way to just play Inki Pinki Ponki and find the right app. That’s why Windows has a utility that allows you to pick the app that’s causing the problem, that is, Clean Boot. You should perform Clean Boot and find out what’s causing the issue and see what’s causing the problem. Then, remove it, and see if the issue persists.
Clean-boot troubleshooting is designed to isolate a performance problem. To perform clean-boot troubleshooting, you must take a number of actions, and then restart the computer after each action. You may need to manually disable one item after another to try and pinpoint the one that is causing the problem. Once you have identified the offender, you can consider removing or disabling it.
3] Reinstall VMWare
If your VMWare app is corrupted, then apart from abrupt crashes, you can also see these sorts of messages. We can easily reinstall the app to resolve the issue. If you are going to uninstall the app, make sure to create a backup, otherwise, your saved data will be wiped up. Uninstall the app, then redownload, reinstall it and check if the issue persists.
Hopefully, these solutions are able to resolve the issue.
How do I power a Virtual Machine in VMWare?
It is quite easy to power on a VM in VMWare. Open the Workstation and go to the VM that you want to open. Finally, click Power on the virtual machine and your VM will be launched. You can also, right-click on your VM and click Power > Power on.
What could cause the VM to fail to power back on?
When you start a Virtual Machine but it fails to power on, there could be multiple reasons responsible for that. Some of thee include file corruption, file locks, Guest OS problems, license problems, network problems, user permission issues, etc.