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

Advertisement

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 :)

 

I have a probable solution to ESXi 6.5 so my parting shot will be to try and finish it up and release before the end of the month.  I have enjoyed working on the unlocker plus all is predecessors, and I am pleased it has been of use to many in the community.

 

Thanks

Share this post


Link to post
Share on other sites

Thanks for everything Donk! Sorry to see you go but I understand. You've been a great resource and have a ton of patience helping people.

Share this post


Link to post
Share on other sites

I really hope you get ESXi 6.5 fixed... :/ But I'm okay with you retiring I've been a happy user of your unlocker for years... ;) I just hope somebody takes over the project so we can keep enjoying OS-X with VMWare because eventually there will be VMWare Workstation 13 & ESXi 7 and so on.. :) Thanks for all your work thru out the years... :)

Share this post


Link to post
Share on other sites

I am trying to run unlocker 2.0.8. When I run win-install file in command prompt using Administrator account, I get the following error.

 

IOError: [Errno 13] Permission denied: u'C:\\Program Files (x86)\\VMware\\VMware Workstation\\vmwarebase.dll

 

My OS is Win 10 64 bit.

VMWare workstation version is 12.0

Share this post


Link to post
Share on other sites

I am trying to run unlocker 2.0.8. When I run win-install file in command prompt using Administrator account, I get the following error.

 

IOError: [Errno 13] Permission denied: u'C:\\Program Files (x86)\\VMware\\VMware Workstation\\vmwarebase.dll

 

My OS is Win 10 64 bit.

VMWare workstation version is 12.0

Running from administrator account is not the same as running with admin privileges.

Share this post


Link to post
Share on other sites

Hi all;

 

I've upgraded my Fedora 26 laptop to kernel 4.12 and I cannot get the unlocker to work with vmware workstation 12.5.7

 

I used the usual fixes, specifically these 2:

 

 

1)

# cp -r /usr/lib/vmware-installer/2.1.0/lib/lib/libexpat.so.0 /usr/lib/vmware/lib# cd /usr/lib/vmware/lib/libz.so.1# mv -i libz.so.1 libz.so.1.old# ln -s /usr/lib64/libz.so.1 .

2)

manually compiling vmmon and vmnet modules (i used this script):

https://github.com/CountPickering/vmww-fix

 

 

This gets vmware to run but I cannot install unlocker208, I get this:

 

 Command '['vmplayer', '-v']' returned non-zero exit status 25

 

 

 

Thoughts?

 

 

Thanks in advance

Share this post


Link to post
Share on other sites

I moved to Virtual Box and successfully using MAC OS Sierra on it. Because I was also not been able to install unlocker208.


Running from administrator account is not the same as running with admin privileges.

JJTagy, I am in the Administrator group on my PC. So it means that I have admin privileges. Or do you want to say something else ?

Share this post


Link to post
Share on other sites

SUCCESS!

 

I upgraded Fedora 26, got a new kernel (4.12.8-300.fc26.x86_64)

 

Then I uninstalled vmware and renamed /usr/lib/vmware to /usr/lib/vmware_old

 

Then took the below steps and vmware worked

 

1)

# cp -r /usr/lib/vmware-installer/2.1.0/lib/lib/libexpat.so.0 /usr/lib/vmware/lib

# cd /usr/lib/vmware/lib/libz.so.1# mv -i libz.so.1 libz.so.1.old# ln -s /usr/lib64/libz.so.1 .

2)

manually compiling vmmon and vmnet modules (i used this script):

https://github.com/C...kering/vmww-fix

 

Now I can run

# vmware&

 

Lastly I stopped vmware, ran the lnx-install script for unlocker208 which also worked

 

Now my mac VM's work!

Share this post


Link to post
Share on other sites

I moved to Virtual Box and successfully using MAC OS Sierra on it. Because I was also not been able to install unlocker208.

 

JJTagy, I am in the Administrator group on my PC. So it means that I have admin privileges. Or do you want to say something else ?

Windows uses UAC which means that even as a user in the Admin group, you aren't running programs with administrative rights. If you right click the program and select "Run as Administrator", then it is running with administrative rights.

Share this post


Link to post
Share on other sites

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!

 

Hi Donk,

Sorry to hear that you are moving on, but I completely understand the churn of keeping this project up to date...

 

 

Unfortunately I installed the github version before checking this page.

 

The good news, is that everything seems to be fine (VMs are running).

 

Hope you will find time to release the final Unlocker 2.0.9 for ESXi 6.5

 

FYI I'm using (uname -a):

 

VMkernel esx 6.5.0 #1 SMP Release build-5969303 Jul  6 2017 21:22:25 x86_64 x86_64 x86_64 ESXi

Share this post


Link to post
Share on other sites

 

The good news, is that everything seems to be fine (VMs are running).

 

Hope you will find time to release the final Unlocker 2.0.9 for ESXi 6.5

 

FYI I'm using (uname -a):

 

VMkernel esx 6.5.0 #1 SMP Release build-5969303 Jul  6 2017 21:22:25 x86_64 x86_64 x86_64 ESXi

 

I have the same version of ESXi running. Glad to hear that your VMs are working fine (past posts on this thread indicates  thateven non-MacOS VMs wouldn't start after installing unlocker but I believe that was with unlocker 2.0.8, not 2.0.9). What I really would like to know is whether you have a Mac OS VM running on ESXi, and if you don't, would you be willing to install one? Thanks for any info.

Share this post


Link to post
Share on other sites

The code in the git repo does now work. However I am not happy with how it is done, by disabling a new sandbox present in ESXi 6.5, so left the warning on the main topic. I will likely finish 2.0.9 once new Workstation and Fusion are released. 

Share this post


Link to post
Share on other sites

Thank you very much for your great work!

 

The code in the git repo does now work. However I am not happy with how it is done, by disabling a new sandbox present in ESXi 6.5, so left the warning on the main topic. I will likely finish 2.0.9 once new Workstation and Fusion are released. 

Share this post


Link to post
Share on other sites

I can confirm that Unlocker 2.0.8 doesn't work on VMware Workstation Pro v14.0.0 Build 6661328.

 

It would have been great if someone started working on it. :(

Share this post


Link to post
Share on other sites

Unlocker 2.0.8 is semi-working with workstation 14. Workstation pro 14 can start exisiting macOS virtual machines after patching. But GUI has no options to create macOS virtual machines.

Share this post


Link to post
Share on other sites

Unlocker 2.0.8 is semi-working with workstation 14. Workstation pro 14 can start exisiting macOS virtual machines after patching. But GUI has no options to create macOS virtual machines.

Me too, and hope new unlocker will come soon.

Share this post


Link to post
Share on other sites

Me too, and hope new unlocker will come soon.

 

You saw this, right?

 

Share this post


Link to post
Share on other sites

I will try my best to fix this before heading off to other things. However I cannot find the table that stores the guest info at the moment, as it has changed from 12. Existing VMs are OK as the code to run macOS is still there and patched correctly, the only change is the routine to populate the new VM dialog guest OS type.

 

Also I am about to go on holiday and won't have time to look at this in detail for 2 weeks.

Share this post


Link to post
Share on other sites

Sort of related...

I tried installing the new guest tools from Fusion 10 (on VMware Player 12).  Afterwards, my guest macOS VM was stuck in high-DPI mode so everything was really huge.  Has anyone else tried the new VMware Tools yet?

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.
       
       
      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.
×