2

I am trying to downgrade a MacBook from Yosemite to Mavericks.

I have created a bootable USB with Mavericks, restarted and booted from USB. When I select Install OS X and click Continue, nothing happens:

Screenshot OS X Utilities

I checked the Installer log and this is the error message it is giving me:

OS X Utilities[384-303] Could not launch application. Exception: launch path not accessible.

Do you know what could be happening ?!

I would appreciate any information about this, thank you!

Best regards.

  • I ended up creating another bootable USB and it worked fine. – Eduardo Amador Aug 26 '15 at 15:38
  • please post that as an answer, @Eduardo – Sathyajith Bhat Sep 7 '15 at 10:06
2

From our experience here, it doesn't matter if you're downgrading or installing OS X from scratch. Also, we had this issue with physical as well as (VMware Fusion 8.1.1 Pro) virtual machines with exactly the described symptoms. Upgrading seems to work OK.

The cause seems to be that copying the installation file downloaded from the Apple App Store (called Install OS X Mavericks.app or Install OS X Yosemite.app or Install OS X El Capitan.app, couple of GB in size) to a non-Mac file system (Linux ext4fs shared over Samba here) removes or alters some file meta data. That at least is our best guess about the actual cause.

The file is still good to create USB boot sticks (which later on then expose the same problem) or go through the basics of a VMware VM setup, but when it comes to the point of actually installing the OS, clicking the Install button does nothing and the error message detailed in the question is printed to the installation log.

Solution: Store the installation medium on OS X file systems only.

See also this VMware forum post for more information. As mentioned, the problem is not related to VMware though, it's yet another OS X issue.

  • As the VMware forum post mentions, you can create a disk image of the app, and then safely store that disk image on foreign filesystems. – ryandesign Sep 20 '17 at 0:42
  • I was able to resolve this issue by running chmod -R +x . after changing directories to the USB media. – Alex Gittemeier Oct 16 '18 at 7:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.