Jump to content
Donk

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

686 posts in this topic

Recommended Posts

fcl,

 

You can download the tools at the following location, link below:

 

http://www.insanelymac.com/forum/files/file/31-vmware-tools-for-os-x-darwiniso/

 

Also the How To guide has full details regarding manually installing the VMware tools, see link below:

 

http://www.insanelymac.com/forum/topic/290949-how-to-install-os-x-10x-snow-leopard-to-el-capitan-in-vmware-workstation-1011-workstation-proplayer-12-player-67-esxi-56/

 

Yes thank you, I did fix my issue. I was googling the wrong keyword and finally got the darwiniso

... and sorry for late reply, I kept forgetting my forum password

Share this post


Link to post
Share on other sites
Advertisement

rafaeldamasceno,

 

Looks like latest VM Update (12.5.5 build-5234757) breaks the patch. Cannot load vmtools on Windows or OS X clients. Plan to roll back to an earlier version. Was working a week ago.

Share this post


Link to post
Share on other sites

rafaeldamasceno,

 

Looks like latest VM Update (12.5.5 build-5234757) breaks the patch. Cannot load vmtools on Windows or OS X clients. Plan to roll back to an earlier version. Was working a week ago.

 

Did you re-apply the unlocker after upgrading? 

Share this post


Link to post
Share on other sites

Yes, re-applied after upgrading. Uninstalled and rolled back to 12.1.0. and reapplied 2.0.8. Then was able to run VM Tools on Windows machine. Still had an issue with Darwin tools but have since learned that the current updated Darwin.iso is too new for 10.9 and 10.10. Used Darwin 7.1.0 as a trial and it worked.

 

Using VMware 12.5.5 would give a server error when trying to install VMware tools on a Windows machine.

 

I can update and try again if it would be of help.

Share this post


Link to post
Share on other sites

The unlocker would not affect the tools in any way if already installed. I believe there has been an issue with newer Widows versions and VMware tools discussed on the VMware forums.

 

I am using the latest version of Workstation on Windows and Linux with the unlocker and it does work OK.

Share this post


Link to post
Share on other sites

Hi.

 

As mentioned in the 1st post 2.0.9 is not out finally yet. On github i find 2.0.9 RC2. When do you expect a final release, or is it safe to use 2.0.9 RC2 now?

 

for now i'm using 2.0.8 on ESXi 6.0 on HP MicroServer Gen8. Everthing is working fine, but i would like to upgrade to ESXi 6.5.

Share this post


Link to post
Share on other sites

Has anyone been able to use their real macOS Dual Boot Partition as the disk in VMWare, so they can access their macOS Hackintosh installation from Windows?

 

(like how I can use virtualize my real Windows installation on MacOS)

Share this post


Link to post
Share on other sites

Hi all, having a bit of trouble. On Windows 10 -- installed VMware Workstation Player to the default location, ran the win-install file as administrator, but getting some errors and not seeing macOS in the OS list. Gist is below. Thanks in advance!

 

https://gist.github.com/anonymous/df7ab5e1e89b077b64cda9c4391934b1

 

Edit: Also when starting the machine, it acts like no OS is installed - it said IDE device could not be started, loads to Intel PXE boot, then fails.

Share this post


Link to post
Share on other sites

Hi all, having a bit of trouble. On Windows 10 -- installed VMware Workstation Player to the default location, ran the win-install file as administrator, but getting some errors and not seeing macOS in the OS list. Gist is below. Thanks in advance!

 

https://gist.github.com/anonymous/df7ab5e1e89b077b64cda9c4391934b1

 

Edit: Also when starting the machine, it acts like no OS is installed - it said IDE device could not be started, loads to Intel PXE boot, then fails.

 

This is an issue in the pyinstaller system used to package up the Python code. I am not sure what is causing this issue so can I suggest some different tests?

 

1. Disable any AV you have running as that can stop some of the VMware processes from being stopped. For example McAfee HIPS interferes with the unlocker. After patching it can be restarted.

