# Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2

vmware unlocker

669 replies to this topic

### #1 Donk Posted 13 December 2014 - 04:27 PM

Donk

InsanelyMac Deity

• Members
• 2,321 posts
• Gender:Male
• Location:Manchester UK

POPULAR

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.

InsanelyMac: http://www.insanelym...e/339-unlocker/

14/11/15 - Version 2.0.8
• Player 12 on Linux fixes
• Get latest VMware tools command
• Removed firmware files
• Moved to PyInstaller 3.0

16/09/15 - Version 2.0.7

• Workstation 12 on Linux fixes

20/06/15 - Version 2.0.6

• ESXi 6 patch for smcPresent vCenter compatibility. Thanks Sam!

18/06/15 - Version 2.0.5

ESXi 6 work was greatly helped by Sam B. Thanks to Sam for helping me out and finding the last piece of the puzzle.

• ESXi 6 working
• Latest tools from Fusion 7.1.2

24/01/15 - Version 2.0.4

Couple of quick fixes:

• Added stop and start of VMware View USB Service to Windows batch files
• Fixed broken GOS Table patching on Linux

03/01/15 - Version 2.0.3

Added new EFI firmware files to remove Server check for 10.5 and 10.6.

If you are using a 32-bit installation of OS X:

1. Copy efi32-srvr.rom to guest folder.
2. Edit the vmx file and add:

efi32.filename = "efi32-srvr.rom"

If you are using a 64-bit installation of OS X:

1. Copy efi64-srvr.rom to guest folder.
2. Edit the vmx file and add:

efi64.filename = "efi64-srvr.rom"

14/12/14 - Version 2.0.2

Uploaded a new version, 2.0.2, which removes need for Python on Windows. Packaged using PyInstaller. If you have already used 2.0.0 successfully then you do not need this as there are no other changes. Also added darwin.iso back into the zip file.

http://www.insanelym...e/339-unlocker/

Mac OS X Unlocker for VMware V2.0
=================================

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

Unlocker 2 is designed for Workstation 11, Player 7, ESXi 6 and Fusion 7.

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

Version 2 has been tested against:

* Workstation 11/12 on Windows and Linux
* Player 7 & Workstation Player 12 on Windows and Linux
* Fusion 7/8 on Mavericks and Yosemite
* ESXi 6.0

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

* Fix vmware-vmx and derivatives to allow Mac OS X to boot
* Fix vmwarebase .dll or .so to allow Apple to be selected during VM creation
* Fix libvmkctl.so on ESXi 6 to allow use with vCenter
* Download a copy of the latest VMware Tools for OS X

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 OS X or ESXi 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 now Python as it makes the Unlocker easier to run and maintain on ESXi.
There are some challenges to write the code as ESXi has a subset of Python 2.7 which
constrains some modules that can be used.

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

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

Windows 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 and ESXi products are OK and do not show this problem.

+-----------------------------------------------------------------------------+
| IMPORTANT:                                                                  |
| ==========                                                                  |
|                                                                             |
| If you create a new VM using version 11 or 12 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 OS X 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 OS X guest tools

6. Mac OS X
-----------
On Mac OS X 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 Mac OS X.

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

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

7. ESXi
-------
You will need to transfer the zip file to the ESXi host either using vSphere client or SCP.

Once uploaded you will need to either use the ESXi support console or use SSH to
run the commands. Use the unzip command to extract the files.

<<< WARNING: use a datastore volume to run the scripts >>>

Please note that you will need to reboot the host for the patches to become active.
The patcher is embbedded in a shell script local.sh which is run at boot from /etc/rc.local.d.

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

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

Note:
1. Any changes you have made to local.sh will be lost. If you have made changes to
that file, you will need to merge them into the supplied local.sh file.
2. The unlocker runs at boot time to patch the relevant files and it now survives
an upgrade or patch to ESXi as local.sh is part of the persisted local state.

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.

