Let me explain entries 4,5,6 in your current setup.
GPT4 = Microsoft System Reserved - Used on GPT disks for EFI installation. It is internal data used by Windows, similar to a BCD.
GPT5 = Main NTFS partition.
GPT6 = Windows RE (Recovery Environment).
BCA cannot clean this properly. It has to be done manually. The following terminal commands need to be exactly typed otherwise there is potential for data loss.
A. Merge disk0s4 - disk0s6 into a single FAT partition.
diskutil mergePartitions fat32 BOOTCAMP disk0s4 disk0s6
This is the syntax help for the command. Please read the note below the example.
diskutil mergepartitions
Usage: diskutil mergePartitions [force] format name
DiskIdentifier|DeviceNode DiskIdentifier|DeviceNode
Merge two or more pre-existing partitions into one. The first disk parameter
is the starting partition; the second disk parameter is the ending partition;
this given range of two or more partitions will be merged into one.
All partitions in the range, except for the first one, must be unmountable.
All data on merged partitions other than the first will be lost; data on the
first partition will be lost as well if the "force" argument is given.
If "force" is not given, and the first partition has a resizable file system
(e.g. JHFS+), it will be grown in a data-preserving manner, even if a different
file system is specified (in fact, your file system and volume name parameters
are both ignored in this case). If "force" is not given, and the first
partition is not resizable, you will be prompted if you want to erase.
If "force" is given, the first partition is always formatted. You should
do this if you wish to reformat to a new file system type.
Merged partitions are required to be ordered sequentially on disk.
See diskutil list for the actual on-disk ordering; BSD slice identifiers
may in certain circumstances not always be in numerical order but the
top-to-bottom order given by diskutil list is always the on-disk order.
Ownership of the affected disk is required.
Example: diskutil mergePartitions JHFS+ NewName disk3s4 disk3s7
This example will merge all partitions *BETWEEN* disk3s4 and disk3s7,
preserving data on disk3s4 but destroying data on disk3s5, disk3s6,
disk3s7 and any invisible free space partitions between those disks;
disk3s4 will be grown to cover the full space if possible.
B. Download GPT Fdisk from http://sourceforge.net/projects/gptfdisk/ and create a Hybrid MBR.
Rebuild MBR to match the new GPT information thus resetting the Hybrid MBR. Use defaults for other questions (like partition codes). The only values that need modifications are the Boot flags and step 10. Accept all other defaults that Gdisk offers. Please see thesample Q&A as an example. These steps can be repeated if you make a mistake before you get to Step 12, otherwise start from Step 1 for these steps. Step 6 has numbers which are typed with a space between the numbers.
- Sudo gdisk /dev/rdisk0
- P (Print list of parts)
- R (Recover)
- O (print current Hybrid MBR)
- H (chooses Hybrid)
- Partitions numbers to be hybridized: 2 3 4
- Y (Good for GRUB question)
- N (part 2 boot flag)
- N (part 3 boot flag)
- N (part 4 boot flag - designated Windows partition)
- O (print current Hybrid MBR)
- W (Write the new MBR)
- Y (Yes! write the new MBR)
- Reboot
After Reboot use the USB to install Windows (do not choose EFI). Please post back with any error messages.
