Bobcares

“Taking ownership of this virtual machine failed” Vmware Error

by | Feb 6, 2025

Learn how to fix the “Taking ownership of this virtual machine failed” VMware error. Our VMware Support team is here to help you with your questions and concerns.

“Taking ownership of this virtual machine failed” Vmware Error

“Taking ownership of this virtual machine failed” Vmware ErrorThe following error message usually pops up when moving or copying a virtual machine, after a power failure on the host, or if the virtual machine becomes corrupted.

Taking ownership of this virtual machine failed.

To prevent power-related issues, ensure that the hypervisor’s host machine is equipped with an uninterrupted power supply (UPS) and a RAID system with battery backup.

Here are some of the causes behind the “Take Ownership” error:

  • VMware locks certain VM files (`.vmdk`, `.vmx`, etc.) while in use to prevent conflicts.
  • If the VM or host shuts down unexpectedly, file locks may not be released correctly.
  • Two users or processes attempting to access the same VM simultaneously.
  • Sometimes, lock files persist even after a VM has been shut down properly, leading to ownership errors.

How to Fix the “Take Ownership” Error

To resolve this error, we need to remove lock files from the VM storage directory manually.

  1. Pause or power off any running virtual machines inside the VMware Workstation.
  2. Now, it is time to end the VMware processes:
    1. Open Task Manager by pressing `CTRL + ALT + DEL`.
    2. Then, go to the Details tab (Windows 8/10) or the Processes tab (Windows 7 and earlier).
    3. Look for `vmware-tray.exe` in the list of running tasks.
    4. Select `vmware-tray.exe`, then press `DEL` to end the process.
  3. Then, go to the folder containing the problematic virtual machine.
  4. Look for any `.lck` or `.lock` files and folders.
  5. Hold `CTRL` and left-click to select these files/folders.
  6. Right-click one of the selected items and choose Cut.
  7. Now, create a new folder named Temp inside the VM directory.
  8. Then, right-click inside Temp and select Paste to move the lock files there.
  9. Next, click Start, then type `VMware Workstation`.
  10. Select VMware Workstation Pro from the list.
  11. If the application does not open in full screen, locate the VMware Workstation icon in the system tray and double-click it.
  12. Locate the problematic virtual machine and attempt to start it.

At this point, our virtual machine should start successfully.

Best Practices to Prevent “Take Ownership” Errors

  • Avoid forcefully powering off virtual machines or shutting down the host abruptly.
  • Use monitoring scripts or manually check for file locks if frequent issues arise.
  • Prevent multiple users from modifying the same VM simultaneously to avoid ownership conflicts.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to fix the “Taking ownership of this virtual machine failed” VMware error,

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF