This informative article will demonstrate the comprehensive guide to fix VirtualBox mistakes while installing Mac OS X. Most sites producing content about the installment of Mac OS X El Capitan or macOS Sierra on VirtualBox aren’t complete and have errors. The guide may be right and operate on a single device perfectly and with no issue. However, there are plenty of devices and various types of errors. A couple of weeks ago, we made a post on the way best to set up Mac OS X El Capitan on VirtualBox, and the traffic has different sorts of issues.

OS X El Capitan. This version of OS X El Capitan is for users running OS X Snow Leopard who would like to upgrade to macOS Sierra. If you are running Snow Leopard and would like to upgrade to Sierra, you need to install El Capitan first. This version of El Capitan can also be installed on Mac computers that are not comparable with Sierra. Mac Os X El Capitan Iso Download For Virtualbox; Mac Os X On Virtualbox; Like macOS X El Capitan, macOS X Yosemite, macOS Sierra, macOS High Sierra, and macOS Mojave is out new and perfectly professionally made. With every feature of macOS Mojave, you are able to make your work easy.

Minimum System Requirements to install MacOS X on Virtualbox:

Minimum system requirements to install MacOS X on Virtualbox are: (It will help run macOS High Sierra or later versions without any problem.)

• Minimum 2 GB memory (Recommended 8GB or higher)
• Minimum 2 cores of processors (Recommended 4 cores or higher)
• Hard disk free space 40 GB (Recommended 100GB or higher)
• Your system should support Intel or AMD VT (Virtualization Technology)
• Intel/AMD VT (Virtualization Technology) Should be enabled from BIOS setup

For fast performance, try installing macOS X on SSD rather than HDD.

Required: Enable Virtualization Technology (aka Intel VT or AMD-V). See video below.

Some key points to remember before Installing Mac OS X:

1) Intel CPU works better than AMD

2) Turn OFF Antivirus programs (Windows Defender) and Windows Firewall before starting the install

3) Set Video RAM to between 64-128MB

4) Use no spaces in VM name (ex: “MACOSX” not “MAC OSX”). Also, no punctuation. Also, re-verify:

VM Type: Mac OS X and Version: Mac OS X 10.11 El Capitan (64-bit)

(These are in Virtualbox Settings->General)

5) Suggest use wired Internet, not WiFi, for initial download/updates, etc.

6) Run CMD window as Administrator when entering command-line commands.

7) May need to start Virtualbox as Administrator.

8) Be patient during initial boot up. It runs disk checks and other repairs… and can reboot a couple of times.

9) Be sure your HD or SSD has >80GB of free space. All the updates after initial installation gobble space.

10) Black Screen? Try video RAM > 64MB and Chipset = PIIX3

11) Do not install Virtual Box Extensions “CD”

12) Before adding commands on CMD, make sure you have quit your Virtualbox.

Unkown option –cpuidset

If you get this error “VBoxManage.exe: error: Unknown option. –cpuidset. The VM hangs on boot” while adding the first code in the Command Prompt. It’s because of the double hyphen. Use Double hyphen “- – “before cpuidset.

VBoxManage error: Could not find a registered machine named Your VM Name

If you get this error “VBoxManage error: Could not find a registered machine named Your VM Name“, it is because you haven’t used the correct name of your virtual machine when adding the codes on CMD.

You need to make sure you use the same VM Name you used when creating the virtual disk.

Missing Bluetooth Controller

If you get this error, make sure you close the virtual machine before adding the CMD codes.

Guru Meditation error or Black Screen

This error is majorly seen because of two issues-

The critical error happens due to the guest operating system. It is trying to switch to the PAE mode, which is currently disabled by default in VirtualBox. PAE support can be enabled using the VM settings (System/Processor)”.

1. Open VM VirtualBox
2. File -> Settings -> System -> Processor
3. Check Extended Features: Enable PAE/NX

OR,

For people with the black screen problem or Guro Meditationerror, change the operating system version from macOS 10.13 High Sierra (64-bit) or macOS 10.12 Sierra (64-bit) to just the Mac OS X (64-bit). If the error still exists, switch the Video Memory Size to 128 MB from Virtual machine settings. This is a significant issue with most of the users.

This version of Mac OS X is not supported on this platform Reason: Iloveapple

Make sure Virtualization Technology (VT) is enabled from BIOS.

error: VBoxManage setextradata “OSX” “VBoxInternal/Devices/smc/0/Config/DeviceKey” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc” and you are stuck at appleKeyStore: operation failed (pid:30 sel:7 ret:e00002c2 ‘-536870206’)

Exit VirtualBox before adding codes to CMD

