VMware Communities
bryanpjones
Contributor
Contributor
Jump to solution

Can't install Yosemite Guest on Fusion Pro 7.1.2

Odd issue here.  I'm running Fusion Pro 7.1.2 and can't install Yosemite as a guest inside 10.11 El Capitan...

Step I've followed:

  1. Downloaded Yosemite from the Mac App Store and moved the file into the ~/Downloads folder
  2. In Fusion - create a new VM using the "Install OS X Yosemite" file.
  3. Accept the defaults and save the VM to my local virtual machines folder.
  4. The VM boots first to the black Apple menu (and progress bar), and then into the OSX Utilities menu as expected.
  5. Here's where I get stuck.  I choose "Install OS X" and click the Continue button, but nothing happens.  I turned on the Installer Log viewer and see an error:

OS X Utilities[487:12972] Could not launch application.  Exception: launch path not accessible

I can launch the Disk Utility and do see a Macintosh HD formatted and ready to accept the OS as you'd expect.  I've even deleted that drive and recreated it successfully, but each time I return to the OS X Utilities menu, I can't proceed.

Help?

Thanks,

Bryan

0 Kudos
1 Solution

Accepted Solutions
dariusd
VMware Employee
VMware Employee
Jump to solution

Hi Bryan,

I've seen that exact problem before when the .app has been copied through a filesystem or protocol which doesn't support all the OS X metadata, such as FAT filesystems or NFS shares.  Could that explain the problem you're seeing there?

For maximum reliability when moving the .app around, I recommend using Disk Utility at the source to create a .dmg containing the whole .app, and copying it out of the .dmg onto an HFS+ volume at the destination.

Unfortunately, once the .app is in this state, I've not yet found a way to fix it so that it works again... I've just transferred/downloaded a fresh copy and started again with that.

Hope this helps!

--

Darius

View solution in original post

0 Kudos
3 Replies
dariusd
VMware Employee
VMware Employee
Jump to solution

Hi Bryan,

I've seen that exact problem before when the .app has been copied through a filesystem or protocol which doesn't support all the OS X metadata, such as FAT filesystems or NFS shares.  Could that explain the problem you're seeing there?

For maximum reliability when moving the .app around, I recommend using Disk Utility at the source to create a .dmg containing the whole .app, and copying it out of the .dmg onto an HFS+ volume at the destination.

Unfortunately, once the .app is in this state, I've not yet found a way to fix it so that it works again... I've just transferred/downloaded a fresh copy and started again with that.

Hope this helps!

--

Darius

0 Kudos
bryanpjones
Contributor
Contributor
Jump to solution

You could be right Darius.  I've certainly copied the installer to/from my NAS and it could have lost an attribute along the way.  I'll try your suggestion and also will change the way I archive OS X installers on my NAS.  Thanks for the tip and I'll provide feedback after the new installer downloads from Apple.

Thanks,

Bryan

0 Kudos
bryanpjones
Contributor
Contributor
Jump to solution

You nailed it darius‌!  Thanks so much for the help!

Bryan

0 Kudos