Jump to content
InsanelyMac Forum
Donk

macOS Unlocker 2.1 for VMware Workstation 11/12/14, Player 7/12/14, Fusion 7/8/10

Recommended Posts

Unlocker 2.1 for latest VMware products.

 

Important message - ESXi 6.x support has been removed from the Unlocker as it is too unreliable. Several methods have been tried but they cause random disconnects of vCenter and failure of the hostd daemon. Support will be added back if and when a reliable method is found.

 

 

Support Request
Please, please, please do NOT copy vmx or log files inline in a post. Always attach the log file as an attachment. It slows down the forum editor and puts a lot of junk in the actual post, and I cannot analyse unless it is a separate file. Alternatively post a link to a Gist.
 
Download Links

Version 2.1.1  - http://www.insanelymac.com/forum/files/file/835-unlocker/

 

Please continue to use version 2.0.8 for ESXi 6.0.

macOS Unlocker for VMware V2.1
==============================

+-----------------------------------------------------------------------------+
| IMPORTANT:                                                                  |
| ==========                                                                  |
|                                                                             |
| Always uninstall the previous version of the Unlocker before using a new    |
| version. Failure to do this could render VMware unusable.                  |
|                                                                             |
+-----------------------------------------------------------------------------+

1. Introduction
---------------

Unlocker 2 is designed for Workstation 11/12/14, Player 7/12/14, 
and Fusion 7/8/10.

If you are using an earlier product please continue using Unlocker 1.

Version 2 has been tested against:

* Workstation 11/12/14 on Windows and Linux
* Workstation Player 7/12/14 on Windows and Linux
* Fusion 7/8/10 on macOS Sierra

The patch code carries out the following modifications dependent on the product
being patched:

* Fix vmware-vmx and derivatives to allow macOS to boot
* Fix vmwarebase .dll or .so to allow Apple to be selected during VM creation
* Download a copy of the latest VMware Tools for macOS

Note that not all products recognise the darwin.iso via install tools menu item.
You will have to manually mount the darwin.iso for example on Workstation 11 and Player 7.

The vmwarebase code does not need to be patched on macOS systems so you will see a
message on those systems telling you that it will not be patched.

In all cases make sure VMware is not running, and any background guests have
been shutdown.

The code is written in Python as it makes the Unlocker easier to run and maintain on ESXi.

2. Prerequisites
----------------

The code requires Python 2.7 to work. Most Linux distros and macOS ship with a compatible
Python interpreter and should work without requiring any additional software.

Windows Unlocker has a packaged version of the Python script using PyInstaller, 
and so does not require Python to be installed.

3. Limitations
--------------

If you are using VMware Player or Workstation on Windows you may get a core dump.

Latest Linux products are OK and do not show this problem.

+-----------------------------------------------------------------------------+
| IMPORTANT:                                                                  |
| ==========                                                                  |
|                                                                             |
| If you create a new VM using version 11, 12 or 13 hardware VMware may stop  |
| and create a core dump. There are two options to work around this issue:    |
|                                                                             |
| 1. Change the VM to be HW 10 - this does not affect performance.            |
| 2. Edit the VMX file and add:                                               |
|    smc.version = "0"                                                        |
|                                                                             |
+-----------------------------------------------------------------------------+

4. Windows
----------
On Windows you will need to either run cmd.exe as Administrator or using
Explorer right click on the command file and select "Run as administrator".

win-install.cmd   - patches VMware
win-uninstall.cmd - restores VMware
win-update-tools.cmd - retrieves latest macOS guest tools

5. Linux
---------
On Linux you will need to be either root or use sudo to run the scripts.

You may need to ensure the Linux scripts have execute permissions
by running chmod +x against the 2 files.

lnx-install.sh   - patches VMware
lnx-uninstall.sh - restores VMware
lnx-update-tools.cmd - retrieves latest macOS guest tools

6. macOS
--------
On macOS you will need to be either root or use sudo to run the scripts.
This is really only needed if you want to use client versions of macOS.

You may need to ensure the macOS scripts have execute permissions
by running chmod +x against the 2 files.

osx-install.sh   - patches VMware
osx-uninstall.sh - restores VMware

7. ESXi
-------
ESXi is no longer supported as there are too many errors on newer versions due to
VMware hardening the ESXi image.
   
8. Thanks
---------

Thanks to Zenith432 for originally building the C++ unlocker and Mac Son of Knife
(MSoK) for all the testing and support.

Thanks also to Sam B for finding the solution for ESXi 6 and helping me with
debugging expertise. Sam also wrote the code for patching ESXi ELF files and
modified the unlocker code to run on Python 3 in the ESXi 6.5 environment.


History
-------
10/10/17 2.1.0 - New version to support ESXi 6.5, Workstation/Player 14 and Fusion 10
               - Removed support for ESXi 6.0
               - Added ESXi boot option to disable unlocker (nounlocker)
11/10/17 2.1.1 - Removed all support for ESXi 6.x


(c) 2011-2017 Dave Parsons

Share this post


Link to post
Share on other sites
Advertisement

Hi. :)

 

Great work! But...

 

After upgrading to Workstation 14 and installing the newly downloaded Darwin-Tools i cannot change my Display Resolution and everything is displayed in HiDPI-Mode...

 

Any suggestions? :)

 

EDIT:

 

Here is a short video of that strange behavior... --> https://youtu.be/4vPYXK3Vimo