Yhal Htet Aung

Try to change the inverted commons throughout the virtual codes. Since you are copying the codes, you might be using the wrong inverted commas.

So, copy the codes in your notepad file, replace all the inverted commas via your keyboard and then try again.

Invalid Virtualbox Version

Make sure you add the right virtual codes. You can download the correct version codes here-

Stuck in an infinite loop on Black Screen

Try using this command as the last command on CMD-

VBoxManage modifyvm “VM_name” –cpu-profile “Intel Core i7-6700K”

Or,

Try Motherboards Chipset – both PIIX3 and ICH9 one by one

install.nsh is not recognized as an internal command

1st method:
If you get ‘install.nsh’ is not recognized as an internal or external command, operable program, or script file. You have not attached the Virtualbox Boot Image.

See, https://www.geekrar.com/fix-macos-catalina-install-nsh-isnt-recognized-as-an-internal-error/

2nd method:
If you then get messages along the lines of ‘macOS Install DataLocked FilesBoot Filesboot.efi’ missing or not recognized:

run setup.nsh

now run, fs0:SystemLibraryCoreServicesboot.efi

and all should now spring into life.

3rd method:

1. At UEFI prompt: Type exit
2. You’ll be brought into an EFI text-mode GUI.
3. Select Boot Maintenance Manager and click.
4. Select Boot From File and click

Mac Os El Capitan Virtualbox

You should see two entries in a list (they are cryptic looking PCI bus paths).

The first PCI path in the list is probably the boot partition that doesn’t contain bootable firmware. The second PCI path is probably to the recovery partition, the one you need to boot from. If the 2nd partition isn’t the recovery partition, look under the paths in the list to see if one of them is it. If the recovery partition isn’t present and valid, these instructions won’t work.

Click the 2nd entry, you should see (and then click):

macOS Install Data

Then click:

Locked Files

Then (if present), click

Boot Files

And finally click:

boot.efi

The installation will continue, or you will boot into the OS or get the Recovery utility menu (where macOS can be reinstalled from or Disk Utilities run). The ambiguity of that last statement is I did that awhile before writing this comment, and I don’t recall what I booted into first, only that it worked and was not hard to figure out what to do at that point. If you have a recovery partition, to boot directly into the Recovery Mode, turn on the Mac and immediately press and hold (⌘)-R

Set screen resolution

Use the following command-

cd “C:Program FilesOracleVirtualBox”

VBoxManage setextradata “VM Name” VBoxInternal2/EfiGraphicsResolution 1440×900

If you are still facing some issues, try using VMWare to install macOS on your Windows. When your current PC does not support Virtualbox and its configurations, try switching to VMWare. The process for it is relatively painless.

Share files and folders between Windows and MAC on Virtual Machines

You can go through this complete guide- How to share folders on VirtualBox & Vmware? (Windows-MAC) Step by Step Guide

I tried installing macOS Catalina on Virtual on Windows 10 on a low configration system. You can watch the video tutorial here-

Macos El Capitan Iso Virtualbox

One well known issue of running a guest MacOS X under VirtualBox is that it'snot possible to enter Recovery OS by pressing the Command+R key combination onVM startup. In fact after reading some bug reports on VirtualBox bugtracker itseems that it's not possible to enter Recovery OS at all.

Fortunately, we don't even need Recovery OS to disable System IntegrityProtection. We can use the Installer environment to run csrutil tool. SIP'sconfiguration is stored inside NVRAM, so it actually doesn't matter whatapproach we will take, as long as we will put some magic values into magicvariables inside NVRAM. Please be advised that while this method works, it willwork until the shutdown of your VM. You can do soft restarts, but if you'll shutdown the VM and boot it up again, you will need to disable SIP again.

In order to access Installation environment under VirtualBox, you will need toenter the VirtualBox EFI BIOS by pressing F12 few times, at very early stage ofguest VM boot up.

You will be greeted with an old school text mode BIOS interface, in which youshould choose the Boot Manager option.

Inside, launch EFI Internal Shell to enter EFI commandline mode.

After getting the command prompt, switch to the FS2: drive:

Of course, your drive number can be different, depending on the partition tablestructure you've chosen to have.

On the FS2: drive, in com.apple.recovery.boot directory, there is a EFIprogram inside the boot.efi file. We need to launch it.

Any errors that start with ERROR!!! can be safely ignored! :)

The Installation Environment should now start booting up, this can take severalminutes to complete.

When it will load, you need to launch the terminal, from which you will be ableto use the csrutil command:

I've uploaded a video that walks through these steps, so if you'll have anyproblems in understanding anything, you can watch it, maybe it'll help.