How to Run macOS on Windows 10 in a Virtual Machine

Gavin Phillips Updated 17-05-2019

Windows 10 is a great operating system. It has its quirks and annoyances, but what operating system doesn’t? Even if you’re beholden to Microsoft and Windows 10, you can still shop around. What better way to do that than from the safe confines of your existing operating system and a virtual machine? This way, you can run macOS on Windows, which is perfect when you want to use Mac-only apps on Windows.


In this tutorial, you will learn how to install macOS in a virtual machine, making a virtual Hackintosh. “Hackintosh” is the name of any unsupported hardware running a Mac operating system. Unsure if you will get along with a Mac? Give this tutorial a try!

What Files Do You Need to Create a macOS Virtual Machine on Windows 10?

Before delving into the “how to,” you need to download and install the essential tools. The tutorial details how to create macOS virtual machines using both Oracle VirtualBox Manager (VirtualBox) and VMware Workstation Player (VMware Player). Not sure which to use? Learn more about the differences between VirtualBox and VMware.)

Download the latest version of VirtualBox. The tutorial uses VirtualBox 6.0.6.

Download the latest version of VMware Player. The tutorial uses VMware Player 15.0.4.

(Note: If you’re thinking about using the paid version of VM Player in a commercial setting, make sure you try a free trial first.)

You also need a copy of macOS, too. Mojave is the latest macOS version. However, at the time of writing, there is no AMD macOS Mojave build available to those without an existing AMD-based macOS installation.

That doesn’t mean AMD users are completely out of luck though. You can still install macOS High Sierra in a virtual machine. And in time, an AMD-based macOS Mojave virtual machine build will become available.

This tutorial will focus on installing macOS in a virtual machine running on Intel hardware. Unfortunately, I do not have access to any AMD hardware so cannot provide a tutorial. However, if you continue reading, you will find links to several AMD macOS High Sierra and Mojave tutorials towards the end of the article.

Download the macOS Virtual Image

Download the macOS virtual image for your CPU, virtual machine type, and the version of macOS you want:

Intel Mojave

After the file finishing downloading, right-click, and extract using your favorite archive tool. For instance, I would right-click, then select 7-Zip > Extract to “Mojave Image.” In the folder, you will find a .VMDK file, which stands for Virtual Machine Disk Format. The VMDK file contains the operating system you will use in the next section.

How to Create a macOS Mojave Virtual Machine with VirtualBox

Open VirtualBox. Select New. Type macOS. VirtualBox will detect the OS as you type and will default to Mac OS X. However, you need to change this. Under Version, select macOS 10.13 High Sierra.

macos virtual machine choose os

Next, set the amount of RAM the virtual machine and macOS can use. I would suggest a minimum of 4GB, but the more you can give from the host system, the better your experience will be. Remember, you cannot assign more RAM than your system has available, and you need to leave some memory available for the host operating system. (How much RAM does a system need?)

Finally, you need to assign a hard disk. Select Use an existing virtual hard disk file.

macos virtual machine select vmdk file

Select the folder icon and browse to the VMDK file, then hit Create.

Edit the macOS Mojave Virtual Machine Settings

Before firing up the virtual machine and using macOS Mojave, you need to make a few tweaks to the settings. Right-click you macOS virtual machine and select Settings.

Under System, remove Floppy from the boot order. Ensure the Chipset is set to ICH9.

macos virtual machine set RAM

Select the Processor tab. Assign two processors. If you have an i7 CPU with power to spare (or an i9 with multiple extra cores), consider assigning more. However, this isn’t vital. Make sure the Enable PAE/NX box is checked.

macos virtual machine set processoers

Under Display, set Video Memory to 128MB.

macos virtual machine set video memory

Now, under Storage, check the box alongside Use Host I/O Cache.

Use Command Prompt to Add Custom Code to VirtualBox

Unfortunately, in its current configuration, VirtualBox doesn’t work with your macOS VMDK. To get it up and running, you have to essentially patch VirtualBox before the macOS virtual machine will function. TO do this, you need to enter some code using the Command Prompt. All the details are below.

Start by closing VirtualBox. The commands will not execute properly if VirtualBox or any of its associated processes are running. Once closed, press Windows Key + X, then select Command Prompt (Admin) from the menu. If your menu only shows the PowerShell option, type command into your Start menu search bar. Then right-click the Best Match, and select Run as Administrator.

The following code works for VirtualBox 5.x and 6.x.

Use the following command to locate the Oracle VirtualBox directory:

cd "C:\Program Files\Oracle\VirtualBox\"

Now, enter the following commands, one by one. Adjust the command to match the name of your virtual machine. For instance, my virtual machine name is “macos.” Here are the commands:

VBoxManage.exe modifyvm "macos" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff

VBoxManage setextradata "macos" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3"

VBoxManage setextradata "macos" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"

VBoxManage setextradata "macos" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Iloveapple"

VBoxManage setextradata "macos" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"

VBoxManage setextradata "macos" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1

After the completion of the commands, and presuming you encountered no errors, close the Command Prompt.

macos virtual machine command prompt virtualbox

Boot Your macOS Mojave Virtual Machine

Reopen VirtualBox. Double-click your macOS virtual machine to start it. You will see a long stream of text, followed by a gray screen. The gray screen can take a moment or two to clear, but don’t panic. When it resolves, you will arrive at the macOS “Welcome” screen.

macos virtual machine virtualbox welcome screen

From here, you can set your macOS Mojave virtual machine up as you see fit.

Pro Tip: Take a snapshot of your virtual machine once it passes the gray screen. If anything goes wrong down the line, you can return to the Welcome screen setup and start the process again. Once you complete the macOS setup, take another one so you can jump straight into your macOS installation. Head to Machine > Take Snapshot, give your snapshot a name, and wait for it to process.

Mouse and Keyboard Not Working?

Turn your macOS Mojave virtual machine off. Now, download and install the VirtualBox Extension Pack.

Once installed, right-click your macOS virtual machine and select Settings. Open the USB tab and select USB 3.0 (xHCI) Controller, then press OK.

Start your macOS Mojave virtual machine again, and you are good to go.

How to Create a macOS Mojave Virtual Machine Using VMware Workstation Player

Prefer VMware over VirtualBox? You can create a macOS Mojave virtual machine using VMware that works exactly the same as VirtualBox. And, just as with VirtualBox, VMware also requires patching before the macOS Mojave virtual machine will work.

Patch VMware Workstation Player

In the “macOS Virtual Image” file list above is the “VMware Player Patch Tool.” Before commencing any further, download the patch tool. Then, browse to the location you downloaded the patch tool to. Extract the contents of the archive. This process works best when the folders are on the same drive (e.g., the VMware root folder and extracted archive are both found on the C:\ drive).

Make sure VMware is completely closed. Now, in the patcher folder, right-click the win-install command script and select Run as Administrator. The script will open a Command Prompt window, and the patch-script will run. Pay attention. The script whizzes by and you need to keep watch for any “File not Found” messages.

The most common reason for a “file not found” or a “system cannot find the file specified” message is installing VMware Workstation Player in a different location to the default folder, and executing the patch from a different directory.

Once the patch completes, you can open VMware.

Create the macOS Mojave Virtual Machine With VMware

Select Create a New Virtual Machine. Choose I will install the operating system later. Now, select Apple Mac OS X, and change the Version to macOS 10.14. If you don’t see the macOS options, it is because the patch didn’t install correctly.

macos virtual machine vmware choose os

Next, you need to choose a name for your macOS Mojave virtual machine. Choose something easy to remember, then copy the file path to somewhere handy—you’re going to need it to make some edits in a moment. On the next screen, stick with the suggested maximum hard disk size, then select Store virtual disk as a single file. Complete the virtual disk creation wizard, but do not start the virtual machine just yet.

Edit the macOS Mojave Virtual Machine Settings

Before you can boot the virtual machine, you must edit the hardware specifications. Plus, you need to tell VMware where to find the macOS VMDK.

From the main VMware screen, select your macOS Mojave virtual machine, then right-click, and select Settings. Like VirtualBox, bump the virtual machine memory up to at least 4GB. You can allocate more if you have RAM to spare.

macos virtual machine vmware choose ram

Under Processors, edit the number of available cores to 2.

Now, under Hard Disk (SATA), you need to remove the hard disk created earlier. Select Remove and VMware will remove the disk automatically. Now, select Add > Hard Disk > SATA (Recommended) > Use an existing disk. Browse to the location of the macOS VMDK.

Edit the macOS VMX file

Your final set of edits before switching your VMware macOS Mojave virtual machine on!

Close VMware. Head to the location you stored the macOS virtual machine. The default location is:

C:\Users\YOURNAME\Documents\Virtual Machines\YOUR MAC OS X FOLDER

Browse to macOS.vmx, right-click, and select Open with…, select Notepad (or your preferred text editor). Scroll to the bottom of the configuration file and add the following line:

smc.version = "0"

Save, then Exit.

You can now open VMware, select your macOS Mojave virtual machine, and fire it up!

macos virtual machine vmware welcome screen

Install VMware Tools to Your macOS Mojave Virtual Machine

Remember the other ISO file downloaded with the VMware patch tool? That contains the VMware tools, a set of utilities and extensions that improve mouse handling, video performance, and other useful things.

With the macOS virtual machine running, select Player > Removable Devices >  CD/DVD (SATA) > Settings. Select Use ISO image file, then Browse to the location of the VM Tool New.ISO file downloaded earlier. Press OK and head back to macOS.

