Complete Guide to Fix VirtualBox Errors While Installing Mac OS X
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.
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.)
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)”.
For people with the black screen problem or Guro Meditation error, 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”
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.
2nd method:
If you then get messages along the lines of ‘\macOS Install Data\Locked Files\Boot Files\boot.efi’ missing or not recognized:
now run, fs0:\System\Library\CoreServices\boot.efi
and all should now spring into life.
3rd method:
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
Locked Files
Then (if present), click
Boot Files
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 Files\Oracle\VirtualBox”
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
I tried installing macOS Catalina on Virtual on Windows 10 on a low configration system. You can watch the video tutorial here-
Boot on sierra
gamerlozano
My system is
H67-usb3-b3
Core I7 3770
8gb ram 1333
Ssd adata xpg 256
Attachments
BreBo
Moderator
gamerlozano
thank you, just disable usb3 from BIOS and is working, now i have another problem, sometimes, and just somthimes, my hackintosh starts but in low resolution (1024*768) and all graphics show laggy, and bad, and sometimes, boots just fine, in my config.plis i have this
according i already read, this must work, but the same problem, any ideas? thank you again
BreBo
Moderator
gamerlozano
yes i do
8
Scan
Entries
First
Tool
ScreenResolution
1920×1080
Theme
tonymacx86
Graphics
and i dont use any ig-platform-id
i just added like this
ScreenResolution
1920×1080
Theme
tonymacx86
ig-platform-id
0x01620005
Jithin.C.V
Boot to OS X normally and run below command on Terminal.
gamerlozano
Boot to OS X normally and run below command on Terminal.
)
com_driver_LogJoystick: robe(IOResources)
com_driver_LogJoystick[
btw i just add this 5 minutes ago this in config.plist
ScreenResolution
1920×1080
Theme
tonymacx86
ig-platform-id
0x01620005
Post 13.3.3 upgrade failure
GinoTheCop
I have installed 13.3.3 onto my system and it worked liked charm for 2 days. Then while I was working it suddenly rebooted and now sticking on the boot screen.
verbose mode message says;
and above message loops forever.
I copied FakeSMC.kext from Others to 10.13 as well under EFI/CLOVER/kexts
but still the same..
Any suggestions or ideas? I am stuck in the mid of my work and cannot boot..
cmn699
I have installed 13.3.3 onto my system and it worked liked charm for 2 days. Then while I was working it suddenly rebooted and now sticking on the boot screen.
verbose mode message says;
and above message loops forever.
I copied FakeSMC.kext to 10.13 under EFI/CLOVER/kexts
but still the same..
Any suggestions or ideas? I am stuck in the mid of my work and cannot boot..
GinoTheCop
cmn699
GinoTheCop
I have the bios defaults set and then Intel GPU disabled from the bios (been using it like that for like few years now)
The disk is a SSD with APFS, the bios is set to boot from that disk only. (again same settings for years)
The contents of the CLOVER (will share)
The picture of the verbose screen is below;
GinoTheCop
Returned to 10.13.2 with Time Machine.. Boots OK now..
I will need to investigate why this happened.
cmn699
Returned to 10.13.2 with Time Machine.. Boots OK now..
I will need to investigate why this happened.
The former is from the inability to find the right Graphics card to boot and the latter verbose boot error ( The current «Waiting for DSMOS) is from a missing DSMOS in the expected folder /EFI/CLOVER/kexts/Other or as a result of some other Folders blocking the path to this critical folder «Other».
All the named folders: «10.6 to 10.13» in /EFI/CLOVER/kexts are unnecessary, serve no useful purpose, and often contribute to boot freeze in macOS High Sierra System disk. It is a good practice to delete them.
GinoTheCop
The uploaded screen shot was the result of your «troubleshoot» for the wrong diagnosis of
«DSMOS has arrived» and the screen going to sleep or turning Black. That error is different from «Waiting for DSMOS» as shown in the recently uploaded image.View attachment 319107
The former is from the inability to find the right Graphics card to boot and the latter verbose boot error ( The current «Waiting for DSMOS) is from a missing DSMOS in the expected folder /EFI/CLOVER/kexts/Other or as a result of some other Folders blocking the path to this critical folder «Other».
All the named folders: «10.6 to 10.13» in /EFI/CLOVER/kexts are unnecessary, serve no useful purpose, and often contribute to boot freeze in macOS High Sierra System disk. It is a good practice to delete them.
Ошибка при чистой установке Mac OS X
При установке OS X El Capitan или OS X Yosemite могут появиться ошибки:
«This copy of the Install OS X El Capitan application can’t be verified. It may have been corrupted or tampered with during downloading» или «This copy of the Install OS X Yosemite application can’t be verified. It may have been corrupted or tampered with during downloading», ну или «An error occurred while preparing the installation. Try running again».
«Не удалось проверить этот экземпляр программы Установка OS X Yosemite (Mavericks). Он мог был быть поврежден или подвергнуться изменениям в процессе загрузки.»
Иногда они могут быть решены путем простой перезагрузки и попытки переустановки OS X еще раз (или повторной перезаписи дистрибутива на флешку/диск, если он был поврежден), но если сообщения об ошибках появляются постоянно, то можно решить проблему только сменой даты на вашем Mac.
Меняем дату на Mac
Сделать это можно не выходя из меню установки, использовав терминальные команды. Для этого запускаем «Терминал» и вводим команду:
После чего вам отобразится установленная в данный момент дата. Ее нужно поменять, задав дату выпуска дистрибутива.
Дата и время вводятся в определенном формате: [mm]dd]HH]MM[[cc]yy]. Расшифровывается это так: Месяц Число Часы Минуты Секунды Год, введенные без пробелов и, обязательно, в такой последовательности.
К примеру, если нужно установить дату и время на 24 октября 2015 года 18 часов 25 минуты, то команда будет выглядеть так:
Смысл в том, чтобы выставить дату, позже выпуска вашего дистрибутива, но раньше выпуска следующего обновления. Экспериментируйте!
После этого закрываем «Терминал» и начинаем процесс установки.
Если вы нашли ошибку, пожалуйста, выделите фрагмент текста и нажмите Ctrl+Enter.
Applekeystore Operation Failed Virtualbox
Listing Of Websites About applekeystore operation failed virtualbox
Posted at: 1 week ago | Categories: FAQs | 121 People Used View Detail
Posted at: 4 days ago | Categories: FAQs | 196 People Used View Detail
Error : applekeystore operation failed | Rossmanngroup Forums
Posted at: 3 days ago | Categories: FAQs | 450 People Used View Detail
Posted at: 1 week ago | Categories: FAQs | 283 People Used View Detail
Posted at: 1 day ago | Categories: FAQs | 205 People Used View Detail
Applekeystore operation failed virtualbox» Keyword …
Posted at: 1 day ago | Categories: FAQs | 468 People Used View Detail
Posted at: 2 days ago | Categories: FAQs | 307 People Used View Detail
Posted at: 1 day ago | Categories: FAQs | 405 People Used View Detail
Posted at: 1 week ago | Categories: FAQs | 378 People Used View Detail
macOS Big Sur on VirtualBox : virtualbox
Posted at: 1 week ago | Categories: FAQs | 154 People Used View Detail
Posted at: 4 days ago | Categories: FAQs | 413 People Used View Detail
Posted at: 1 week ago | Categories: FAQs | 81 People Used View Detail
「applekeystore operation failed e00002c2」でMac起動しない！ …
Posted at: 1 week ago | Categories: FAQs | 239 People Used View Detail
Virtualbox Apple
Posted at: 5 days ago | Categories: FAQs | 439 People Used View Detail
Install El Capitan On Virtualbox
Posted at: 5 days ago | Categories: FAQs | 292 People Used View Detail
Posted at: 1 week ago | Categories: FAQs | 422 People Used View Detail
Posted at: 1 week ago | Categories: FAQs | 246 People Used View Detail
Posted at: 3 days ago | Categories: FAQs | 238 People Used View Detail
Virtualbox Macos Install
Posted at: 4 days ago | Categories: FAQs | 136 People Used View Detail
Posted at: 2 days ago | Categories: FAQs | 413 People Used View Detail
Posted at: 1 week ago | Categories: FAQs | 121 People Used View Detail
Install Macos Catalina On Virtualbox Windows 10
Posted at: 6 days ago | Categories: FAQs | 215 People Used View Detail
Install Macos Catalina On Virtualbox Windows 10
Posted at: 5 days ago | Categories: FAQs | 468 People Used View Detail
Oracle Client For Mac High Sierra
Posted at: 1 week ago | Categories: FAQs | 85 People Used View Detail
How do I install VirtualBox on my Mac?
Now, that you’ve executed the macOS Sierra VirtualBox code. Open the VirtualBox app then click the Start button to power on the VM. A black screen with a lot of white text will appear on the screen. Just wait for a few minutes and the macOS Sierra installation will start.
Why do I get missing bluetooh controller in VirtualBox?
You’ll see all your Virtual Machines (in case you have more than one). At the right of the Mac image is the GUID of the machine. Copy that GUID an replace it for the name of the VM in the command. You are getting the “Missing Bluetooh Controller” error because you are running the commands (Step# 5) while the Oracle VM software is open.
Why does vboxmanage.exe hang on boot?
How do I shut down VirtualBox on Mac?
When the macOS initial setup starts, shut down macOS with Command-Q Set the virtual machine’s USB version to 1.1 and disable all network adapters from the VirtualBox settings (AppleKeyStore, the system’s secure keychain, crashes otherwise) After initial setup is complete the USB settings and network adapters can be restored.