2. Apparently pyinstaller may not like unusual characters in paths so the next step would be to try it from a path without "(" or ")" characters:

C:\Users\xxxx\Downloads\VMWare Player Patch Τool macOS Sierra\unlocker208

3. Also pyinstaller has had problems with the code page in the terminal. Can you run the CHCP command in a command prompt and let me know the value please?

 

Thanks

Share this post


Link to post
Share on other sites

This is an issue in the pyinstaller system used to package up the Python code. I am not sure what is causing this issue so can I suggest some different tests?

 

1. Disable any AV you have running as that can stop some of the VMware processes from being stopped. For example McAfee HIPS interferes with the unlocker. After patching it can be restarted.

2. Apparently pyinstaller may not like unusual characters in paths so the next step would be to try it from a path without "(" or ")" characters:

C:\Users\xxxx\Downloads\VMWare Player Patch Τool macOS Sierra\unlocker208

3. Also pyinstaller has had problems with the code page in the terminal. Can you run the CHCP command in a command prompt and let me know the value please?

 

Thanks

 

  1. No antivirus on my system aside from Windows Defender, so that should be clear.
  2. I took the parentheses out of the folder name but it didn't seem to help. Current path is C:\Users\baile\Downloads\VMWare Player Patch Τool macOS Sierra\unlocker208
  3. System active code page: 437

Here's the latest snippet

Thanks for the help in advance!

 

Edit: Got it! pyinstaller must not like long file names. I changed the folder name from "VMWare Player Patch Τool macOS Sierra" to "patch" and it worked flawlessly.

Share this post


Link to post
Share on other sites
Traceback (most recent call last):
  File "<string>", line 18, in <module>
  File "D:\PyInstaller-3.0\PyInstaller\loader\pyimod03_importers.py", line 634, in install
  File "D:\PyInstaller-3.0\PyInstaller\loader\pyimod03_importers.py", line 222, in __init__
ImportError: Can't load frozen modules.

In both calls to the python scripts in win-install I get this, which results in the scrips exiting with -1 and the install failing. I've tried installing Python 3.0 and 2.7, removing and reinstalling VMWare, and running the .py files instead of the .exe files. Nothing has worked so far. Any ideas?

Share this post


Link to post
Share on other sites

 

Traceback (most recent call last):
  File "<string>", line 18, in <module>
  File "D:\PyInstaller-3.0\PyInstaller\loader\pyimod03_importers.py", line 634, in install
  File "D:\PyInstaller-3.0\PyInstaller\loader\pyimod03_importers.py", line 222, in __init__
ImportError: Can't load frozen modules.

In both calls to the python scripts in win-install I get this, which results in the scrips exiting with -1 and the install failing. I've tried installing Python 3.0 and 2.7, removing and reinstalling VMWare, and running the .py files instead of the .exe files. Nothing has worked so far. Any ideas?

 

 

 

There are issues when there are characters in the path such as Chinese, Japanese etc. What is the folder name you are using? This is a known issue with Python and PyInstaller.

Share this post


Link to post
Share on other sites

There are issues when there are characters in the path such as Chinese, Japanese etc. What is the folder name you are using? This is a known issue with Python and PyInstaller.

I changed the folder name to test to see if that fixed anything and it worked perfectly. There weren't any foreign characters in the path, but they weren't all alphanumeric.  Thank you.

 

Edit: Now I see that the issue directly before me was the same thing.  I skimmed the first few pages of the thread and searched "Can't load frozen modules" and then didn't see those posts. Sorry to make you solve the same issue twice in a row.

Share this post


Link to post
Share on other sites

I hate to be the bearer of bad news, but this DOES NOT work on ESXi 6.5, I ran the installer, and got "Failed - Transport (VMDB) error -45: Failed to connect to peer process. Errors Transport (VMDB) error -45: Failed to connect to peer process." after reboot when trying to start ANY, Windows, Linux, VM.