macos virtual machine vmware add iso

On the desktop, you should note the VMware Tools drive symbol. Double-click the drive to open, then select Install VMware Tools. During installation, you will meet a security warning. Select Open Security Preferences > Allow, then click the Padlock icon to confirm the changes. Restart the virtual machine, and you can start using macOS as you please.


There are a couple of things that can (and probably will) go wrong during the macOS virtual machine installation in VMware Player Workstation.

If you cannot see “Apple Mac OS X” during the virtual machine creation wizard, then you need to revisit the patch process. Ensure every process associated with VMware Player is off.

If you receive the message “Mac OS X is not supported with binary translation” when starting the virtual machine, there is a strong chance you need to activate virtualization in your BIOS/UEFI configuration.

If you receive the message “VMware Player unrecoverable error: (vcpu-0)” when starting the virtual machine, you need to head back to the macOS.vmx configuration file to ensure you added the extra line and saved the edit.

macOS Virtual Machine for AMD Hardware

Apple uses Intel hardware to power desktops and laptops. Configuring a macOS virtual machine using Intel hardware is easier because the hardware specifications are very similar. With AMD, the opposite is true. Because Apple does not develop macOS on AMD hardware, creating a macOS virtual machine on an AMD system is trickier.

Adding to this, I don’t have an AMD system to test macOS virtual machines on, so cannot give you a detailed tutorial. I can, however, point you in the direction of several macOS AMD virtual machine tutorials that do work, so long as you are patient and follow each step accordingly.

The AMD OS X forum is a great resource for macOS virtual machines. You can find many more forum threads regarding AMD macOS virtual machines, too.

macOS Mojave Virtual Machine Installation Complete

You have two options to choose from for your macOS Mojave virtual machine. Both options are great if you want to give macOS a try before making the switch from Windows. You can also use a macOS to some of the best Apple apps on offer.

You can use a virtual machine to test other operating systems too. For instance, here’s how to install a Linux distro in a virtual machine How to Install Linux in Windows With a VMware Virtual Machine Do you want to install Linux, but can't leave Windows? Try a virtual machine to run your favorite version of Linux inside Windows. We show you how to set up VMware Workstation Player. Read More . Looking to learn more about virtual machines? Check out our VirtualBox User’s Guide How to Use VirtualBox: User's Guide With VirtualBox you can easily install and test multiple operating systems. We'll show you how to set up Windows 10 and Ubuntu Linux as a virtual machine. Read More , which teaches everything you need to know, or our guide to creating a virtual machine using Windows 10 Hyper-V How to Create a Virtual Machine Using Windows 10 Hyper-V Did you know Windows 10 has an integrated tool for creating virtual machines? It's called Hyper-V and here's how it works. Read More .

Explore more about: Emulation, Operating Systems, Virtual Machine, Windows 10.

Whatsapp Pinterest

Enjoyed this article? Stay informed by joining our newsletter!

Enter your Email

Leave a Reply

