<link href="https://fonts.googleapis.com/css?family=Roboto:100,100italic,200,200italic,300,300italic,400,400italic,500,500italic,600,600italic,700,700italic,800,800italic,900,900italic&amp;display=swap" rel="stylesheet"/>
1 minute reading time (259 words)

SOLVED: macOS VMware Virtual Machine won't start, stuck in a boot loop

SOLVED: macOS VMware Virtual Machine is stuck in a boot loop. Check the VMware workstation log and install the latest version of macOS Unlocker.

Problem: macOS VM wont start, stuck in a boot loop

macOS VMware Virtual Machine is stuck in a boot loop. The Apple logo appears but macOS won't load and the VM automatically restarts.

VMware workstation 17, Windows 11

Troubleshooting steps:

Check the VMware workstation log

Check the VMware workstation log for errors
C:\Users\Username\Documents\Virtual Machines\VM-Name\vmware.log

In this case, we saw the following errors in the log:

vmx GuestRpcSendTimedOut: message to toolbox-dnd timed out
vcpu-0 Chipset: The guest has requested that the virtual machine be hard reset
vcpu-0 DEVICE: Resetting device 'ALL'.
vcpu-1 SMC_Open: Unable to open MacHALDriver: 0x00000002.

vcpu-1 SMC_Open: Unable to open MacHALDriver: 0x00000002

This error indicates an issue with the Mac Hardware Abstraction Layoer (HAL) driver. This is a core driver that allows the macOS VM to work with the VMware virtual hardware so this is most likely the reason it wont boot up.

Solution: Reinstall or update macOS Unlocker

Reinstalling or updating macOS unlocker should fix the HAL driver problem.

When I had this issue, reinstalling the same version of macOS unlocker fixed it. If that doesnt work, try updating macOS unlocker to the latest version.

Close VMware workstation


Download and install the latest version of macOS unlocker from GitHub
https://github.com/paolo-projects/unlocker/releases

Related Posts

 

Comments 9

Guest - David on Wednesday, 21 December 2022 15:00

I have tried this with updating the unlocker, but I think it is the same version I already had.

I have a snapshot with it up and running, but when I reboot it does the perpetual showing the Apple logo and then restarting over and over.

I am running VMWare Workstation 17 and I am trying to work with MacOS Monterey.

Here is what I think is the relevant snippet from the VMWare log:

2022-12-21T14:54:52.331Z Wa(03) vmx Can't set WSS, error 1314
2022-12-21T14:54:52.331Z In(05) vmx VerificationOfHostParameters status 1
2022-12-21T14:54:52.331Z Wa(03) vmx VMX can't verify host parameters.
2022-12-21T14:54:52.332Z In(05) vmx FeatureCompat: No EVC masks.

I have tried this with updating the unlocker, but I think it is the same version I already had. I have a snapshot with it up and running, but when I reboot it does the perpetual showing the Apple logo and then restarting over and over. I am running VMWare Workstation 17 and I am trying to work with MacOS Monterey. Here is what I think is the relevant snippet from the VMWare log: 2022-12-21T14:54:52.331Z Wa(03) vmx Can't set WSS, error 1314 2022-12-21T14:54:52.331Z In(05) vmx VerificationOfHostParameters status 1 2022-12-21T14:54:52.331Z Wa(03) vmx VMX can't verify host parameters. 2022-12-21T14:54:52.332Z In(05) vmx FeatureCompat: No EVC masks.
Guest - David on Wednesday, 21 December 2022 15:22

The fix for me using VMWare Worsktation 17 was to download the latest unlocker which is version 4 from here:

https://github.com/DrDonk/unlocker

The fix for me using VMWare Worsktation 17 was to download the latest unlocker which is version [b]4[/b] from here: https://github.com/DrDonk/unlocker
TechLabs on Wednesday, 21 December 2022 16:58

Great, glad you got it working

Great, glad you got it working :D
Guest - David on Wednesday, 21 December 2022 17:52

Definitely cannot get Ventura working without a reboot loop though, and after scouring the internet I can see that it seems to be impossible. (With Ryzen processor)

Definitely cannot get Ventura working without a reboot loop though, and after scouring the internet I can see that it seems to be impossible. (With Ryzen processor)
TechLabs on Thursday, 22 December 2022 15:55

Hi again, my host machine has an Intel processor. Unfortunately, I don’t have an AMD machine to do any testing with. Sorry I cant be of more help

Hi again, my host machine has an Intel processor. Unfortunately, I don’t have an AMD machine to do any testing with. Sorry I cant be of more help :(
Guest - unknown on Saturday, 24 June 2023 07:53

same problem

same problem
Guest - Bub on Wednesday, 15 February 2023 19:14

Thanks for you hard work!!! This works for me and cured my major headache!

Thanks for you hard work!!! This works for me and cured my major headache!:D
TechLabs on Saturday, 29 April 2023 12:53

Hey, glad you got it working!

Hey, glad you got it working!
Guest - Ninad Chitre on Sunday, 07 January 2024 19:54

Hi,

What a life saver! I got a new laptop. I brought the vmware player 17 and vms from old machine's backup. The hardware had changed, so I had to repair the vmware player. But I didn't re-apply the patch. That caused the bootloop with the guest osX requesting a hard reset. I was about to abandon the vm instance. But a last minute googling led me to this article. I repatched the player and everything is hunky dory. :-) Yaay !!

Thank you so much!

-Ninad
[Mr Ninad Chitre]

Hi, What a life saver! I got a new laptop. I brought the vmware player 17 and vms from old machine's backup. The hardware had changed, so I had to repair the vmware player. But I didn't re-apply the patch. That caused the bootloop with the guest osX requesting a hard reset. I was about to abandon the vm instance. But a last minute googling led me to this article. I repatched the player and everything is hunky dory. :-) Yaay !! Thank you so much! -Ninad [Mr Ninad Chitre]
Already Registered? Login Here
Sunday, 27 April 2025
You can help support this website by buying me a coffee!
Buy Me A Coffee