History
-------
12/12/14 2.0.0 - First release
13/13/14 2.0.1 - Removed need for Python for Windows
13/13/14 2.0.2 - darwin.iso was missing from zip file
02/01/15 2.0.3 - Added EFI firmware files to remove Server check
- Refactored Python code
07/01/15 2.0.4 - Added View USB Service to Windows batch files
- Fixed broken GOS Table patching on Linux
18/06/15 2.0.5 - ESXi 6 working
- Latest tools from Fusion 7.1.2
20/06/15 2.0.6 - ESXi 6 patch for smcPresent vCenter compatibility
16/09/15 2.0.7 - Workstation 12 on Linux fixes
14/11/15 2.0.8 - Player 12 on Linux fixes
- Get latest VMware tools command
- Removed firmware files
- Moved to PyInstaller 3.0

(c) 2011-2015 Dave Parsons

### #2 MSoK Posted 13 December 2014 - 05:24 PM

MSoK

InsanelyMac Legend

• Members
• 1,082 posts
• Gender:Male
• Location:Birmingham (UK)

Reserved

### #3 virge Posted 13 December 2014 - 06:15 PM

virge

InsanelyMac Protégé

• Members
• 2 posts

Completely removd VMWare Workstaition 11, deleted vmware folder, ran ccleaner, rebooted.

Installed VMWare 11 to default dir c:\program files x86\vmware

Installed Python 2.7.to c:\program files x86\vmware\phython

Ran the win-install.cmd to path vmware

Rebooted

When trying to launch OS X 10.10 Yosemite for vmware for Windows 8.1 x64, it stalls half way though the launch to the desktop.

After inspecting the console window, it cannot find python.  The readme states "The python.exe file must be on the executable PATH. If it is not on PATH please
edit win-install.cmd to point to the installation path", what do i change in the win-install.cmd to reflect the path that python has been installed to ?  I'm not a programmer, and not sure what to change/edit in the .cmd file.

Thanks very much for releasing this update. Will report back once it's working.

### #4 Hundley Posted 13 December 2014 - 06:39 PM

Hundley

InsanelyMac Protégé

• Members
• 19 posts
• Gender:Male
• Location:Utah, USA

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

Would you expect a Python wrapper such as py2exe to work?  Maybe somebody can confirm if they've had success with this method...

### #5 ZhuangJW Posted 13 December 2014 - 06:42 PM

ZhuangJW

InsanelyMac Protégé

• Members
• 22 posts
• Gender:Male
• Location:China

Completely removd VMWare Workstaition 11, deleted vmware folder, ran ccleaner, rebooted.

Installed VMWare 11 to default dir c:\program files x86\vmware

Installed Python 2.7.to c:\program files x86\vmware\phython

Ran the win-install.cmd to path vmware

Rebooted

When trying to launch OS X 10.10 Yosemite for vmware for Windows 8.1 x64, it stalls half way though the launch to the desktop.

After inspecting the console window, it cannot find python.  The readme states "The python.exe file must be on the executable PATH. If it is not on PATH please
edit win-install.cmd to point to the installation path", what do i change in the win-install.cmd to reflect the path that python has been installed to ?  I'm not a programmer, and not sure what to change/edit in the .cmd file.

Thanks very much for releasing this update. Will report back once it's working.

When you install the Python , you can chose the "Entire feature will be installed on local hard driver" in "Add python.exe to Path " . And root your computer . the Python will be OK .

### #6 Hundley Posted 13 December 2014 - 06:53 PM

Hundley

InsanelyMac Protégé

• Members
• 19 posts
• Gender:Male
• Location:Utah, USA

After inspecting the console window, it cannot find python.  The readme states "The python.exe file must be on the executable PATH. If it is not on PATH please

edit win-install.cmd to point to the installation path", what do i change in the win-install.cmd to reflect the path that python has been installed to ?  I'm not a programmer, and not sure what to change/edit in the .cmd file.

You have two options:

1) Modify win-install.cmd to point to your Python installation - you must edit Line 40 where it says "python.exe vmxsmc.py" to point to the location that you installed Python on your system:

(e.g. change the line to "path\to\python.exe vmxsmc.py")

2) Edit Windows' PATH environment variable to include your Python installation:

Right click on My Computer / This PC -> Properties -> Advanced System Settings -> Environment Variables... -> find "Path" in the top pane and click Edit... -> add the path to python.exe where you installed it on your system, separated from the existing paths by a semicolon. (e.g. "C:\path\to\python\installation\") - but only to the folder containing the executable, don't add python.exe itself to the path.

### #7 Donk Posted 13 December 2014 - 06:54 PM

Donk

InsanelyMac Deity

• Members
• 2,321 posts
• Gender:Male
• Location:Manchester UK

Would you expect a Python wrapper such as py2exe to work?  Maybe somebody can confirm if they've had success with this method...

I will be looking at this next. There was a decision to release it as-is now to allow some degree of functionality to be available to those who want it. The thread is in this forum on the unlocker status.

InsanelyMac Protégé

• Members
• 2 posts

hi im on linux , should be newest python availabe, i get errors using the install script

VMware Unlocker 2.0.0
===============================
Creating backup folder...
‘/usr/lib/vmware/bin/vmware-vmx’ -> ‘./backup/vmware-vmx’
‘/usr/lib/vmware/bin/vmware-vmx-debug’ -> ‘./backup/vmware-vmx-debug’
‘/usr/lib/vmware/bin/vmware-vmx-stats’ -> ‘./backup/vmware-vmx-stats’
‘/usr/lib/vmware/lib/libvmwarebase.so.0/libvmwarebase.so.0’ -> ‘./backup/libvmwarebase.so.0’
Patching...
File "./vmxsmc.py", line 66
print '+LKS Memcpy: 0x' + lks_cpy.encode('hex')
^
SyntaxError: invalid syntax

after that, nothing seems to be unlocked

have a nice day to everybody

### #9 Donk Posted 13 December 2014 - 07:15 PM

Donk

InsanelyMac Deity

• Members
• 2,321 posts
• Gender:Male
• Location:Manchester UK

hi im on linux , should be newest python availabe, i get errors using the install script

VMware Unlocker 2.0.0
===============================
Creating backup folder...
‘/usr/lib/vmware/bin/vmware-vmx’ -> ‘./backup/vmware-vmx’
‘/usr/lib/vmware/bin/vmware-vmx-debug’ -> ‘./backup/vmware-vmx-debug’
‘/usr/lib/vmware/bin/vmware-vmx-stats’ -> ‘./backup/vmware-vmx-stats’
‘/usr/lib/vmware/lib/libvmwarebase.so.0/libvmwarebase.so.0’ -> ‘./backup/libvmwarebase.so.0’
Patching...
File "./vmxsmc.py", line 66
print '+LKS Memcpy: 0x' + lks_cpy.encode('hex')
^
SyntaxError: invalid syntax

after that, nothing seems to be unlocked
have a nice day to everybody

What Linux distro? And what is the output of python -V from the terminal?

### #10 ZhuangJW Posted 13 December 2014 - 07:26 PM

ZhuangJW

InsanelyMac Protégé

• Members
• 22 posts
• Gender:Male
• Location:China

It is stop in Boot Manager .

I was used the *.dmg .

hi im on linux , should be newest python availabe, i get errors using the install script

VMware Unlocker 2.0.0
===============================
Creating backup folder...
‘/usr/lib/vmware/bin/vmware-vmx’ -> ‘./backup/vmware-vmx’
‘/usr/lib/vmware/bin/vmware-vmx-debug’ -> ‘./backup/vmware-vmx-debug’
‘/usr/lib/vmware/bin/vmware-vmx-stats’ -> ‘./backup/vmware-vmx-stats’
‘/usr/lib/vmware/lib/libvmwarebase.so.0/libvmwarebase.so.0’ -> ‘./backup/libvmwarebase.so.0’
Patching...
File "./vmxsmc.py", line 66
print '+LKS Memcpy: 0x' + lks_cpy.encode('hex')
^
SyntaxError: invalid syntax

after that, nothing seems to be unlocked

have a nice day to everybody

The python version error , you should used the version 2.7.* , not is 3.*

### #11 Donk Posted 13 December 2014 - 07:30 PM

Donk

InsanelyMac Deity

• Members
• 2,321 posts
• Gender:Male
• Location:Manchester UK

It is stop in Boot Manager .
I was used the *.dmg .

The python version error , you should used the version 2.7.* , not is 3.*

Of course, the encode issue in Python 3. Again something for next release to fix. Hopefully will sort out fixes quickly.

### #12 dbali Posted 13 December 2014 - 07:33 PM

dbali

InsanelyMac Protégé

• Members
• 1 posts

Of course, the encode issue in Python 3. Again something for next release to fix. Hopefully will sort out fixes quickly.

Yeap. I got it on Arch Linux where Python defaults 3.4.2 Changing the install script from "python" to "python2" did the trick.

### #13 ZhuangJW Posted 13 December 2014 - 07:42 PM

ZhuangJW

InsanelyMac Protégé

• Members
• 22 posts
• Gender:Male
• Location:China

Hey , I meet a  problem about , the unsuccessful.tual SCSI CDROM Drive (0.0) . And the next the VM will going in the Boot Manager .

An the end , I came the Boot Manager ->EFI Internal Shell , I saw blk0 and blk1 is (null) .

What should I do ?

InsanelyMac Protégé

• Members
• 2 posts

changing to python2 did the trick, thx

### #15 virge Posted 14 December 2014 - 02:46 AM

virge

InsanelyMac Protégé

• Members
• 2 posts

I can confirm it now works perfectly, the trick was to check "Add phython.exe to path" during the install.  Thank you Donk for this, you made my day.

### #16 lenix Posted 14 December 2014 - 09:54 AM

lenix

InsanelyMac Protégé

• Members
• 7 posts

Thanks for the unlocker, everything works well for me on workstation

### #17 mcobold Posted 14 December 2014 - 11:11 AM

mcobold

InsanelyMac Protégé

• Members
• 4 posts

At first I like to thank you for a great Job. I'm only an interested user, not a programmer. This may explain my question. I have a WS11 running on Windows 8.1. I installed python 2.7. The path to python now is

C:\Program Files (x86)\Python27\python.exe

In the next step I tried to change the path in the win-install.cmd to C:\Program Files (x86)\Python27\

When I start the win-install.cmd I always see something like "the command C.\Program is wrong written..."

What is my failure?

### #18 Donk Posted 14 December 2014 - 11:25 AM

Donk

InsanelyMac Deity

• Members
• 2,321 posts
• Gender:Male
• Location:Manchester UK

Uploaded a new version, 2.0.1, which removes need for Python on Windows. Packaged using PyInstaller. If you have already used 2.0.0 successfully then you do not need this as there are no other changes.

http://www.insanelym...0-unlocker-201/

### #19 trungpt Posted 14 December 2014 - 12:12 PM

trungpt

InsanelyMac Geek

• Members
• 107 posts
• Gender:Male
• Location:Earth
• Interests:Insanelymac

Thanks God we have you to play with MacOSX on Windows or Linux.

Edit: v2.0.1 is missing the Darwin.iso file

### #20 ZhuangJW Posted 14 December 2014 - 12:34 PM

ZhuangJW

InsanelyMac Protégé

• Members
• 22 posts
• Gender:Male
• Location:China

How can I change the VRAM , it is always is 128M ? Maybe it is great number on the Old Mac version , but in  Yosemite it is not enough .

So , what should I do Donk ?

### Also tagged with one or more of these keywords: vmware unlocker

Topic Stats Last Post Info

#### 1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users