Hot answers tagged

3

Here's an updated procedure for Windows 10, based on orkoden's excellent answer. I tested this process on a MacBookPro11,1 running OS X 10.11.5 (15F34). Throughout the process, directly connect all devices to your Mac. I found that certain operations failed more frequently if I used the USB hub in my monitor. In addition to the external drive that will ...


1

The results you posted from the readgpt command leads me the following conclusions about your drive's partitions. The six partitions are listed in the order found on the drive. ~200 MB EFI partition (Usually hidden from the user) ~100 GB Windows partition ~75 GB OS X partition ~50 GB Windows partition ~650 MB OS X recovery partition (This is exactly the ...


1

The use of Core Storage seems to be a common denominator in problems similar to mine. I used the sudo diskutil cs revert [Logical Volume guid] command in the Terminal application to get rid of Core Storage, and then restarted. Presto! My missing GBs were returned. The above command can only be used if the command diskutil cs list shows the Logical ...


1

When using the Winclone product to install Windows on a external USB drive, it is extremely important that you first read all the instructions provided by Winclone. Winclone provides the Web page: Running Windows from an External Drive. This page provides links to two videos. The first link is the same as given in your question. The second link provides the ...


1

The solution for fixing Boot Camp Assistant was the same as with previous versions of the OS: reset the NVRAM. I found a discussion mentioning a similar problem with an upgrade to Yosemite here that I intiially disregarded as it referenced repairing permissions and running a Disk Verify, neither of which Disk Utility appears to support anymore. As for ...


1

To most easily resolve this, you need to erase your USB drive with a "Master Boot Record" scheme. Steps: Open Disk Utility Select the USB drive Click "Erase" Choose Format "MS-DOS (FAT)" MOST IMPORTANT: Choose Scheme "Master Boot Record" Click Erase button Many thanks to nholtappels for figuring out the problem!


1

If you want to EFI boot the installer you need to flash your firmware from MacPro4,1 to MacPro5,1. Create an installer like mentioned here without any bootmgr files to force an EFI boot. Remove all disks from Mac Pro to avoid further trouble with Mac EFI looking for MBR or protected MBR. EFI boot your installer. Be sure to clean the unneeded Bootcamp ...



Only top voted, non community-wiki answers of a minimum length are eligible