NOTE: This tutorial is now considered outdated and I've published a new instructable with a newer, better and more efficient method to install Mac OS X on your PC, not RUN it! Please refrain from using this tutorial and follow the Even if you're a Windows user, you've probably thought about trying the Mac OS X. Maybe you'd like to test OS X before buying a Mac or building a Hackintosh, or maybe you just want to run an app on your Windows machine which is only exclusive for the Mac OS X. Whatever your reason is, you can actually install and run OS X on any Intel-based Windows PC with a program called VirtualBox.
![Mac Iso Image For Virtualbox Mac Iso Image For Virtualbox](/uploads/1/2/4/0/124082076/254660215.png)
Running OS X on your Windows desktop will take a bit of work, but it's pretty easy to do and the final product is quite outstanding. Thanks to and for providing the original instructions!
Jun 30, 2018 - Creating a macOS High Sierra VM for VirtualBox (Mac Host). If you use VMware Fusion, instructions for creating the ISO should be the same, and the rest. Create a temporary disk image to create the bootable installer. Create a VirtualBox description script, and create an.iso image from, e.g., an Ubuntu 14.04.3-desktop-amd64 iso image, adding files. Useful for creating a clean test or development environment. Useful for creating a clean test or development environment.
To cut to the chase, here's how to do this. Before you start the installation process, you’ll want to gather the following: - A PC running 64-bit Windows with at least a dual-core processor and 4GB of RAM. Mountain Lion is 64-bit, and thus requires your copy of Windows to be 64-bit. If you’re on a 32-bit version of Windows, you can install Snow Leopard instead (Google it as this instructable is for Mountain Lion not Snow Leopard). Note that your processor also needs to support VT-x.
Should help you find out whether yours does. and the VirtualBox Extension Pack: VirtualBox is my favourite virtualisation tool for Windows, and it’s completely free. VirtualBox doesn’t officially support OS X, but it’s actually very easy to get up and running. You should download the main program and the Extension Pack, which will give you support for USB devices. A hacked Mountain Lion disc image. Sadly, this won’t work with a vanilla Mountain Lion installer, so you’ll have to find a compatible hacked version.
The hacking group Olarila has put a great installation ISO together, and you can find it by searching Google. If that doesn’t fit well with you, you can head over to the Mac App Store and, so you can at least pirate with a clear conscience. The and ISO files. Each one has it's own function which you'll know later. However, both will help you boot into the installation., which will help you get audio and other things working correctly after installation. You’ll need to register for a free account over at Tonymacx86.com to download this.
Make sure to download MultiBeast 4 — it’s labelled “Lion”, but for our purposes the Lion version works better than the Mountain Lion version. Before we install OS X, we’ll need to set up VirtualBox so the OS X install disc can boot correctly. Here’s what you need to do: Step 1: Launch VirtualBox and click the New button. Give your new virtual machine a name (I just called it “Mac OS X”) and set the operating system to “Mac OS X Server (64-bit)”. See the picture of step number one. Step 2: Click Next and choose how much RAM to give your virtual machine. This depends on how much RAM is in your system — you can get away with 2GB, but if you have more, give it more.
4GB of RAM should be a good amount, though I gave mine 4GB, you can set it till 6GB if you have spare. See the picture of step number two. Step 3: Click Next again and choose “Create New Disk”. Create your new disk in VDI format and with dynamically allocated storage. When you’re done, VirtualBox should take you back to the main screen. This step is easy, so it does not need a picture. Step 4: From here, right-click on your OS X machine in the left sidebar and click Settings.
Head to the “System” section and uncheck “Enable EFI”. Same as step 3, it's easy, so it does not need a picture. Step 5: Click on the Storage section of the settings and click on the CD icon that says “Empty” under Storage Type. Then, click the CD icon next to the “CD/DVD Drive” dropdown list and select “Choose a Virtual CD/DVD Disk File”. Choose the HackBoot 1 ISO and click OK. See the picture of step number five.
Now your virtual machine is ready to boot for the first time. Make sure you have your Mountain Lion ISO ready to go and proceed to the next step.
The next step involves actually installing OS X to your new virtual machine. When you’re ready, start up VirtualBox and follow these instructions: Step 1: Select your OS X virtual machine in VirtualBox’s left sidebar and click the Start button in the toolbar. It will bring you to the HackBoot boot screen, with one icon in the middle labelled HackBoot. See the picture of step number one. Step 2: Click on the CD icon at the bottom of the VirtualBox window and select “Choose a Virtual CD/DVD Disk File”. This time, choose your hacked Mountain Lion ISO. This step is pretty easy, so it does not need a picture.
Step 3: Go back to the HackBoot boot screen and press F5. It should reload the boot menu, this time showing you an “OS X Install DVD”. Select this option and press Enter. After a moment, it will take you to the OS X Installation screen.
Also this step is easy, so it does not need a picture. Step 4: After you choose your language and agree to the terms and conditions, you’ll see that OS X doesn’t detect any valid hard drives. To fix this problem, head up to the menu bar and go to Utilities Disk Utility. This step is pretty simple, so it does not need a picture. Step 5: Click on your VirtualBox hard drive in the left sidebar, then click the Erase tab in Disk Utility’s main panel.
Give your drive a name (like “Macintosh HD”) and click “Erase”. See the picture of step number five. Step 6: Once Disk Utility has finished formatting your drive, you should see it show up in the left sidebar.
When you do, exit Disk Utility and continue with the OS X installation as normal. This step is so easy, so it does not need a picture as well. The rest of the installation should be largely self-explanatory and should go off without a hitch. It took me about 20 minutes to install OS X. When it finishes, it will take you to a black screen with white text. At this point, you can click the “X” in the upper-right corner of the window to power off the virtual machine. You’re almost there!
You’ve installed OS X, but you will still need to tweak a few things to get audio and graphics working properly. Here’s what you need to do. Fix Audio with MultiBeast Step 1: Open up VirtualBox and right-click on your OS X virtual machine in the left sidebar. Head back to its Settings and go to the Storage section. Once again, click on the disc icon on the right side of the window, this time choosing the HackBoot 2 ISO. This step is simple, therefore it does not need a picture.
Step 2: Click the Start button to reboot your virtual machine. You should see the HackBoot menu again, this time with an option to boot into your new virtual machine. Select that option and press Enter.
See the picture of step number two. Step 3: After a minute, you should see the Mountain Lion desktop with the familiar galaxy wallpaper. Open up Safari, head to Tonymacx86.com, and download MultiBeast as described in the “Requirements” step. This step is easy as well, so it does not need a picture. Step 4: Open up System Preferences - Security. Click the lock in the bottom left-hand corner, enter your password, and set the “Allow Applications” preference to “Anywhere”.
This will let you run apps from untrusted developers, which includes Multibeast. This is step is quite easy, so it does not need a picture as well. Step 5: Launch Multibeast. When you get to the Installation Type section, Choose the options pictured in the picture of step number five. After that, click continue and finish the Multibeast installation.
It may take a few minutes. Your audio won’t work just yet, but we have a few other things we need to do before we restart.
In order to boot OS X without the HackBoot CD, we’ll need to delete a problematic kext. You can do this with the following steps: Step 1: Open up the Finder and select Go Go to Folder from the menu bar.
Type in '/System/Library/Extensions' (without the quotations) and press Enter. Of course does not need a picture. Step 2: In this folder, find the 'AppleGraphicsControl.kext' (without the quotations) file and delete it. This will allow your virtual machine to boot up without the HackBoot ISO. See the picture of step number two (main image). Step 3: Click on the disc icon at the bottom of VirtualBox’s window and uncheck the HackBoot 2 ISO, since you won’t need it anymore. Of course does not need a picture.
Lastly, you may have noticed that your Virtual Machine is running at a pretty low resolution. That’s totally lame, so we’re going to make it run at the same resolution as our monitor with a few tweaks: Step 1: Head back to Go - Go to Folder and go to '/Extra/' (without the quotations). Double-click on the 'org.Chameleon.boot.plist' (without the quotations) file and add the following to the bottom of the file, above the line: Graphics Mode 1920x1080x32 Save the file and close TextEdit. This allows OS X to start up with a higher resolution. Note that you can set whatever resolution you want; just replace '1920x1080' (without the quotations) with the resolution you want. Step 2: If the resolution you picked is bigger than 1280×1024 and/or is widescreen, you’ll need to do one last thing to get it working properly. Shut down your virtual machine and open Windows’ Command Prompt.
Type the following commands, hitting enter after each one: cd 'C: Program Files Oracle VirtualBox' vboxmanage setextradata 'MyVirtualMachine' 'CustomVideoMode1' '1920x1080x32' Replace the first line with the path to your VirtualBox program folder. In the second line, replace MyVirtualMachine with the name of your machine (in our case, “Mac OS X”), and 1920x1080x32 with the same resolution you added to your Chameleon plist. When you’re done, restart your OS X virtual machine and you should be greeted with a full-res desktop and working audio. You can now continue to install your favourite apps, set up your keyboard and mouse, and do anything else you like. You’ve got a fully working virtual Mac on your Windows desktop!.DISCLAIMER: The eyed-apple logo is a copyrighted image that belongs to tonymacx86.com and does not belong to me by any way, as I'm just using it to for reference to guide the installation.DISCLAIMER: This instructable should be done on your OWN responsibility.
I will not tolerate any damage (software damage) regarding this instructable if you do not follow the steps wisely. This was tested several times before on Intel-based PCs and it worked, so if you do not follow the steps wisely, I'm not tolerating any problems or damage that you may cause to your PC due to inattention or neglecting any step implemented in this instructable. Later on, I will be making computer instructables (tutorials) such as this instructable. I will be making newer and more easier methods to install the Mac OS X (all versions such as Lion and Snow Leopard) on your PC.
Some methods require that you already have an existing OS X. I'll also be making some instructables on Hackintoshing your PC. There are several reasons behind not doing this.
Firstly, not all people using this method have the same memory (RAM). For example, if you allocated your VM RAM to 4GB and you have a total of 6GB, not all people have 6GB, so they will have to create the VM from scratch.
Secondly, with my current internet speed, it would take me a month (maybe more) to upload 13GB (which is the size of the finished VM). Thirdly, this is a tutorial, it is made to make people understand how it works and how to create one, but not just to have it ready.
In our previous post we have shown you that how to and now in this article, I’m going to show you that how to install macOS Sierra 10.12 on VirtualBox. Apple has announced the next version of its Mac operating system:. Of course, the real change is that, after fifteen years, Apple has finally ditched the “OS X” moniker.
All things old are new again, and the new operating system will only call “macOS.” We don’t yet know if Sierra carries a “10.12” version number, but with developers getting their hands on the OS later today, we should soon have that question answered. Apple’s Craig Federighi ran through a whole bunch of new features to be included in the revised operating system. He started by mentioning Continuity and Auto-Unlock, which now combine to let you seamlessly unlock a desktop or laptop Mac merely by bringing your Apple Watch close, using what Federighi described as “time-of-flight networking” to detect the watch’s proximity. It was unclear from the presentation whether or not this feature is an Apple Watch exclusive; Federighi did not explicitly say that Auto-Unlock would work with iOS devices.
So, I’m not going to discuss anymore regarding Apple new release “macOS Sierra” instead; I’m gonna talk about installing macOS Sierra on VirtualBox on Windows operating system. Install macOS Sierra on VirtualBox Update: The Steps below works on macOS Sierra 10.12 Final Version the nearly released by Apple. (20 September) First, what you are going to do is make available the following materials.
(1 Part). (7 Parts). Step #1. Extract macOS Sierra Image File Once you downloaded the macOS Sierra image file then, you must extract it via. To extract the file, simply right-click on file then choose “ Extract Here.” It’ll take some minutes to extract so wait for a moment. Extract macOS Sierra VM File Step #2. Install VirtualBox on Your PC Download VirtualBox from the link above.
Once you have downloaded the VirtualBox, then Install it on your Windows PC. To install VirtualBox, just click on the setup then hit “ Next” and “ Next.” Finally, click “ Finished.” Step #3. Create New Virtual Machine #1. Now, you have to create a new Virtual Machine. Open the VirtualBox then tap on “ New” at the upper left-hand side and name the Virtual Machine “ macOS Sierra” then hit the “ Next” button.
Installing macOS Sierra on VirtualBox Step #7. Perform a Clean Installation of macOS Sierra Now while installing macOS Sierra or El Capitan on VMware or VirtualBox then we don’t need to install that on separate disk because while editing the VM we choose the virtual disk type SATA, and this is the one and only way for now to install macOS Sierra or El Capitan on VMware or VirtualBox. So that’s why now in the very next step we have to perform a clean installation and to set up macOS Sierra. Choose your Country and click on Continue. Setting up macOS Sierra Important: For any kinds of error while installing Mac OS X El Capitan and macOS Sierra visit this article. Watch the full video tutorial Conclusion After performing a clean installation and Setting up your macOS Sierra then you should see your final result that, macOS Sierra has successfully installed on VirtualBox. In this post, That was all about, how to install macOS Sierra 10.12 on VirtualBox and I have covered;.
Extract macOS Sierra Image File. Install VirtualBox on Your PC. Create New Virtual Machine. Edit the New Virtual Machine. Add VirtualBox Code to the CMD.
Play the Virtual Machine. Perform a Clean Installation of macOS Sierra Thanks for being with us.
Searches related to install macos sierra on virtualbox Install macOS Sierra 10.12 on VirtualBox – Windows 10, 8, virtualbox macos sierra virtualbox on sierra install mac os sierra on vmware install virtualbox on sierra virtualbox sierra mac virtualbox sierra host install virtualbox on mac sierra macos sierra virtualbox linux. Hello, I am at the step just after entering the new code via cmd prompt, where I have to start to power up masOS Sierra.
I was given a prompt instructing me to select a drive, which was defaulted to E:/, which is my cd rom drive. When it tries to start I am getting the following error: Cannot open host device ‘E:’ for readonly access. Check the permissions of that device (VERRACCESSDENIED). AHCI: Failed to attach drive to Port1 (VERRACCESSDENIED). Is there a way to change the drive to something else? I keep getting stuck in the startup loop and it repeats itself. I followed your instructions as best as possible.
I’m running linux (kali) and I think I just need instructions adapted to that. I deleted the.exe file and ran in!/bin/sh. I don’t fully know what I’m doing with linux or virtualization for that matter. I’m learning everyday.
I have every other VBox machine working (kali within a kali host, mint, windows 10, so I did manage that). Just can’t get the Sierra running on linux, stuck in the loop.
I am trying to run the Mac code. For starters, I do not have ‘cd “C: Program Files Oracle VirtualBox ”‘, my box is saved elsewhere. I am curious if this is the correct pathway that I should use instead? (C: ProgramData Microsoft Windows Start Menu Programs Oracle VM VirtualBox).
Also, no matter the pathway, I keep getting this error in the cmd prompt: “line of code.exe is not recognized as an internal or external command, operable program or batch file.” I cannot find the.exe lines in any files on my computer. How do I find them or redownload/extract them? Everything absolutely impeccable, network management included. Here, the key workaround (and kudos to you, Mukhtar, for putting on this point all the due emphasis) was to select “Intel PRO/1000 MT.SERVER. (82545EM)”, in place of everything else.
As I said, everything is working fine (guest: macOS 10.12 Sierra, on Fedora 27 host), except for one detail (which, unfortunately, is very annoying): the screen resolution. Alas, here, while at least I’ve been able to get out of the 1024×768 mode (“Suitable for this screen”), I’m still stuck with the 1280×720 mode the virtual system has put itself into, as a reaction to my attempt at forcing a 1366×768 mode via ‘VBoxManage setextradata “VMNAME” VBoxInternal2/EfiGopMode N’ Any idea? Best regards ? AIR. Hey there I would love some help with this.
I did everything you told me to do i only installed the macosserria final 1 part do i have to download the 7 parts as well? Every time I start it up it shows a black screen with the words UEFI Interactive Shell v.2.1 EDK II UEFI v2.40 (EDK II, 0X00010000) Mapping table BLKO: Alias(s): PciRoot(0x0)/Pci(0x1F,0x2)Sata(0x0,0x0,0x0) BLK1 Alias(s): PciRoot(0x0)/Pci(0x1F,0x2)Sata(0x0,0x0,0x0) Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
Hi Mukhtar #3. If you wish, you can add a virtual hard disk to the new machine. You can either create a new hard drive file or select one from the last or another location using the folder icon. Here, you should choose the last option “Use an existing virtual hard disk file“. Select the file and click “Create“.
This step wont work bcus I downloaded macOS 10.13.1 High Sierra.dmg and here I cant choose dmg format. I’ve createdd that by choosing “create a vitual hard disk now”.
And after that steps Command Prompt. I start the VM and Insert the dmg file. But it dont work with this error. Everything Working! Just used this tutorial to install on Microsoft Surface tablet. I can’t get iMessage working though, it says “failed to authenticate” when I try to log in. I’m sure this is because I’m running Mac on VM and my apple serial at this point is ‘0’, but is there any possible workaround for this??
Either way, thank you for constructing this tutorial. Also, after getting to installation screen, it was giving me error not enough space. Clicking on the disk utility and partitioning/erasing drive resolved this. Hello I have carefully followed your steps and then read some of ppl’s problems listed above, but noone had mine’s problem. When I launch VM, I have “Virtual box – Guru Meditation” error – “A critical error has occurred while running the virtual machine and the machine execution has stopped” window appears.
When I study log, a first line with ERROR header mentions extension pack: “No extension pack by the name ‘Oracle VM VirtualBox Extension Pack’ was found” I have downloaded and installed Oracle extension pack and the same error appears. I have tried on both Virtual Box 5.2 and 5.1.30 with the same result. Any help would be appreciated ?. Thanks for great instructions. Like others, I couldn’t get it to work on virtualbox 5.2 but it works well on 5.1.30. One question though – I’m having a problem getting the virtual machine to recognise my iphone, despite installing the virtualbox extension pack and iphone nominally being ‘passed through’ via the virtualbox ‘devices’ tab.
I’ve tried uninstalling the windows usb drivers (which then enables the iphone to be seen in the guest (via about this mac/system report)) but it doesn’t show up in xcode or itunes. Any suggestion? I am at the point where you start putting in the CMDs on Windows to alter the VM.
When I go to paste in the line after you cd into the directory, I get the following 3 error lines. VBoxManage.exe: error: Could not find a registered machine named ‘High Sierra’ VBoxManage.exe: error: Details: code VBOXEOBJECTNOTFOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee IUnknown VBoxManage.exe: error: Context: “FindMachine(Bstr(a-argv0).raw, machine.asOutParam)” at line 512 of file VBoxManageModifyVM.cpp. Hi, you’re awesome, great work! Unfortunately I get following error: Error allocating 0x14b6 pages at 0x900 alloc type 2 Error loading kernel cache (0x9) Boot failed. A critical error has ocurred while running the virtual machine and the execution has been stopped.
I’ve trying many times, even starting from scratch deleting the VM and starting again the procedure step by step, specially following carefully step #5, but all my attemps were unsuccesful Your help will be greatly appreciated! Okay, I have a new one. I am running Ubuntu 16.04, I installed everything and all works great, done some work/installations/configurations on the VBox with the MacOS. Now I bought a new laptop, I copied the vmdk file from the old laptop to the new as well as the.vbox and all the contents of the “MacOS Sierra” folder under “Virtualbox VMs” including the saved snapshot of the VM. I can resume the saved snapshot and it opens well, I can save it again and open but if I shutdown the MacOS and try to start it, it fails. Got any pointers? I copied a windows OS and it works fine.
What could be the problem and how should I fix it? Hello, I followed the instructions and have sierra 10.12 running (I have only 4 gb of ram and i could reserve only 2 for the virtual machine but it work fine the same). The problem is that the updates to 10.12.5 (also tried offline combo update to 10.12.5, 10.12.4 and 10.12.1). All the update reach the reboot phase but the machine stop to update at 17 min left or 10 min left (always 10 min left for update to 10.12.5). I don’t found a way to boot in safe mode inside virtual box nor to issue COMMAND+L or similarany suggestion?
Iam getting Guru Meditation Critical error, even if i done everything correctly with closing VBox during the cmd step. When i checked my log, its say something with CPU 0 changed to Meditation Mode: My Specs: OS: Windows 10 Pro CPU: Intel Core i5 7600K 3.80 GHz (7th gen Kaby Lake) GPU: ASUS Strix Geforce GTX 1060 OC6 (6GB version) RAM: 16 GB Corsair Vengance LPX 3000 Mhz (2×8 GB) Mobo: MSI Krait Gaming z270 Storage: (SSD: Samsung 850 Evo 250 GB) HDDs: WD Blue 1TB, Seagate Barracuda 1TB, WD “some shit” 400 GB. I’m having an error on Step 5 and I have the virtual machine off.
I even rebooted my computer. This is the error that appears: C: Program Files Oracle VirtualBoxVBoxManage.exe modifyvm “macOS Sierra” –cpui dset 00006e5 001e3fd bfebfbff VBoxManage.exe: error: The machine is not mutable (state is Saved) VBoxManage.exe: error: Details: code VBOXEINVALIDVMSTATE (0x80bb0002), compo nent SessionMachine, interface IMachine, callee IUnknown VBoxManage.exe: error: Context: “SetCPUIDLeaf(id, aValue0, aValue1, aValue2 , aValue3)” at line 742 of file VBoxManageModifyVM.cpp. I followed the instructions exactly, including the code steps. But I get the error shown at the link. I have VirtualBox 5.1.14 running on Windows 10, Intel Core i7-7700K with 64GB RAM. I limited myself to setting up the vb exactly as shown in the photos and I created a batch file from the included code. There were no errors when I ran the batch file.
I even named my Sierra vb the same as the example. Other OSes run fine in VB (Win 7, Win 8.1, Win Vista) on this PC so I know VirtualBox is installed correctly. Save this into a file, make it executable and run it. This worked for me running VirtualBox on a Debian Linux host following the steps almost 1:1Just have to modify the commands a bit – don’t need to “cd” – vboxmanage is already in your PATH on Debian when you install VirtualBox via apt.
Also, obviously remove the.exe extension from any of the other commands. Screen resolution fix also worked, although I would love to know how to set custom resolutions (namely 1080p). I think it would require also modifying some configs in the guest OS. I tried to work it out from some other info I found online, but nothing has worked so far.
Greatly looking forward to the tutorial on getting iMessage to work, as I see mentioned above in a comment from Jan 7 2017! THANKS FOR THIS!!!!!!!
Trying this setup on both VirtualBox 5.1.6 and the latest 5.1.2 and am getting the same “”A critical error has occurred while running the virtual machine and the machine execution has been stopped”” If I change the Paravirtual type to None – I get ““This version of Mac OS X is not supported on this platform” I have tried to remove all VirtualBox installations and start from scratch at least a dozen times and not getting this going anywhere. Any thoughts? Or specific parts of the VBox.log I can post to help get this going?. I have tried the latest code and run CMD as Administrator. Thank you for this tutorial!
For those who are getting the message “This version of Mac OS X is not supported on this platform” I had to enable some settings not specified in this tutorial (but were visible in the authors VirtualBox screenshot luckily!) System - Processor - Enable PAE/NX System - Processor - Acceleration - Paravirtualization Interface - Select Minimal System - Processor - Acceleration - Enable VT-X / AMD -V System - Processor - Acceleration - Enable Nested Paging Boom! Then I got it to boot into the installation screen ?. I started up the Virtual Machine and got UEFI interactive shell v2.1 EDK II UEFI v2.40 (EDK II, 0x00010000) Mapping table BLK0: Alias(s): pciroot(0x0)/pci(0x1F,0x2)/sata(0x0,0x0,0x0) BLK1:Alias(s): pciroot(0x0)/pci(0x1F,0x2)/sata(0x1,0x0,0x0) Press ESC in 1 seconds to skip startup.nsh or any other key to continue. Shell could someone help me out? It may be noted that I am trying to do this on another drive not the C: drive it is the M: drive the vbox is stored on this drive and so are all of the recommended download files. I also changed the command prompt code to M: instead of C.
I solved the infinite boot loop by selecting the correct CPU spoof:. For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors. This is super helpful — I followed every step, and it worked great! I’m running a Windows 7 host, and I’d like to get my mouse work smoothly in the guest macOS Sierra.
But something went wrong as I tried to get VBoxGuestAddtions installed on the guest macOS Sierra, please see screenshot: It’d be great if I could get some help. My Enviroment: Host: Windows7 + Intel i7-4790 VBox: 5.1.6 VBoxGuestAdditions5.1.6.iso from http://download.virtualbox.org/virtualbox/5.1.6/VBoxGuestAdditions5.1.6.iso. When I get to Step #5 and go to enter the first VBoxManage.exe line, I get this message:: VBoxVBoxManage.exe modifyvm “Sierra” –cpuidset 00006a9 04100800 7fbae3ff bfebfbff VBoxManage.exe: error: Could not find a registered machine named ‘Sierra’ VBoxManage.exe: error: Details: code VBOXEOBJECTNOTFOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee IUnknown VBoxManage.exe: error: Context: “FindMachine(Bstr(a-argv0).raw, machine.asOutParam)” at line 500 of file VBoxManageModifyVM.cpp What is causing this? The machine name is correct. I am trying to do this process using Portable-VirtualBox. Could that have anything to do with it? Try again from Step #5.
Add VirtualBox Code to the CMD Then use these codes linked below.