1) On your existing macOS, go to the App Store and download the High Sierra installer. Some people have reported that a stub installer is only downloaded although this has not happened to me. If it happens to you, follow the instructions on this page: -complete-macos-high-sierra-installer/
3) Create a new Virtual Machine in VMware Workstation. Select "Apple Mac OS X" as the Guest O/S and "macOS 10.12" as the version.
Select the default for all other options (although I prefer to have the virtual disk as one single file)
When you start Disk Utility, look on the upper left and change the View option from Show Only Volumes to Show All Devices. If the virtual disk does not show up, exit Disk Utility and then restart it. I don't know why, but I have seen this where it doesn't seem to detect the drives upon initial load.
If you are stopping on the EFI boot screen which shows that the boot path is "Unsuccessful", then you did not disable the virtual SSD properly. Look at your VMX file and check the type of disk used. The sample I showed above is the default where the VMware virtual disk is a SATA drive and mounted as the first drive. Therefore the line below properly disables the virtual SSD emulation in the virtual machine.
Just for the record, I had a similar problem updating from Sierra to High Sierra on Workstation 11.1.4 (OS wouldn't boot after the last restart). Setting sata0:0.virtualSSD = "0" before updating solved the problem.
I should take this opportunity to report that the resulting volume, while it did not lead to a reinstallation of the operating system, did successfully boot. It did, however, leave the /macOS Install Data folder on my install partition, which I'm about to delete, since the converted partition already boots into a working installation.
I converted the TimeMachine volume of to APFS as it showed up under the Edit Menu in Disk Utility. I decided that the Boot Volume should also be converted but did not see the Convert to APFS volume under the Edit menu. I know from times past the cmdline DiskUtils has way more options than the GUI. I suspected I could conver to APFS using Terminal+diskutils. I did that conversion to disk0s2 (my HFS+ data volume).
Followed that same advice, I did a dirty re-install of High Sierra Beta 7, that fixed enough of the partition entries and blessing to force it to boot the Disk02s. I just had to be very, very patient, and keep my hands off the mouse and keyboard out of fear of interrupting whatever process it was going through to tie the boot files to the APFS converted disk partition.
It's really not worth the effort of getting it up and running again even if it's just a sacrificial test machine or VM. If it does show Convert to APFS under the Edit menu, give it shot. I converted my TimeMachine volume to APFS, but boot volume wasn't having it. Using Terminal and diskutil cmdline, forced it, but then it wouldn't bless.
I had this same problem happen to me recently. Went to reinstall high sierra (was currently running beta 8), went into recovery mode (Command +R at boot), erased the hard drive in diskutility and reformatted it in APFS encrypted. Went into the reinstall macOS and as it worked through the 8 minutes it would stop at the end with a pop up message saying "Could not create a preboot volume for APFS". This made things interesting so I tried reformatting the drive with the unencrypted APFS and still same error. I eventually made a really stupid move from diskutility and from the disk0 drive itself I right clicked and chose to Erase, somehow thinking what harm could be done at this point, thinking it would erase and reappear. Well that never happened. The internal disk0 drive did not come back. I ended up trying to create a backup from another computer and installing the backup to that. This didn't work either since it couldn't find the internal hard drive.
I created a bootable thumbdrive with high sierra from another computer and used that to boot up, and still the internal drive wasn't an option on diskutility. what eventually worked was somehow the drive appeared when I booted into recovery mode with the install thumbdrive and having another thumbdrive in the internal drive finally appeared. I was able to then format it again as APFS. It then populated when I did the reinstall from the install thumbdrive. After that it worked fine.
In hindsight I know I shouldn't have erased that drive, and I likely could have reformatted disk 1 from terminal and seen if it would repopulated in diskutility then. But either way the lesson here is don't erase the internal hard drive from diskutility. If you get that preboot error I would suggest creating a bootable thumbdrive from another computer and using that to enter recovery mode and doing the install this way.
Hi, I'm currently facing the same "Could not create a preboot volume for APFS" issue after i erased the drive from diskutility. I was on the latest version of High Sierra yesterday. Kindly, give me the lines of code necessary to create the bootable usb (especially with the changes you've mentioned). I'm new to macOS. So please bear with me.
I'm having the same issue on a MAC BOOK AIR 2017. First time it gave the error could not contact sever but after countless efforts I managed to to download via the MAC internet recovery afte the download this error popped up.Is there a solution for this ?
Hi I had the same problem. Did the same thing for about 3 times. Format the drive first to apfs 1.Power down the mac. 2.hold the Option-Command-R and power button. 3.a world logo will show and start loading. 4.reinstall mac os in recovery. 5.no more error "could not create a preboot volume for apsf install" Hope this helps
As mentioned in the section above, your system should have the virtualization technology, and after that, you should enable that from your system BIOS. First, you should boot into your system BIOS then find the VT option and enable that. You can find how to boot into your system BIOS by this guide. Enable Virtualization Technology from the host machine.
Once you have downloaded the macOS High Sierra image file, then you should extract it via WinRAR or 7zip after that you can use this image. To unzip the file, just right-click on the file, then selectExtract Here. It will take around 5 minutes.
#1. Now go to macOS High Sierra virtual machine files that you browsed and located in step 4.4. If you have left that steps as default then the files are saved in this location: This PC > Documents > Virtual Machine > virtual machine Name. Here you need to replace the macOS High Sierra Image(8.87GB) with this existing VMDK (5 MB). Just drag the macOS High Sierra Image that you download and extract in step #1 then drop it on the Virtual machine files. If you get a replace or skip files dialog box, then click on Replace them in the destination.
Note: You have to name the macOS High Sierra Image as your virtual machine name. It should be the same in order to be replaced and make it work otherwise; you need to add the image manually. Also, the size should change from 5 MB to 9.57 GB after you replaced the VMDK.
I hope you guys have gotten something from this step by step guide. If you have any kinds of problem or question, feel free to share via comment section down below. Also, in the section below, there are more guides that may help you out. So go ahead and check out them, thanks for being with us.
Now that you have, install macOS High Sierra on VMware on Windows successfully still there are many things need to fix manually. One of the most important ones is the VMware, and you need to install the VMware tool on macOS High Sierra to get the most of macOS High Sierra on Windows. Many features like drag & Drop, fix screen resolution, network and other issues will be fixed after you install VMware tool. We have a create a simple guide to do that so follow the step by step guide.
I know this is like 2 years later and may not mean anything anymore, but your issue is because this article only has the toolkit for Workstation 12 and 13. I tried this toolkit with workstation 15.5, and had the same issue. Do some searching online for your version then try to install the tools again.
I am using vmware player in windows 10 and macoshigh sierra is installed.
My total memory is 16 GB and i allocate 10 GB for vmware player (i.e) macoshighsierra, but it continously freezes when i work for long hours.
Hello, I need your help. I installed vmtool, but when it arrives with .vmware.fusion.tools.darwin. the screen glue, has already opened the VMware Workstation 14 Player and does not appear the Apple Mac OS x option. what do I do
Was able to update successfully to 10.13.2 thru the App Store.
Tried the Combo Update first because I already had it downloaded but it failed because of the Fusion drive issue with the Beta of 10.13.
I tried to leave a reply now my next try:
Great tutorial THX
I got a problem, my virtual disk is getting slightly full after some hours, system freezes cause of a full disk. I am using vmware workstation pro 14 now I am trying BIOS settings instead of UEFI and I placed vmdk i another folder looks better. I had some time machine stuff, disabled also because this could be also a problem. Anyone same issues?
Great tutorial, THX
I Got one strange issue and I have not read all comments, I will do.
The VM with OSX Sierra fills the virtual disk slightly with some stuff, did not know what, problem is that than VM is hanging up and freezes cause of full disk.
Maybe a time machine issue or something else.
Got anyoe of you same difficulties, all worked fine wit VMware workstation pro 14 and I got also after installing VMware tools a big screnn, I am using a tripple screen setup with 32401920 Pixels and it was nice to look at, a little anoying is that no 3D acceleration is working out of the box, are there any known projects?
THX for posts cya