As you already know, macOS High Sierra includes a new file system APFS. If your system drive is solid state, the installer will convert from HFS+J to APFS in both a fresh install scenario and an update scenario. Fortunately, there a ways around this automatic conversion. It is controlled by the ConvertToAPFS option in /macOS Install Data/minstallconfig.xml, which can be controlled by using 'startosinstall' from Terminal, or edited after the fact (see post #2). Note: This guide does not apply to macOS Mojave (or later). Apple has removed this option and will force APFS conversion. You can use CCC (Carbon Copy Cloner) to clone from APFS to HFS+J, but that may be a fight you have to take on every update going forward. Star wars battlefront 2 free pc download. Microsoft outlook for mac wont send email.

If you're running Mojave, you will probably end up adopting APFS. Update scenario using 'startosinstall' After downloading the 10.13 installer, instead of running it, quit. Then in Terminal. /Applications/'Install macOS High Sierra.app'/Contents/Resources/startosinstall --converttoapfs NO --agreetolicenseThe system will copy some files, then reboot, and you'll be able to start the installer (without APFS conversion) by booting the 'Boot macOS Install from.' Option in Clover. Fresh install scenario (or update) using 'startosinstall' You may be able to use the startosinstall in the fresh install scenario by invoking it from Terminal after booting the installer from USB. But when I tested it in the betas, it did not work, likely due to a bug in the startosinstall code that prevented it from running from the installer.

It seems to be fixed by Apple in later releases of the 10.13 installer. Terminal is available from the 'Utilities' menu within the macOS installer. If you were to attempt it, the USB installer volume (install_osx if following my guide), appears to be mounted at /Volumes/'Image Volume'. /Volumes/'Image Volume/Install macOS High Sierra.app'/Contents/Resources/startosinstall --volume the_target_volume --converttoapfs NO --agreetolicenseNote: Change the_target_volume as appropriate for the actual name you decided to use for your macOS target volume. Hopefully it is obvious that the target volume must already be formatted as HFS+J. The --volume option is not available unless running with SIP disabled. Settings for disabling SIP are provided in the plists linked by the Clover laptop guide: Alternative methods Read post #2: Background information.

The recommended methods are in post #1. This post contains alternatives that may still be useful in scenarios that post #1 methods may not be possible. Fresh install scenario (or update), modifying minstallconfig.xml using PlistBuddy Refer to this guide for an overview of the installation process from USB: The process involves creating an installer USB with createinstallmedia, then booting that USB (via Clover on the same USB). You then run the installer, create an HFS+J partition suitable for macOS with Disk Utility, then point the installer to that partition. Even though you create a new HFS+J partition, if the target is an SSD, the installer will still convert it to APFS.

To avoid that, after running the installer, and upon the first reboot where you would be normally directing Clover to boot the next stage of the installer by selecting 'Boot macOS Install from.' , instead, boot the 'install_osx' partition on USB again. When that is finished booting, choose Terminal from the Utilities menu. Now, in Terminal, navigate to your target volume. # list /Volumes to remind yourself of the name you gave it ls -l /Volumes # then change your working directory to it (in my case, I used '1013') cd /Volumes/1013 # now change to the 'macOS Install Data' directory cd 'macOS Install Data' # now fix the minstallconfig.xml with PlistBuddy /usr/libexec/PlistBuddy -c 'Set:ConvertToAPFS false' minstallconfig.xmlThat's it! Now you're ready to quit Terminal, reboot, and continue the installation process by booting the 'Boot macOS Install from.'