Proxmox/Hyper-V/VMware

Taking ownership of a VM failed: The virtual machine appears to be in use

VMware Workstation Pro is the industry standard for running multiple operating systems as virtual machines (VMs) on a single Linux or Windows PC. IT professionals, developers, and businesses who build, test, or demo software for any device, platform, or cloud rely on Workstation Pro. VMware Workstation Pro allows you to run multiple virtual machines, OCI containers, and Kubernetes clusters at once on the same Windows or Linux PC. Create fully featured and securely isolated Linux and Windows VMs and other desktop servers, and cloud environments, complete with configurable virtual networking and network condition simulation, for use in code development, solution architecting, application testing, product demonstrations, and more. Here are some similar VM errors, the virtual machine has terminated unexpectedly during startup with exit code 1 (1×0), and Windows failed to start, a recent hardware or software change might be the cause.

VMware Workstation runs on standard x86-based hardware with 64-bit Intel and AMD processors, and on 64-bit Windows or Linux host operating systems. For more detail, see our System Requirements documentation.

Root cause: You are trying to open another VM console while there is actually one running and open or there are lockfiles or lockdirs. To fix this issue, kindly follow the steps discussed below.

Method 1: You already have an open console and you are trying to open a new one:

Even you you try to take ownership, it will fail with the following error below.

Just search for an open VM session from the taskbar. This will open the Virtual Machine window

Method 2: The lockfiles or lockdirs: If the above method does not work for you, please try the following method as suggested below. See these guides on some related contents: How to fix VirtualBox Displaying only 32 bits Option, and how to enable Hyper-V on a VMware Workstation.

- Exit (close) the VMware Workstation
- Find and delete all files with the extension .lck or .lock in the directory of the VM that is causing this trouble
- Try to start the VM again.

I welcome you to subscribe to my YouTube Channel. I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x