Darrell Stall
Level 1 (22 points)
Mac OS X

Q: Can I install Windows 10 from Bootcamp Asst USB created drive?

I got the following message when opening Boot Camp -

"The startup disk cannot be partitioned or restored to a single partition.

The startup disk must be formatted as a single Mac OS Extended (Journaled) volume or already partitioned by Boot Camp Asst for installing Windows."

My startup disk is formatted as a Mac OS Extended (Journaled) volume, so I clicked OK, but then the 3rd box on the Select Tasks screen was greyed out so I couldn't check "Install or remove Windows 7 or later version, so I left the 1st two boxes checked and ran BCA to "Create a Windows 7 or later version install disk", and "Download the latest Windows support software from Apple", after which I only had option to quit, not install a partition or anything else.

Now, when I boot to startup manager, it shows my OSX HD, the EFI boot drive and a Windows drive.

When I select it, message says "Booting from Boot Camp Asst USB created drive . . ."

What happens when I let that drive run installation of Windows 10?

Is it going to create a Windows partition?
If not where is it going to install Windows? over my OSX 10.11 startup disk?!!! or what?

Note: The USB created drive was created from the Windows 10 iso that I downloaded as Windows developer which can be used without an installation key.

I used it with Parallels Desktop without any problem.

Mac mini (Late 2012), OS X El Capitan (10.11.2), 2.3GHz, 16GB RAM

Posted on Jul 24, 2016 3:36 PM

by Loner T,Solvedanswer
Loner T Loner T
Level 7 (23,828 points)
Safari
A:

1. Please back up OSX first.

 

2. Merge partitions.

     diskutil mergePartitions jhfs+ "MAC_MINI" disk0s2 disk0s4

 

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.

This will merge disk0s3 and disk0s4 into disk0s2, leaving the main OSX partition.

 

 

3. Re-install OSX to get Recovery HD back. Be aware, Internet Recovery may provide the shipping version of OSX, not your current version. Please see About OS X Recovery - Apple Support for reference.

 

4. If you prefer to do this without touching your internal disk, then How to install OS X on an external drive connected to your Mac - Apple Support, upgrade the external disk OSX version to match your internal disk's OSX version. Boot from this external disk and re-install OSX on the internal disk after step 2. This will give you Recovery HD which matches El Capitan. Re-installing OSX does not manipulate any non-OSX files, but a backup is strongly recommended to work around "crApple Engineering" failures.

Posted on Jul 25, 2016 8:00 AM

Close
Darrell Stall

Q: Can I install Windows 10 from Bootcamp Asst USB created drive?

  • All replies
  • Helpful answers