Your email address will not be published. Required fields are marked *

  1. Lorenzo
    March 9, 2020 at 1:21 am

    Links to the downloads of Mojave versions don't work anymore

  2. Graham
    January 29, 2020 at 5:08 pm


    I have installed everything correctly and it boots up and works just fine. However, everything is just extremely laggy. I am on a windows 10 host. Is there any way to fix this?

    • Nelson Abreu
      March 16, 2020 at 1:39 pm

      Add additional resources to the VM?

  3. Ley
    January 17, 2020 at 4:02 pm

    Hi, the links to the image aren't working. Could you update these? Thanks in advance!

  4. Bert
    December 29, 2019 at 8:34 pm

    Thanks for this. Installed with VirtualBox and working fine .

    Question: Is is possible to increase display to greater than 1024 x 768? If so, how?


  5. Gunnar
    December 10, 2019 at 10:08 am

    Hi! Most of the steps on this guide seem to working for me, but for the life of me I cannot figure out where to (or how to for that matter) download the .vmdk file. I'm using the VMWare setup. I'm also curious as to what Liam commented on October 7th about the OS Versions that no longer work for VMWare and the Patch installer? Thank you for your time.

  6. Hben
    November 17, 2019 at 5:07 am

    I was initially successful, Thanks.
    As someone else also said. I tried the patch from another tutorial and was able to install OSX. The Vmware tools, I also got it working, not at the first try but also made several tries with different versions of the Tools, and at first and not sure how, but all of a sudden, was able to get full screen capability. Once in OSX, I did not have Maps running properly (black background instead of the actual map graphics) Started messing around with graphics settings, updated, re-installed Tools. Then I lost the full screen capability. Many tries, including creating new VM, re-installing patches, updating tools, etc. nothing. Today I get notification the VMware player has new update, I install and lost access to OSX. Luckily I was able to restore.
    Any tips on how to get full screen again? Is there a newer patch somewhere?
    Also, I am assuming, the VMware Workstation Pro version should be able to get the full graphics on Maps. Can anyone confirm if this hack would work in VMware Pro?

  7. windows_lover
    October 20, 2019 at 8:26 am

    Thank you! It actually worked without any hassle.

  8. tiago
    October 15, 2019 at 8:34 pm

    Gavin, thank you very much. It worked, after 4hrs trying to figure out, stuck here and there... This did not work on Workstation 15 basically, the unlock process. I downgraded to 14 and found unlocker302, I found the vmware website where you can manually download ALL the .rar or .tar. Copied all to "tools" folder in the uncloker. Run the install.cmd, got some errors but eventually, it worked. Follow the other steps to edit the file.

    October 12, 2019 at 10:43 am

    I have successfully installed OSX on Virtualbox but I cannot connect my mobile device to debug my app. Is there any workaround to fix it?

  10. Bob
    October 9, 2019 at 6:08 pm

    Hi Gavin.
    I did all the stuff above with virtualbox. when i boot MacOS the text stream goes and stop with:
    "root device uuid is '.....
    End InitBootStruct
    Start LoadRAMDisk
    End LoadRAMDisk
    Start FinalizeBootStruct
    Start RandomSeed
    End RandomSeed"

    That's it. Nothing goes further, no gray screen... What did i done wrong?

  11. Liam
    October 7, 2019 at 5:08 pm

    VMWare Player 15.0.4 used in this article no longer works with the latest updates on Windows 10 x64 as of approximately 08 October 2019.

    VMWare Player 15.1.0 must now be used instead:|PLAYER-1510|product_downloads

    The latest version (v3.0 at time of writing) of the Patch Tool (unlocker) should also be used
    * Old versions of the Patch Tool (unlocker) must be uninstalled prior to installing newer versions.

    PLEASE NOTE: Versions 2.1 (as recommended in the article) and version 3.0 of the Patch Tool (unlocker) DO NOT WORK with VMWare 15.5.0. VMWare 15.1.0 must be used instead.

  12. Anthony
    October 1, 2019 at 5:18 am

    When trying to boot in Virtual Box for the first time, in the boot text after StartLoadKernelFromStream
    I get
    Error allocating 0xa00 pages at 0x0000000002400000 alloc type 2
    End LoadKernelFromStream
    ERROR!!! Load prelinked kernel with status 0x80000000000000009
    Error loading kernel cache (0x9)

    Help! I don't even know what it means.

    • Joseph
      November 15, 2019 at 5:54 am

      Same. Please help!

  13. Mike
    September 26, 2019 at 12:34 am

    Mediafire link for VMWare is not working.

    • Gavin Phillips
      October 4, 2019 at 2:35 pm

      Updated with new working link!

  14. Jordan
    September 11, 2019 at 7:45 am

    Thank You!

  15. Alastair Stephen
    August 14, 2019 at 12:47 pm

    Everything installed okay; cmd codes done okay, i run my macOS machine and it does not load past the lines of text, no gray screen just holds with lines of text and no MAC loading screen?? the VM is running with duration timer - what have i done wrong??

    I am running the full install from an external HD, on a very small OS laptop however mem and storage isnt a problem as its running the machine okay; just doesnt seem to go past the in machine text/ start the MAC OS??

    Thanks, As

  16. Mohomed Rashad
    July 23, 2019 at 5:01 pm

    Hello there!
    It seems the vmware mac os download links aren't working.
    the google drive and the media fire links are down.
    Please fix this issue as soon as possible.
    It would be so much nice.

    • Gavin Phillips
      October 4, 2019 at 2:35 pm

      Hi, updated with working links.

  17. Jaime
    July 11, 2019 at 6:02 pm


    When I choose guest operating system in VMware new virtual machine wizard, a message telling that "64-bit guest operating systems are not supported by this host and will not run.".

    What should I do?


  18. Mark
    June 30, 2019 at 7:35 pm

    I've installed the new Catalina into Virtual Box but can't connect to an iCloud account. It says that is a valid AppleID but not an iCloud Account. What can I do? Thanks.

    • Gavin Phillips
      October 4, 2019 at 2:37 pm

      Sorry, I'm not sure. That sounds like an Apple issue, and I've also not tried updating to Catalina. Did the Catalina upgrade work?

  19. Rob Hopgood
    June 17, 2019 at 9:09 pm

    Is there a version of the code for virtualbox on linux????

  20. Dave Smith
    May 31, 2019 at 7:33 pm

    Will this work with macOS Mojave?

  21. Dave Smith
    May 31, 2019 at 7:32 pm

    Will this work with the latest Mac OS, macOS Mojave?

  22. Ken
    May 17, 2019 at 8:45 pm

    Please, please, please be careful with those "Hackintosh" Mac images.

    A couple of years ago I tried the same thing and was able to get the Hacked Mac OS to boot up.

    But then I noticed some really odd processes and connections to random IP addresses while using the Mac OS image I acquired.

    There is NO guarantee that the originator of the image while "tweaking" to work in a VM/non-Mac hardware environment didn't add some extra commands for key logging, data mining, etc.

  23. Adam
    May 17, 2019 at 7:22 pm

    Very interesting. Is there any special *magic* that needs to be done to do the same thin in Linux?

  24. Lane Jasper
    October 23, 2018 at 8:37 pm

    How can I change my Workstation 15 Mojave or ElCap resolution to a higher one? Both machines only show 1024x768 so do I need to I stall Nvidia web drivers perhaps? Im running a pro version of Workstation 15 I bought and have 2 VMs running great except for the low Resolution. TIA!

  25. Zak
    September 16, 2018 at 1:30 pm

    When I start mac (VirtualBox) it just stays on the screen with the grey and yellow text

  26. Vote4cake
    April 28, 2018 at 4:31 pm

    This was very helpful for me. Took me ages to figure this out. Thanks!

  27. Elliott
    April 18, 2018 at 9:53 pm

    I can use the mac but it won't let me use iMessage, apple support says its because the serial number is zero and it's probably a Hackintosh (oops). Is there any way I can change the serial number to something legit so i can use iMessage etc?

    • M. Kociscin
      June 6, 2019 at 4:13 pm

      From what I've seen, there are scripts of commands that can be run in Virtual Box that make a proper (but essentially fake/cloned) Mac (hardware) serial #. But it's good enough to allow you to get some of the things like iMessage going. My advice is to do your due dilligence to ensure the script that does this also doesn't sneak in any malware, etc.

  28. Sascha
    April 2, 2018 at 11:04 am

    Thanks a lot for this brilliant tutorial. I successfully installed the AMD version with VMWare. All steps described above went through without any errors.

    However, I seem to be the only one having this problem. When the VM starts I get the Apple logo in the center of the screen and a progress bar beneath it moving slowly to the right. When it reaches 100% nothing more happens. It just won't go any further. No (visible) errors are thrown.

    What could be the issue here?

    Thanks in advance for any pointers.

    • Sascha
      April 3, 2018 at 10:26 am

      I do see error messages in the log.

      They're about some problem with the CD-ROM drive of the host computer. I am unsure how to interpret the log messages, though:

      2018-04-03T12:16:49.102+02:00| vcpu-1| I125: Guest: toolbox: Version: build-5214329
      2018-04-03T12:16:49.103+02:00| vcpu-1| W115: GuestRpc: application toolbox, changing channel 65535 -> 0
      2018-04-03T12:16:49.103+02:00| vcpu-1| I125: GuestRpc: Channel 0, guest application toolbox.
      2018-04-03T12:16:49.158+02:00| vcpu-0| I125: TOOLS Received tools.set.versiontype rpc call, version = 10278, type = 2
      2018-04-03T12:16:49.159+02:00| vcpu-0| I125: Tools_SetVersionAndType did nothing; new tools version (10278) and type (2) match old Tools version and type
      2018-04-03T12:16:49.159+02:00| vcpu-0| I125: ToolsISO: open of C:\Program Files (x86)\VMware\VMware Player\isoimages_manifest.txt.sig failed: Could not find the file
      2018-04-03T12:16:49.159+02:00| vcpu-0| I125: ToolsISO: Unable to read signature file 'C:\Program Files (x86)\VMware\VMware Player\isoimages_manifest.txt.sig', ignoring.
      2018-04-03T12:16:49.162+02:00| vcpu-0| I125: ToolsISO: Selected Tools ISO 'darwin.iso' for 'darwin15-64' guest.
      2018-04-03T12:16:49.162+02:00| vcpu-0| I125: VMware Player did not ship with the tools ISO.
      2018-04-03T12:16:49.162+02:00| vcpu-0| I125: TOOLS Setting autoupgrade-checked TRUE.
      2018-04-03T12:16:51.504+02:00| vcpu-1| I125: TOOLS state change 3 returned status 1
      2018-04-03T12:16:51.504+02:00| vcpu-1| I125: Vix: [10500 mainDispatch.c:4155]: VMAutomationReportPowerStateChange: Reporting power state change (opcode=2, err=0).
      2018-04-03T12:17:41.214+02:00| vmx| I125: CDROM sata0:1: CMD 0x1b (START STOP UNIT) FAILED (key 0x5 asc 0x24 ascq 0)

      • Sascha
        April 4, 2018 at 1:21 pm

        The above error appears, because there is no disc in the CD-ROM drive. When I put in a disc, the VM tries to access it during bootup but then throws another error. So apparently that is not the root-cause for the VM not to finish booting.

    • Sascha
      April 11, 2018 at 5:48 pm

      In case anyone else is stuck at the Apple logo and the progress bar:

      Instead of only adding the line 'smc.version = "0"' to the vmx-file, also change 'firmware = "efi"' to 'firmware = "bios"'.

      Voilá: mac OS finally boots into setup!

  29. Joost
    March 5, 2018 at 10:08 am

    Thanks for the tutorial, but unfortunately I have the same problem as Jose with VirtualBox on AMD. The screen stays black even after about five minutes. I have an AMD Phenom II X6.

    Here's a list of thing I tried that did not help:
    Tried both OS Sierra and El Capitan.
    Saw somewhere in the comments that if you have an AMD with 6 processors you need to assign all 6 as virtual processors, that did not help.
    Checked in the BIOS that the Secure Virtual Machine option is enabled.
    Tried to disable Windows Hyper-V, but could not find it in the Windows control panel so I used a commandline to disable it.
    Disabled my McAfee virus checker.
    Checke the VirtualBox forum but they only talk about running Mac OS guests on Apple hardware.

    I created an Ubuntu VM to see if that would work and it works fine. I also started on the VMWare option, but the link to the Unlocker is not valid anymore.

    So I hope you can tell me how I can get this working.


  30. Jose
    February 22, 2018 at 7:50 pm

    I used VirutalBox and am running on AMD. I installed everything but when I start the MacOS I do not get the gray screen. It stays in the black screen with the white text which does say the system uptime meaning the system is up, but it does nothing else. Any help?

    • Sascha
      April 2, 2018 at 10:55 am

      The messages probably report a panic mode. If you downloaded the torrent for AMD, it won't run with Virtual Box. Use VMWare instead.

  31. David
    December 21, 2017 at 11:28 pm

    Hi Gavin
    Many thanks for this. I got it working for Intel on Virtual Box. Everything working fine exceot for one thing - the Apple maps app is completely black! The reason I wanted to this in the first place was to use Apple maps.

    Any ideas?

  32. Elle
    November 30, 2017 at 9:52 pm

    Sorry to bother , in my case everything went fine all the way, but upon opening virtual box and double clicking the created virtual mac, i got the following error :
    The virtual machine 'MAC' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\userx\VirtualBox VMs\MAC\Logs\VBoxHardening.log'.

    Result Code:
    E_FAIL (0x80004005)
    IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
    Thanks if you guys could help... cheers!

    September 26, 2017 at 11:42 am

    Tried to use my Apple ID when it asked me to, then this message appears:
    Cannot create Apple ID
    This mac is no longer eligible to create apple id accounts
    Create an apple id using a different device.
    Note: I was not creating a new one, just using my existing ID.

  34. gsoftwares
    September 22, 2017 at 2:29 pm

    i got a kernel panic i think while starting
    exit reason namespace 2 subcode 0x4 description: none

  35. abraham
    September 19, 2017 at 1:48 pm

    Greetings everyone!

    I followed the instructions but all i'm getting is a Shell>_ and nothing more.

    Please hekp

  36. Mani
    August 8, 2017 at 3:19 pm

    Hi Gavin,
    I followed your tutorial on a Windows 10 machine with Oracle VM Box and I was able to boot into MAC OS Sierra without any issues. Infact, I had some issues initially and found out that they are with the command line codes I used. I fixed them and though the initial screens threw some errors, finally I was able to set up my MAC OS on a Windows PC successfully!

    However, there is no sound in the virtual MAC OS. Is there any fix for the same? I am using the
    VMBox version 5.1.26 and have a direct HDMI sound (do not have any separate audio devices connected for sound) in my Windows PC. Any help would be greatly appreciated.

    • TheDeviceWolf79
      December 22, 2017 at 8:33 am

      VirtualBox audio on Sierra is not supported. If you want sound then VMware is your only choice.

  37. Pamela
    July 25, 2017 at 12:10 pm

    I've followed the instructions to the T and upon execution, a message by Virtual Box - Guru Meditation (???) tells me that 'a critical error has occurred while running the virtual machine and the machine execution has stopped.'

    It tells me to look at VBox.log & VBox.png. What have I done wrong?

    I have 16gb RAM & partitioned 8gb for it plus 3 of the 4 processors. Thank you in advance!

    • Pamela Lim
      July 29, 2017 at 12:01 pm

      I got it to work finally by downloading 5.1.14 version of VirtualBox and selecting Mountain Lion instead of ElCapitan. Not sure about the rest, now my only issue is to get the screen size to a decent resolution and scale. Thank you very much!

  38. Terrance
    July 19, 2017 at 2:43 am

    Hi Gavin,

    I have followed all the steps and not seemed to have any errors or issues, but when I go to run the machine I just get a quick shot of the VirtualBox logo and then it goes to black and doesn't move on. Any idea what might be causing this and how to fix it? Cheers!

  39. Pablo
    July 18, 2017 at 1:39 pm

    Hi Gavin!

    I have gone through the steps to set up macOS on virtualbox, however I get stuck at a screen with grey, white and yellow text. The screen says UEFI Inteactive Shell v2.1 EDK II.

    Any idea what this is and how I can get around it???


  40. Pablo
    July 17, 2017 at 1:44 am

    I have gone through the process but on the Command Prompt I keep getting "Syntax error: Missing or INvalid argument to '--cpuidset'??

    Any thoughts on what this could be.

  41. Garrett Wilt
    July 15, 2017 at 5:36 am

    I've downloaded mac OS 10.12 and Virtual Box. I've extracted the file and now have a VMDK file. However, when I go to create a new virtual machine in virtual box, I'm unable to. I only get Mac OS x (32-bit) and Mac OS 10.6 Snow Leopard as options. I don't see OS 10.12 or 10.11 presented as options.

    • Gavin Phillips
      July 15, 2017 at 1:57 pm

      First, type "turn windows features" into the start menu search. Select the top match. Ensure "Hyper V" and its nested options are *unchecked.* Restart Virtualbox.

      If no luck, you need to uninstall Virtualbox, head to your BIOS, and make sure virtualization is selected. There will be an option, but it'll be named something specific to your motherboard manufacturer (Intel VT-x or AMD-v).

      Finally, are you running a 64bit operating system host?

  42. Milad
    July 11, 2017 at 1:51 pm

    Whenever I try to start macOS from VM i get an error which states ''VT -x is disabled in the BIOS for all CPU modes.'' How can i fix this?

    • Gavin Phillips
      July 11, 2017 at 3:05 pm

      Hey Milad,

      You need to enable virtualization in your BIOS settings. Press either F2 or DEL during the boot process, then searching for an option concerning virtualization.

      Hopefully that helps.

  43. Navraj Singh
    July 6, 2017 at 2:26 pm

    Installation went through smoothly and even the command line updates for VirtualBox were successful. But when I try to run my vm, I get a black screen and a popup window with a message that "A critical error has occurred while running the virtual machine and the machine execution has been stopped."

    • jacob powell
      August 6, 2017 at 7:56 pm

      i got this too anyone have any kind of fix for this?

  44. MinMin
    July 6, 2017 at 1:42 pm

    No idea if this will get a response but here's hoping. When extracting the AMD Sierra OS, it's just a .dmg, not the .vmdk. I tried mounting it with a virtual ODD but it rejects it. Did I just download the wrong thing? Mind helping me get through installing via a .dmg?

    Thanks in advance! I appreciate the write up either way.

    • Gavin Phillips
      July 9, 2017 at 4:16 pm

      Hey MinMin,

      Sorry for the slow reply. I'm working on a fix. I'll update you as soon as possible!

    • Gavin Phillips
      July 9, 2017 at 6:38 pm

      Can I ask what VM software you were using?

    • Gavin Phillips
      July 10, 2017 at 12:28 am

      Hey MinMin,

      There is a new version of the AMD Sierra OS vmdk available: You'll need to create an account at the site, and use VMware (still patching as per the article instructions).

      Hopefully you get up and running!

  45. Dave
    June 24, 2017 at 10:38 pm

    Tried the intel version today with Virtualbox and never get to grey screen. In some kind of a boot loop with the text part of the bootup repeating over and over. Got any idea what might be wrong?

    • Gavin Phillips
      July 9, 2017 at 1:59 pm

      Hi Dave,

      Sounds like something went wrong during the installation process. I would suggest retrying, double checking each line of code is exactly the same.

      • Fabrice Tayou
        July 30, 2017 at 8:59 pm

        I had the same problem , @Dave may also have to execute the DOS commands while VirtualBox is closed, that worked for me

        • Gavin Phillips
          July 30, 2017 at 9:40 pm

          Good tip, Fabrice, and thought I'd included that in the original article.

          Have edited it in.

          Thank you.

  46. yuri
    June 9, 2017 at 6:21 am

    Hi, I downloaded the AMD version but it is .dmg, not .vmdk, so virtualbox doesn´t allow it. I tried to convert the file but I didn´t find any suitable converter and dmg2img through command line has also an issue, it says the .dmg file is corrupted.

    Do you have any ideas what´s wrong?
    (sorry for my bad english)

    • Gavin Phillips
      July 9, 2017 at 4:17 pm

      Hi Yuri.

      I'm working on a fix. I'll update you as soon as possible. Thanks for being patient.

    • Gavin Phillips
      July 10, 2017 at 12:28 am

      Hey Yuri,

      There is a new version of the AMD Sierra OS vmdk available: You'll need to create an account at the site, and use VMware (still patching as per the article instructions).

      Hopefully you get up and running!

  47. Peter
    June 7, 2017 at 8:02 am

    Except, when I download the macOS Sierra file, it is a .dmg file, not a .vmdk. Like what am I supposed to do now?

    • Gavin Phillips
      July 9, 2017 at 4:18 pm

      Hi Peter,

      Sorry for the slow reply. I'm working a fix for you. Thanks for your patience. I'll update you as soon as possible.

    • Gavin Phillips
      July 9, 2017 at 6:38 pm

      Which VM software are you using?

    • Gavin Phillips
      July 10, 2017 at 12:29 am

      Hey Peter,

      There is a new version of the AMD Sierra OS vmdk available: You'll need to create an account at the site, and use VMware (still patching as per the article instructions).

      Hopefully you get up and running!

  48. shekhar
    May 31, 2017 at 7:02 pm

    hey this article was great as t helped me get mac on my dell laptop and it seems to work fine but the only catch I face is the trackpad is not detected and the screen resolution is 1200x768 and because of that most of the screen real estate is black . can anyone help me fix these two issues ??

    • Gavin Phillips
      May 31, 2017 at 7:58 pm

      You can specify resolution in the hardware tab, found in the settings menu. The trackpad is a little more tricky. Which VM are you using, VirtualBox, or VMware?

      • Anders Hydén
        November 12, 2017 at 6:37 pm

        I'm having the same resolution issue as Shekhar.
        Since I have a 4K screen, it'd be awesome to use all of the real estate. :)
        However, in VirtualBox, I can't find any settings for the screen/resolution?

  49. Tim Cook
    May 31, 2017 at 6:34 am

    Download Quota exceeded for file, could someone post an alternative link for the intel version

    • Gavin Phillips
      May 31, 2017 at 7:48 pm

      Hey Tim,

      I'm not having any trouble with it, and nor are other people I've asked to test it.

      Nonetheless, not wanting to disappoint, I uploaded it here, just for you:

      Hopefully that sorts things out for you.


      • Navan Chauhan
        June 1, 2017 at 2:39 am

        Thanks a ton Gavin, I read the original article and for the black borders there is an isolated file named 'VM Tool's I could send you the link if you want

        • Gavin Phillips
          June 1, 2017 at 11:36 am

          No problem, glad it helped :)

      • Colin
        June 1, 2017 at 11:24 am

        Thanks Gavin, was getting same error as Tim.

        • Gavin Phillips
          June 1, 2017 at 11:37 am

          Ah, strange. But obviously a problem. Glad it helped, Colin.

      • Chris Bidmead
        June 3, 2017 at 10:59 am

        I'm getting "Download Quota Exceeded" too.

        Thanks for that alternative URL.


        • Chris Bidmead
          June 5, 2017 at 10:09 am

          Ha! I have the full downloads now (thanks). But I can't get your VBoxManage mods to work.

          > .\VBoxManage list vms
          ...manages to find "macos MUO" (I've given mine the same name as yours.

          But when I run your full command VBoxManage complains that it "Could not find a registered machine called 'macos MUO'"

          Is there some registration process I've missed?


      • TonyM
        June 7, 2017 at 3:00 pm

        I have tried the AMD download but the DMG is not bootable in VMWare for me. I even made it available in an older MAC AMD VM but the installer would start but never really get going right. Does someone have the ADM file that will be a good bootable DMG?

  50. Tim Cook
    May 31, 2017 at 6:33 am

    Download quota exceeded for file, could someone mirror it or reply for any other link

  51. likefunbutnot
    May 30, 2017 at 5:22 pm

    I keep a MacOS VM around for making screenshots in documentation. Ironically, I actually do spend some time on Apple hardware, but my setup is customized such that it's not really recognizable.

    • Gavin Phillips
      May 31, 2017 at 7:54 pm

      That is exactly why this article came about. I needed a Mac OS version to test some things for another article, and realised we hadn't covered it. I hope you found it useful in some way.


  52. Doc
    May 30, 2017 at 4:17 pm

    I used TechReviews' Sierra preview (not final) with VirtualBox (Apple does NOT allow you to use anything but Mac OS for uploading eBooks to the iTunes Store! BOO! Make a website to do it, Apple!) and it works somewhat well. Please note that you shouldn't use ALL your CPU cores in your VM, since it will make your Hackintosh unstable...

    • Gavin Phillips
      May 31, 2017 at 7:55 pm

      Aye, that's a really good point, Doc, thank you.