Share this post


Link to post
Share on other sites

Hi. :)

 

Great work! But...

 

After upgrading to Workstation 14 and installing the newly downloaded Darwin-Tools i cannot change my Display Resolution and everything is displayed in HiDPI-Mode...

 

Any suggestions? :)

 

EDIT:

 

Here is a short video of that strange behavior... --> https://youtu.be/4vPYXK3Vimo

 

You could try :

sudo defaults write /Library/Preferences/com.apple.windowserver DisplayResolutionEnabled -bool NO

Share this post


Link to post
Share on other sites

Hi.

Thanks for the hard work, but I have an issue.

After applying the unlocker 210 I still doesn't have "Apple Mac OS X" to be selected during VM creation. 

Do you have any suggestions what is the problem?

Thanks

 

 

18947114.png

 

 

UPD: added an image

Share this post


Link to post
Share on other sites

Hi.

Thanks for the hard work, but I have an issue.

After applying the unlocker 210 I still doesn't have "Apple Mac OS X" to be selected during VM creation. 

Do you have any suggestions what is the problem?

Thanks

Did you uninstalled v2.0.8 first? 

 

You could try to uninstall v2.1 und reinstall it again... maybe this helps... :)

Share this post


Link to post
Share on other sites

There have been reports of issues still with ESXi 6.5 and so I think I will remove support for ESXi for now. I will release a new version with the ESXi stuff removed. VMware are quite clearly locking ESXi down and so this is getting harder to support.

 

If anyone can find a solution please let us now but I don't wanttthe responsibility of screwing up an ESXi host. 2.1.1 will be released later today.

Share this post


Link to post
Share on other sites
Hi, thanks for you hard working, this tool is good. But on esxi 6.5u1 have some issues.

1.The "hostd" demon have panic "NOT_IMPLEMENTED bora/vim/hostd/hostsvc/provider/vmkernel/SecurityDomainProviderImpl.cpp" periodically and server disconnect from dataceter by few minutes. But on previous version esxi this issue don't reproduce. I tried reinstall esxi, but it didn't help when I upgraded esxi to 6.5u1.

2.And second issue, after server reboots, not always the "hostd" demon automatic starts. It reproduce on each build esxi 6.5. This problem isn't so important,just for you information.

 

Thanks for any help

log.tar

Share this post


Link to post
Share on other sites

 

Hi, thanks for you hard working, this tool is good. But on esxi 6.5u1 have some issues.
1.The service "hostd" have panic "NOT_IMPLEMENTED bora/vim/hostd/hostsvc/provider/vmkernel/SecurityDomainProviderImpl.cpp" periodically and server disconnect from dataceter by few minutes. But on previous version esxi this issue don't reproduce. I tried reinstall esxi but it didn't help when I upgraded esxi to 6.5u1.
2.And second issue, after host reboots, not always service "hostd" automatic starts. It reproduce on each build esxi 6.5. This problem is not so important,just for you information.
 
Thanks for any help

 

 

Yes those are the issue so I am sorry to say that I am withdrawing support for ESXi for now. Some folks do this on production systems and I am not happy being responsible for any issues.

Share this post


Link to post
Share on other sites

 

You could try :

sudo defaults write /Library/Preferences/com.apple.windowserver DisplayResolutionEnabled -bool NO

 

Great! :-) That did the trick. Many thx!

Share this post


Link to post
Share on other sites

Worked for me too...  Thanks so much.

I just went into settings --> Display --> and turned off "Display Scaling" and that worked also without having to use any commands.

Share this post


Link to post
Share on other sites

Hello everybody.

 

I also get the panics at boot with Workstation 14.0.0 build-6661328 / Windows Pro 10 - x64

 

OSX is 10.13 downloaded & converted to iso a on October 10. 2017.

 

Edit: Patcher 2.1.1

Share this post


Link to post
Share on other sites

Hello everybody.

 

I also get the panics at boot with Workstation 14.0.0 build-6661328 / Windows Pro 10 - x64

 

OSX is 10.13 downloaded & converted to iso a on October 10. 2017.

 

Edit: Patcher 2.1.1

 

How did you create the ISO? Panics ae usually due to incorrect conversions. Or do you have an AMD CPU which is not natively supported by macOS.

Share this post


Link to post
Share on other sites

Great! :-) That did the trick. Many thx!

Mine still jumps back to 794x568 (HiDPI).. :(

Nor the command or systempref. helps.

Had no problem with unlocker 2.0.9, untill updated to 2.1.1 and installed the new darwin.

Share this post


Link to post
Share on other sites

The unlocker won't have done this but it is likely the tools. Get the previous tools and trying replacing them.

Share this post


Link to post
Share on other sites

Mine still jumps back to 794x568 (HiDPI).. :(

Nor the command or systempref. helps.

Had no problem with unlocker 2.0.9, untill updated to 2.1.1 and installed the new darwin.

 

Same problem with another resolution

i used the 2.1.0 (link on the fist page don't point to the 2.1.1)

 

 

EDIT: tried with unlocker209-unofficial and now it's work :)

Share this post


Link to post
Share on other sites

Mine still jumps back to 794x568 (HiDPI).. :(

Nor the command or systempref. helps.

Had no problem with unlocker 2.0.9, untill updated to 2.1.1 and installed the new darwin.

 

defaults write ~/Library/Preferences/com.vmware.tools.plist enableAutoHiDPI -bool false

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.



×