starred/unlocker

Fork 0

mirror of https://github.com/DrDonk/unlocker.git synced 2026-04-26 06:06:01 +03:00

[GH-ISSUE #6] Unlocker V4.0 does not work for VMware Workstation Pro v16.2.1.18811642 #5

New issue

Closed

opened 2026-03-02 03:57:33 +03:00 by kerem · 7 comments

kerem commented

2026-03-02 03:57:33 +03:00

Owner

Originally created by @AEROBATlCS on GitHub (Jan 13, 2022).
Original GitHub issue: https://github.com/DrDonk/unlocker/issues/6

Hello Friend! For some reason your solution doesn't work for VMware Workstation Pro v16.2.1.18811642 and earlier builds of version 16. Why is this happening? A message about the guest operating system pops up. AMD 5950X.
smc.version = "0" presented.
I understand this message (The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.) is caused by VMware software? Does it depend on the mounted disk image?

Originally created by @AEROBATlCS on GitHub (Jan 13, 2022). Original GitHub issue: https://github.com/DrDonk/unlocker/issues/6 Hello Friend! For some reason your solution doesn't work for VMware Workstation Pro v16.2.1.18811642 and earlier builds of version 16. Why is this happening? A message about the guest operating system pops up. AMD 5950X. smc.version = "0" presented. I understand this message (**The CPU has been disabled by the guest operating system. Power off or reset the virtual machine**.) is caused by VMware software? Does it depend on the mounted disk image?

kerem

2026-03-02 03:57:33 +03:00

closed this issue
added the
wontfix
label

kerem commented

2026-03-02 03:57:34 +03:00

Author

Owner

@DrDonk commented on GitHub (Jan 16, 2022):

This is because you are using an AMD CPU which native macOS does not support. The patches cannot fix this and you will need to look for macOS patches to run it on AMD.

You could ask here https://amd-osx.com/

@DrDonk commented on GitHub (Jan 16, 2022): This is because you are using an AMD CPU which native macOS does not support. The patches cannot fix this and you will need to look for macOS patches to run it on AMD. You could ask here https://amd-osx.com/

kerem commented

2026-03-02 03:57:34 +03:00

Author

Owner

@AEROBATlCS commented on GitHub (Jan 17, 2022):

This is because you are using an AMD CPU which native macOS does not support. The patches cannot fix this and you will need to look for macOS patches to run it on AMD.

Ready! Works fine!
Created a question with a description of the solution.
https://qna.habr.com/q/1100816

@AEROBATlCS commented on GitHub (Jan 17, 2022): > This is because you are using an AMD CPU which native macOS does not support. The patches cannot fix this and you will need to look for macOS patches to run it on AMD. Ready! Works fine! Created a question with a description of the solution. https://qna.habr.com/q/1100816

kerem commented

2026-03-02 03:57:34 +03:00

Author

Owner

@DrDonk commented on GitHub (Jan 17, 2022):

OK I was not aware that there was still an issue with the SMC setting. It is not something I can patch but I will add a note back into the readme about this workaround.

I am interested in what you used for the AMD CPU. Was it a specific macOS kernel patch or OCLP?

@DrDonk commented on GitHub (Jan 17, 2022): OK I was not aware that there was still an issue with the SMC setting. It is not something I can patch but I will add a note back into the readme about this workaround. I am interested in what you used for the AMD CPU. Was it a specific macOS kernel patch or OCLP?

kerem commented

2026-03-02 03:57:34 +03:00

Author

Owner

@DrDonk commented on GitHub (Jan 19, 2022):

I will add some notes explaining changing the SMC version.

@DrDonk commented on GitHub (Jan 19, 2022): I will add some notes explaining changing the SMC version.

kerem commented

2026-03-02 03:57:34 +03:00

Author

Owner

@AEROBATlCS commented on GitHub (Jan 20, 2022):

I cannot say. These are just guesses. I can't say for sure.

@AEROBATlCS commented on GitHub (Jan 20, 2022): I cannot say. These are just guesses. I can't say for sure.

kerem commented

2026-03-02 03:57:35 +03:00

Author

Owner

@DrDonk commented on GitHub (Jan 20, 2022):

OK, well thanks for pointing me to the web page.

@DrDonk commented on GitHub (Jan 20, 2022): OK, well thanks for pointing me to the web page.

kerem commented

2026-03-02 03:57:35 +03:00

Author

Owner

@BKdilse commented on GitHub (Feb 3, 2022):

I can confirm that the following worked for me on an AMD Ryzen 3900x, adding to the VMX:

cpuid.0.eax = "0000:0000:0000:0000:0000:0000:0000:1011"
cpuid.0.ebx = "0111:0101:0110:1110:0110:0101:0100:0111"
cpuid.0.ecx = "0110:1100:0110:0101:0111:0100:0110:1110"
cpuid.0.edx = "0100:1001:0110:0101:0110:1110:0110:1001"
cpuid.1.eax = "0000:0000:0000:0001:0000:0110:0111:0001"
cpuid.1.ebx = "0000:0010:0000:0001:0000:1000:0000:0000"
cpuid.1.ecx = "1000:0010:1001:1000:0010:0010:0000:0011"
cpuid.1.edx = "0000:0111:1000:1011:1111:1011:1111:1111"

@BKdilse commented on GitHub (Feb 3, 2022): I can confirm that the following worked for me on an AMD Ryzen 3900x, adding to the VMX: ``` cpuid.0.eax = "0000:0000:0000:0000:0000:0000:0000:1011" cpuid.0.ebx = "0111:0101:0110:1110:0110:0101:0100:0111" cpuid.0.ecx = "0110:1100:0110:0101:0111:0100:0110:1110" cpuid.0.edx = "0100:1001:0110:0101:0110:1110:0110:1001" cpuid.1.eax = "0000:0000:0000:0001:0000:0110:0111:0001" cpuid.1.ebx = "0000:0010:0000:0001:0000:1000:0000:0000" cpuid.1.ecx = "1000:0010:1001:1000:0010:0010:0000:0011" cpuid.1.edx = "0000:0111:1000:1011:1111:1011:1111:1111" ```