So I ran the uninstaller .bat script, thank god it worked and now everything is back to normal.

ESXi 6.5 users beware, this won't work yet, and until the post is updated to mention .5 support, I wouldn't recommend trying it.

Share this post


Link to post
Share on other sites

I hate to be the bearer of bad news, but this DOES NOT work on ESXi 6.5, I ran the installer, and got "Failed - Transport (VMDB) error -45: Failed to connect to peer process. Errors Transport (VMDB) error -45: Failed to connect to peer process." after reboot when trying to start ANY, Windows, Linux, VM.

 

So I ran the uninstaller .bat script, thank god it worked and now everything is back to normal.

 

ESXi 6.5 users beware, this won't work yet, and until the post is updated to mention .5 support, I wouldn't recommend trying it.

 

I have pointed this out on the first post:

 

WARNING - Do NOT use the code on GitHub please wait until a release is announced. The current 2.0.9 code is there but there are serious issues still to be resolved which could render your ESXi host unusable!

Share this post


Link to post
Share on other sites

Hello Donk,

 

First off, thank you for your hard work!  I stumbled across this and I am excited to test out OSX in a VM environment.  I currently have eSXI 6.5, which I see Unlocker only works for 6.0.  Do you anticipate a release that supports 6.5 or should I downgrade from 6.5 to 6.0?

Share this post


Link to post
Share on other sites

Hello Donk,

 

First off, thank you for your hard work!  I stumbled across this and I am excited to test out OSX in a VM environment.  I currently have eSXI 6.5, which I see Unlocker only works for 6.0.  Do you anticipate a release that supports 6.5 or should I downgrade from 6.5 to 6.0?

 

Hi Curlyp. Have you actually tried the latest unlocker 2.0.8 version with 6.5?

 

I just used unlocker 2.0.8 with the latest Workstation 12.5.7 version, and it worked perfectly fine.

 

In general VMware ESXi 6 and 6.5, as well as Workstation 12 and 12.5 seem to be in the same group.

Share this post


Link to post
Share on other sites

Hi Curlyp. Have you actually tried the latest unlocker 2.0.8 version with 6.5?

 

I just used unlocker 2.0.8 with the latest Workstation 12.5.7 version, and it worked perfectly fine.

 

In general VMware ESXi 6 and 6.5, as well as Workstation 12 and 12.5 seem to be in the same group.

Gents,

 

Unlocker 2.0.8 works fine for ESXi 6.0 with all subsequent updates, but does not work properly with ESXi 6.5, hence the work Donk is doing on 2.0.9. But as he states still some issues so only use at your own risk and in a test environment where you can afford to lose everything.

Share this post


Link to post
Share on other sites

Error received when working with Python 3.6.2rc1 (64-bit) and VMware Player 12.5.7:


GOS Patching: D:\Program Files (x86)\VMware\VMware Player\vmwarebase.dll
Traceback (most recent call last):
  File "<string>", line 413, in <module>
  File "<string>", line 404, in main
  File "<string>", line 283, in patchbase
IOError: [Errno 13] Permission denied: u'D:\\Program Files (x86)\\VMware\\VMware
 Player\\vmwarebase.dll'
unlocker returned -1

 

Running unlocker.exe from command prompt with administrator rights.  I see that there seem to be extraneous backslashes, is there some way to remove them?

 

S

Share this post


Link to post
Share on other sites

Error received when working with Python 3.6.2rc1 (64-bit) and VMware Player 12.5.7:

GOS Patching: D:\Program Files (x86)\VMware\VMware Player\vmwarebase.dll

Traceback (most recent call last):

  File "<string>", line 413, in <module>

  File "<string>", line 404, in main

  File "<string>", line 283, in patchbase

IOError: [Errno 13] Permission denied: u'D:\\Program Files (x86)\\VMware\\VMware

 Player\\vmwarebase.dll'

unlocker returned -1

 

Running unlocker.exe from command prompt with administrator rights.  I see that there seem to be extraneous backslashes, is there some way to remove them?

 

