Macos High Sierra 10.13 Disk For Virtualbox

Let’s Download MacOS High Sierra Image File for Virtualbox & VMware, however, the current Apple OS is MacOS Catalina 10.15 that announced and released in 2019, besides that, macOS Mojave 10.14 is also the greatest operating system having tons of feature But still, MacOS High Sierra 10.13.6 is in high demand and legions of people are installing MacOS High Sierra on Macbook, Mac Mini. Update google for mac os x. Jan 15, 2020 How to Setup macOS 10.13.6 on VirtualBox 6.0.8 in Windows 10. Apple has released Mac OS High Sierra 10.13.6 update for Mac users. Mac users can update their computers by downloading the 10.13.6 update from the Apple Store.

If you work on a Mac computer and need to read or write files from HDD, SSD or a flash drive formatted under Windows, you need Microsoft NTFS for Mac by Paragon Software.Write, edit, copy, move and delete files on Microsoft NTFS volumes from your Mac! Supports macOS 10.15 (Catalina). Mount, unmount, verify, format or set any of your Microsoft NTFS volumes as a startup drive.New! Ntfs for mac free trial. Fast, seamless, easy to use.

NOTE: The instructions to create an ISO from any OSX Install application are covered in another article.

Install OSX 10.13
  1. Create a new VM with the 10.13 template. Accept the defaults, with the exception of RAM (at least 3 GB), number of vCPUs (at least 2) and amount of HD (according to your needs, no less than 10 GB). Also make sure that USB3 controller is selected under the Ports » USB. Choose the newly created ISO as your boot medium.
    NOTE: Do NOT designate your virtual HD as an 'SSD'. The installation WILL fail if you do that, because the OSX installer will convert the filesystem to APFS, something that the VirtualBox EFI can not handle.
  2. Start the VM. It may seem that the installation stalls but don't shut the VM, be patient. Specifically, right before you switch to the graphics with the Apple logo and the progress bar, you'll get stuck at the point where the OSX ≥ 10.12.4 gets stuck:
  3. After selecting the language, open 'Disk Utility'. For reasons that only Apple engineers understand, you will *not* see your hard drive! Instead you'll see a bunch of partitions that are of no interest to you whatsoever (see NOTE below). On the top-left side, click on the 'View' drop-down and select 'Show All Devices'. Now you'll see your 'VBOX HARDDISK Medium'. Select it and choose 'Erase' from the toolbar. Leave the defaults (HFS+J/GUID), except maybe the name, choose anything you like. Quit 'Disk Utility' once done.
    NOTE: This 'glitch' has been fixed with 10.13.2. Now the hard disk shows properly when Disk Utility is opened.
  4. Select 'Install macOS'. Continue and agree to the license. This will start a phase where the actual installer is copied to the Recovery Partition of the hard disk that you selected. That part is rather quick, lasting less than a couple of minutes on an SSD drive. After that your VM reboots. But, you won't re-boot into the OSX installation phase, you'll restart the whole installation again from scratch! Houston, we have a problem!!! If you're observant, you'll notice a quick message coming up, right before the VM boots again from the ISO to restart the whole installation process:
  5. Apple (another wise move) has modified the way that it reads/treats the different partitions in the EFI, something that currently VirtualBox cannot handle (as of 5.2.2). But, there is a solution. Once you find yourself up and running, right after the language selection step, shut down the VM and eject the 10.13 ISO that you booted from. Then boot the VM again. You get dropped in the EFI Shell.
  6. You need to keep resetting the VM (HostKey+R) and press any key until you get into the EFI menu screen. If you don't succeed, and you end up in the EFI shell, enter 'exit'. That will you get to the EFI menu, shown below:
  7. Select the 'Boot Maintenance Manager' option, then 'Boot from File'. Now, you should have two options. The first one is your normal Boot partition, but this is not yet working, because you haven't yet installed 10.13. This is where the VM should be booting up from normally, and this is why it fails to boot. The second partition however is your Recovery partition. This is the one you should boot from to do the installation. This could be also used to do a re-installation of 10.13, just like on a real system, should the need arise.
    BootFromFile.png (48.02 KiB) Viewed 77090 times

  8. Choose the second option, then '<macOS Install Data>', then 'Locked Files', then 'Boot Files', and finally 'boot.efi' and let the games begin!
  9. That second part of the installation is where 10.13 actually gets installed. This is going to take substantially more time, about 20-30 min with the VM consuming every available CPU cycle. The VM will reboot a couple of times but you should be all set.
PS: There is also another guide, which I discovered after I wrote this guide, that contains some pretty pics in case you get confused by the text-only instructions: http://tobiwashere.de/2017/10/virtualbo .. st-system/Getting the following error when trying to create a High Sierra VM.
The DMG does mount, but VirtualBox refuses to use it for a VM.
Failed to open the disk image file /Volumes/L/Software 2016/Mac OS X/10.13 High Sierra/MacOS_High_Sierra_v10.13[Developer_Beta_4]/macOS_10.13_Beta_4[17A315i].dmg.
Could not open the medium '/Volumes/L/Software 2016/Mac OS X/10.13 High Sierra/MacOS_High_Sierra_v10.13[Developer_Beta_4]/macOS_10.13_Beta_4[17A315i].dmg'.
VD: error VERR_VD_DMG_INVALID_HEADER opening image file '/Volumes/L/Software 2016/Mac OS X/10.13 High Sierra/MacOS_High_Sierra_v10.13[Developer_Beta_4]/macOS_10.13_Beta_4[17A315i].dmg' (VERR_VD_DMG_INVALID_HEADER).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component: Macos High Sierra 10.13 Disk For Virtualbox
MediumWrap
Interface:
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}Macos High Sierra 10.13 Disk For Virtualbox
Callee:
IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
Callee RC:

Macos High Sierra 10.13 Disk For Virtualbox 8

VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)