After VMware is abnormally shut down, it prompts "Failed to lock this configuration file exclusively" when it is restarted! ! ! A few days ago, when I was using a VMware virtual machine, the virtual machine suddenly froze. I shut down my computer and restarted it. When I opened the virtual machine again, an exception message appeared saying "Failed to exclusively lock this configuration file", and an abnormal process in the background was seriously occupying the CPU. After checking various statements online, it turned out that the virtual machine was not shut down normally, and a process was still running in the background and occupying the configuration file, which caused an abnormal prompt when the machine was turned on again. Solution 1 given by netizens: Kill all VMware processes through Task Manager and then restart them: However, when ending the process, it prompts "Access Denied", and even using the cmd command line to force kill the process, these processes cannot be ended. This method fails! ! Solution 2: Restore normal startup by deleting temporary files in the virtual machine installation directory: After trying this method, although the temporary files were deleted, it still could not start normally. This method failed! ! Found solution 3: end the old process occupation by disabling the startup item, and finally solved it! ! 1. Press the "win + R" key combination to enter "Run". 2. Type "msconfig" (without quotation marks, you can copy it directly) and press Enter. 3. Go to "System Configuration", select "Services", check "Hide all Microsoft services" in the lower left corner, then click "Disable all", and click "Apply". 4. Then open the "Start" option next to "Service" and open "Click Task Manager". 5. Among the listed startup items, find VMware, right-click, and select "Disable" to disable all startup items. 6. Close the "Task Manager", return to the "System Configuration" interface, click "OK", and restart the computer according to the prompts. 7. After the computer restarts, start all services again according to the above process, and VMware can start normally; This is the end of this article about how to solve the problem when VMware virtual machine prompts "Failed to exclusively lock this configuration file". For more information about VMware locking configuration files exclusively, please search for previous articles on 123WORDPRESS.COM or continue to browse the following related articles. I hope you will support 123WORDPRESS.COM in the future! You may also be interested in:
|
<<: Comprehensive understanding of Node event loop
>>: MySQL 8.0.19 installation and configuration tutorial under Windows 10
Table of contents initialization initState() init...
I have previously introduced to you the configura...
This article shares the specific code of js to ac...
Configuration Example upstream backend { server b...
Table of contents Row-Column Conversion Analyze t...
Common nmcli commands based on RHEL8/CentOS8 # Vi...
This article example shares the specific code of ...
This article shares the specific code of jQuery t...
Table of contents Why optimize? ? Where to start?...
<br />First of all, I have to state that I a...
Table of contents Code cleaning "Frames"...
background Getting the slow query log from mysql....
Table of contents Preface optimization Derivative...
Table of contents Preface Related Materials Achie...
Error message: Job for mysqld.service failed beca...