S

 

 

Version of Python should not matter as it is packaged with pyinstaller which embeds the correct Python in the executable. The double backslashes are correct as they are used to ensue the path is correctly escaped.

 

Do you have an anti-virus working as I have had problems with McAfee especially Host Intrusion Protection?

Share this post


Link to post
Share on other sites

Error received when working with Python 3.6.2rc1 (64-bit) and VMware Player 12.5.7:

GOS Patching: D:\Program Files (x86)\VMware\VMware Player\vmwarebase.dll

Traceback (most recent call last):

  File "<string>", line 413, in <module>

  File "<string>", line 404, in main

  File "<string>", line 283, in patchbase

IOError: [Errno 13] Permission denied: u'D:\\Program Files (x86)\\VMware\\VMware

 Player\\vmwarebase.dll'

unlocker returned -1

 

Running unlocker.exe from command prompt with administrator rights.  I see that there seem to be extraneous backslashes, is there some way to remove them?

 

S

 

Ensure you have Python 2.7.x available in PATH as the code is in python 2 not 3 (there are some stylistic changes that aren't backwards compatible). Next ensure you are running the installer from a folder without spaces in its name (i.e. the path to the installer needs to be C:\Patch\ rather than C:\Some Place With Spaces\).

 

The "extraneous backslashes" are to tell python the previous backslash is not one which is for an 'escape character' such as \n (newline) and \r (carriage return).

 

Hope this helps.

Share this post


Link to post
Share on other sites

Is there someone interested in taking over the work on the unlocker? I have decided, after 10 years of working on different methods to run macOS on VMware products, that it is time for a change. The code will be on Github for awhile but as I intend to use my account for other work I will be removing it at some point.

 

It has been fun but time for other things in life.

Share this post


Link to post
Share on other sites

Is there someone interested in taking over the work on the unlocker? I have decided, after 10 years of working on different methods to run macOS on VMware products, that it is time for a change. The code will be on Github for awhile but as I intend to use my account for other work I will be removing it at some point.

 

It has been fun but time for other things in life.

Donk,

 

Sorry to hear you are stopping work on your unlocker, but understand fully about other things in life. I think I can speak for everyone on this forum and say thank you for your tireless effort and support. Enjoy your InsanelyMac retirement.

 

On a personal note, please keep in touch via email.

 

Regards,

MSoK.

Share this post


Link to post
Share on other sites

Donk,

 

Sorry to hear you are stopping work on your unlocker, but understand fully about other things in life. I think I can speak for everyone on this forum and say thank you for your tireless effort and support. Enjoy your InsanelyMac retirement.

 

On a personal note, please keep in touch via email.

 

Regards,

MSoK.

 

Well thanks for all your support over the years, and the others here who have helped out with answering questions or providing code. I enjoyed the fun of looking into how to make this all work and hope has been useful to the community.

 

I will still probably lurk around the forums to see what is going on.

 

I will stay in touch and you know my email address.

Share this post


Link to post
Share on other sites

Is there someone interested in taking over the work on the unlocker? I have decided, after 10 years of working on different methods to run macOS on VMware products, that it is time for a change. The code will be on Github for awhile but as I intend to use my account for other work I will be removing it at some point.

 

It has been fun but time for other things in life.

Obviously this is sad news, especially for those of us who were hoping for an update for ESXi 6.5 compatibility, guess I'll have to downgrade to ESXi 6!

 

Nevertheless I completely understand your decision. Thank you for all the work you've put into this project over the years, hopefully someone comes along and takes over :)

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.

  • Similar Content

    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VMware Workstation on a Windows Host
       
      I wanted to make a simple guide on how to create a vanilla OS X El Capitan virtual machine running on a Windows host.  The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are many guides and videos on the net about running OS X on Windows machines using pre-made VMWare disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from various threads in the Multibooting and Virtualisation section of this forum eg
       
      Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2 by @Donk How to Install OS X 10.x from Snow Leopard to El Capitan in VMware Workstation 10/12, Player 6/8 or ESXi 5/6 by @MSOK HOW TO: Create a bootable El Capitan ISO for VMware Credit and thanks to @Donk, @Albert Nietsnie and @MSOK for all their hard work in creating and testing the VMware Unlocker program.
       
      Requirements
      Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X) 4GB or more RAM (2GB or more will be needed for OS X) Hard Disk with at least 40GB free for Virtual Machine VMware Workstation 12 or later VMware Unlocker 2.0.7 or later Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#41 16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Unmount any attached install image/InstallESD.dmg (if currently mounted) by rebooting the system or running the hdiutil unmount command in terminal eg
       
      3.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes….
       
       
       
      4.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 5.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
      Updates:
      @shela has created an ISO generating script compatible with OS X 10.6-10.12: create_osx_iso post #362.
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS 10.13+ using Apple's createinstallmedia utility.
       
      Install and Patch VMware Workstation 12 on your PC
      1.  Download and install VMWare Workstation Player 12 or later
      2.  Download and extract Unlocker 2.0.7 or later to your USB stick…
      3.  Run the win-install.cmd as administrator by right clicking the file in Windows explorer or run it from an Administrative Command Prompt.
       



       
      Create an El Capitan Virtual Machine
      1.  Double click on the VMware Workstation 12 Player icon on your desktop and click “Create a New Virtual Machine”.  Choose “I will install the operating system later” at the How will you install screen….
       

      2.  Select Apple Mac OS X as the Guest operating system and OS X 10.11 as the version.  By default, an OS X 10.11 folder will be created in your Documents\Virtual Machines folder.
       


      3.  Under Specify Disk Capacity, you can leave the default 40GB or set a larger value.  I personally store the virtual disk as a single file.  Click Finish and you will see OS X 10.11 on the Main Screen of Workstation 12.
       


      4.  Next, we need to edit the virtual machine settings to map the virtual SATA CD/DVD drive to the El Capitan installation iso we created earlier.
       


       
      5.  To prevent the virtual machine from crashing in Windows, the virtualHW.version set in the vmx configuration file needs to be changed from 12 to 10 (alternatively, the line smc.version = "0" can be added to the file).  The OS X 10.11.vmx file can be edited with the WordPad program (navigate to the OS X 10.11 virtual machine folder with Windows Explorer and right click on the file to open in WordPad).
       


       
      6.  For HW10, set USB compatibility to USB 2.0, otherwise your mouse and keyboard might not work in the virtual machine.
       

      7.  Finally click “Play virtual machine”
       

      Installation of El Capitan
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I’ve named the drive Macintosh HD but you can enter whatever you like eg El_Capitan.
       



      3.  Quit DU and choose Macintosh HD to install El Capitan on.
       

      4.  After 20-30 min (depending on how fast your system is), the installation will complete and the VM will automatically reboot…
       

      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
       


      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
       


      7.  Finally, you will arrive at the El Capitan Desktop.  You should eject the Installation iso now by right clicking and selecting “Eject OS X Base System”.  This will allow you to install VMware Tools….
       



      8.  After rebooting, the VM can now be resized or run at full screen resolution.  Audio and network/internet should also work OOB.
       

       
      SMBIOS Customization and iMessage Vars
      To make the Virtual Machine more "Mac like", you can edit the vmx file to add unique identifiers from a real Mac's SMBIOS -
      eg for an iMac 11,3 SMBIOS, you can enter the following lines....
      smbios.reflectHost = "FALSE" board-id.reflectHost = "FALSE" board-id = "Mac-F2238BAE" hw.model.reflectHost = "FALSE" hw.model = "iMac11,3" serialNumber.reflectHost = "FALSE" serialNumber = "W80#######6" Refer How to spoof real Mac in VMware - Multi-booting and Virtualisation.
       
      The critical variables for iMessage/Facetime activation are MLB & ROM.  By default, VMware "reflects" the host's MLB and ROM since it assumes you are running the OSX guest on a real Mac host - see post#42 by @Donk.
       
      If the host is a Windows PC, the following lines need to be added to the vmx file (requires virtualHW.version 12 and smc.version = "0")....
      efi.nvram.var.ROM.reflectHost = "FALSE" efi.nvram.var.MLB.reflectHost = "FALSE" system-id.enable = "TRUE" and the MLB, ROM and optionally system-id entered manually eg
      efi.nvram.var.MLB = "W80######BA1A" (MLB can be 13 or 17 characters long, alphanumeric string) efi.nvram.var.ROM = "<=>?@A" (ROM is entered here as a 6 character ASCII string) uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" <---Optional (if you want to inject a given system-id hexadecimal value) Note the output for ROM from imessage_debug is a 12 character hexadecimal that needs to be entered here as a 6 character ASCII string eg using an Hex to ASCII converter we find that "3c3d3e3f4041" hex is equivalent to   "<=>?@A".
       
      Vanilla Mavericks and Yosemite
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Enjoy
       
      Update for macOS 10.12 Sierra
      The above settings still work for macOS Sierra after upgrading to VMware Workstation 12.5 and unlocker 2.0.8 - see post #13.
       
      Update for macOS 10.13 High Sierra and 10.14 Mojave
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS using Apple's createinstallmedia utility.
      Post#41 describes how to build "Install macOS ******.app" on the fly from installer files downloaded beforehand in /SharedSupport folder.
       
      Update for macOS 10.15beta Catalina
      See post Update for macOS Catalina 10.15beta
       
      CECI.zip
      CYI.tool.zip
      CMI.tool.zip
    • By David-B
      This version of VMware Unlocker is modified to support VMware Workstation 14. It has not undergone extensive testing, but from the little I have used it, it appears to be working properly on VMware Workstation 14.
       
      The original VMware Unlocker is available here: http://www.insanelymac.com/forum/files/file/339-unlocker/
       
      The changes that were made to the code to enable this patcher to work are available here: http://www.insanelymac.com/forum/topic/303311-workstation-1112-player-712-fusion-78-and-esxi-6-mac-os-x-unlocker-2/?p=2503855. Other than this change, only the install scripts and the patcher exe for Windows was modified.
    • By Donk
      Mac OS X Unlocker for VMware V2.0
       
      Please ask questions in this thread http://www.insanelymac.com/forum/topic/303311-workstation-1112-player-712-fusion-78-and-esxi-6-mac-os-x-unlocker-2/
      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

      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 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 hardware VMware will 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

       
      © 2011-2015 Dave Parsons
    • By phantom2000
      I'm tyring to run iATKOS S3 V2 on VMware Fusion 6(on Mavericks). I tried to set up Fusion with the iso file but when I start the VM, it says "The guest operating system is not MacOS X Server". Then I have downloaded the Fusion Unlocker v1.2.0 but I can't seem to get it to work. I have taken the execution permissions for the files install.sh, uninstall.sh and Unlocker.osx file by running the following commands,
      sudo chmod +x /Users/tim/Desktop/VMware/unlock-all-v120/osx/install.sh sudo chmod +x /Users/tim/Desktop/VMware/unlock-all-v120/osx/uninstall.sh sudo chmod +x /Users/tim/Desktop/VMware/unlock-all-v120/osx/unlocker.osx Then I tried to run the install.sh script using the command,
      sudo /Users/tim/Desktop/VMware/unlock-all-v120/osx/install.sh But I get this error message,
      TimBok:~ tim$ sudo /Users/tim/Desktop/VMware/unlock-all-v120/osx/install.sh Password: VMware Unlocker 1.2.0 =============================== Copyright: Dave Parsons 2011-13 Patching... /Users/tim/Desktop/VMware/unlock-all-v120/osx/install.sh: line 12: ./Unlocker.OSX: No such file or directory TimBok:~ tim$ I need to know what I can do here to get rid os this issue and run the VM.
×