Page 1 of 3 last Next

  • by Loner T,

    Loner T Loner T Jul 24, 2016 6:59 PM in response to Darrell Stall
    Level 7 (23,828 points)
    Safari
    Jul 24, 2016 6:59 PM in response to Darrell Stall

    Re-run BCA and check if you can click on only the Install Option. If it is greyed out, from OS X Terminal, please post the output of

     

    diskutil list

    diskutil cs list

  • by Darrell Stall,

    Darrell Stall Darrell Stall Jul 24, 2016 7:36 PM in response to Loner T
    Level 1 (22 points)
    Mac OS X
    Jul 24, 2016 7:36 PM in response to Loner T

    Install Option is greyed out whether either or both of 1st two options are checked or not.

     

    Mac-mini:~ darrellstall$ diskutil list

    /dev/disk0 (internal, physical):

      #:                      TYPE NAME                    SIZE      IDENTIFIER

      0:      GUID_partition_scheme                        *1.0 TB    disk0

      1:                        EFI EFI                    209.7 MB  disk0s1

      2:                  Apple_HFS MAC_MINI                998.7 GB  disk0s2

      3:                Apple_Boot Recovery HD            650.0 MB  disk0s3

      4:                Apple_Boot Recovery HD            650.0 MB  disk0s4

    /dev/disk1 (disk image):

      #:                      TYPE NAME                    SIZE      IDENTIFIER

      0:                            J_CSLA_X64FREO_EN-U... +4.4 GB    disk1

     

    J_CSLA_X64FREO_EN-U... is the Windows 10 USB drive

    There are two Recovery HD because there's an old Mac OSX 10.8.5 one in addition to an El Capitan one.

    (Don't know why that happened but will address deletion of it in another thread)

    Mac-mini:~ darrellstall$ diskutil cs list

    No CoreStorage logical volume groups found

    Mac-mini:~ darrellstall$

  • by Loner T,

    Loner T Loner T Jul 24, 2016 8:02 PM in response to Darrell Stall
    Level 7 (23,828 points)
    Safari
    Jul 24, 2016 8:02 PM in response to Darrell Stall

    My recommendation is to use a Time Machine backup/erase your internal disk/restore from TM backup.

  • by Darrell Stall,

    Darrell Stall Darrell Stall Jul 25, 2016 6:47 AM in response to Darrell Stall
    Level 1 (22 points)
    Mac OS X
    Jul 25, 2016 6:47 AM in response to Darrell Stall

    After rebooting, the Windows USB drive no longer exists when running diskutil list.

    I erased both recovery HD partitions and they now show as Blank in Disk Utility,

    but I cannot resize the main drive partition in order to merge them.

     

    Now, when I open BCA I get message "Boot Camp Assistant cannot be used."

    "The disk is not journaled. You must enable journaling using Disk Utility before using the Boot Camp Assistant."

    The drive is listed in diskutil as "Apple_HFS MAC_MINI  998.7 GB   disk0s2"

    When I select the HD (not just partition) in Disk Utility, the File>Enable Journaling selection is greyed out, indicating the drive already has journaling enabled. I always format drives with journaling enabled.

  • by Darrell Stall,

    Darrell Stall Darrell Stall Jul 25, 2016 6:54 AM in response to Darrell Stall
    Level 1 (22 points)
    Mac OS X
    Jul 25, 2016 6:54 AM in response to Darrell Stall

    See El CRapitan - Disk Utility will NOT resize partition in El Capitan

  • by Darrell Stall,

    Darrell Stall Darrell Stall Jul 25, 2016 6:56 AM in response to Darrell Stall
    Level 1 (22 points)
    Mac OS X
    Jul 25, 2016 6:56 AM in response to Darrell Stall

    Mac-mini:~ darrellstall$ diskutil enableJournal /Volumes/MAC_MINI

    Journaling was already enabled for volume MAC_MINI on disk0s2

    Mac-mini:~ darrellstall$

  • by Loner T,

    Loner T Loner T Jul 25, 2016 6:58 AM in response to Darrell Stall
    Level 7 (23,828 points)
    Safari
    Jul 25, 2016 6:58 AM in response to Darrell Stall

    Please post the output of the following OSX Terminal command.

     

    sudo gpt -vv -r show /dev/disk0

     

    DU will not move partitions, if there are intervening partitions.

     

    Using an older OSX version's DU has other risks with possible version conflicts on file systems.

  • by Darrell Stall,

    Darrell Stall Darrell Stall Jul 25, 2016 7:00 AM in response to Darrell Stall
    Level 1 (22 points)
    Mac OS X
    Jul 25, 2016 7:00 AM in response to Darrell Stall

    More crAPPLE nonsense - Boot Camp Problems. The disk is not journaled.

  • by Loner T,

    Loner T Loner T Jul 25, 2016 7:10 AM in response to Darrell Stall
    Level 7 (23,828 points)
    Safari
    Jul 25, 2016 7:10 AM in response to Darrell Stall

    Darrell Stall wrote:

     

    More crAPPLE nonsense - Boot Camp Problems. The disk is not journaled.

    OP had two Recovery HDs, which is an obvious problem, that you are ignoring.

     

    Blaming Apple is not very helpful for environmental issues.

  • by Darrell Stall,

    Darrell Stall Darrell Stall Jul 25, 2016 7:13 AM in response to Loner T
    Level 1 (22 points)
    Mac OS X
    Jul 25, 2016 7:13 AM in response to Loner T

    gpt show: /dev/disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168

    gpt show: /dev/disk0: PMBR at sector 0

    gpt show: /dev/disk0: Pri GPT at sector 1

    gpt show: /dev/disk0: Sec GPT at sector 1953525167

           start        size  index  contents

               0           1         PMBR

               1           1         Pri GPT header

               2          32         Pri GPT table

              34           6        

              40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

          409640  1950576416      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

      1950986056     1269536      3  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

      1952255592     1269536      4  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

      1953525128           7        

      1953525135          32         Sec GPT table

      1953525167           1         Sec GPT header

  • by Darrell Stall,

    Darrell Stall Darrell Stall Jul 25, 2016 7:15 AM in response to Loner T
    Level 1 (22 points)
    Mac OS X
    Jul 25, 2016 7:15 AM in response to Loner T

    I upgraded from Mountain Lion to El CRapitan.

    I did nothing to retain the old Mountain Lion Recovery HD.

    - crAPPLE did that with its "engineering"!

  • by Loner T,

    Loner T Loner T Jul 25, 2016 7:30 AM in response to Darrell Stall
    Level 7 (23,828 points)
    Safari
    Jul 25, 2016 7:30 AM in response to Darrell Stall

    The Upgrade failed in your case. Use Time Machine to backup OSX, erase your internal disk and restore from TM. You can also use diskutil mergePartitions to clean this up and re-install/upgrade OSX via Internet Recovery. A back up before the mergePartitions is strongly recommended.

  • by Darrell Stall,

    Darrell Stall Darrell Stall Jul 25, 2016 7:48 AM in response to Loner T
    Level 1 (22 points)
    Mac OS X
    Jul 25, 2016 7:48 AM in response to Loner T

    Do the results of the terminal commands you had me run and post results indicate that?
    What do they indicate?

    What you're suggesting is a drastic move.

    I'll probably just use Parallel Desktop,

    write off Boot Camp along with File Vault and god knows what all else -

    My first Mac was an SE, so I'm all too familiar with Apple's "engineering" failures.

    I can't prove it, but after thinking about it I'm sure I wiped HD clean and started with a clean install of El CRapitan so as not to have any problems.

    Either way it's failed crAPPLE "engineering" - failure to delete old Recovery HD at upgrade, or failure to delete old Recovery HD at disk erase.

    But the problem with crAPPLE "engineering" in this case seems to be that Boot Camp Assistant does NOT WORK with ANY other additional drive partitions other than the boot drive partition.

    I've tried using Terminal command diskutil mergePartitions and it doesn't work.

    If I'm citing drive names incorrectly, then please correct.

     

    diskutil mergePartitions HFS+ Apple_HFS MAC_MINI  disk0s2 disk0s3 disk0s4

     

    0:      GUID_partition_scheme                        *1.0 TB     disk0

       1:                        EFI EFI                     209.7 MB   disk0s1

       2:                  Apple_HFS MAC_MINI                998.7 GB   disk0s2

       3:                 Blank                                             650.0 MB   disk0s3                             

       4:                 Blank                                             650.0 MB   disk0s4

  • by Loner T,Solvedanswer

    Loner T Loner T Jul 25, 2016 8:00 AM in response to Darrell Stall
    Level 7 (23,828 points)
    Safari
    Jul 25, 2016 8:00 AM in response to Darrell Stall

    1. Please back up OSX first.

     

    2. Merge partitions.

         diskutil mergePartitions jhfs+ "MAC_MINI" disk0s2 disk0s4

     

    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.

    This will merge disk0s3 and disk0s4 into disk0s2, leaving the main OSX partition.

     

     

    3. Re-install OSX to get Recovery HD back. Be aware, Internet Recovery may provide the shipping version of OSX, not your current version. Please see About OS X Recovery - Apple Support for reference.

     

    4. If you prefer to do this without touching your internal disk, then How to install OS X on an external drive connected to your Mac - Apple Support, upgrade the external disk OSX version to match your internal disk's OSX version. Boot from this external disk and re-install OSX on the internal disk after step 2. This will give you Recovery HD which matches El Capitan. Re-installing OSX does not manipulate any non-OSX files, but a backup is strongly recommended to work around "crApple Engineering" failures.

Page 1 of 3 last Next