Boot Camp Assistant problems

Question

Level 1

0 points

Boot Camp Assistant problems

I am trying to install Windows 10 on my 2015 MacBook Pro 13.3" running Mac OS X El Capitan (10.11.2) but I am unsuccessful (for software that is not supported by Mac OS X). I have tried several times but it always says that my disk space is not enough (cannot remember the exact words in the error message). I then opened the Boot Camp Assistant through the terminal and saw that it only recognizes that the drive would have 4GB of free space available (I have a 500 GB SSD and 130 GB is used) but some insane amount of about 140000000000000 GB was used (what?). When I check in the Disk Utility I also get some suspicions that Boot Camp Assistant selects the Macintosh HD partition, instead the the actual drive. In the Boot Camp Assistant I can choose the size of the partition (I want to leave 370 GB for OS X in the Macintosh HD partition and get 128 GB for the Boot Camp / Windows 10 partition). I can't get this to work and I am grateful for any help!

MacBook Pro with Retina display, OS X El Capitan (10.11.2)

Posted on Jan 1, 2016 1:24 PM

Reply

Answer 1

Loner T

Level 9

59,471 points

Jan 1, 2016 3:48 PM in response to Nikarishi

Windows Installer can generate spurious messages about insufficient disk space. Do you have any external storage connected when you try to install Windows?

If the problem persists, please run the following two procedures and retry.

Resetting the System Management Controller (SMC) on your Mac - Apple Support

How to Reset NVRAM on your Mac - Apple Support

Reply

Answer 2

Nikarishi Author

Level 1

0 points

Jan 1, 2016 7:39 PM in response to Loner T

I did not have any external storage "plugged in", no USB, external HDD or anything. Then I remembered that I have an Airport Extreme that I use for Time Machine. I disconnected that both in Finder and in Disk Utility; that didn't fix my problem.

Then I reset the SMC and NVRAM and it still gives the same error message. I'll attach an image. (In Swedish, but it says that the installation failed because there is not enough space on the disk.)

Reply

Answer 3

Loner T

Level 9

59,471 points

Jan 1, 2016 7:57 PM in response to Nikarishi

Your disk may need repairs. Let us try the simpler steps first.

1. Please boot in Safe Mode - Try safe mode if your Mac doesn't finish starting up - Apple Support - then both normally and re-try the installation.

2. Boot into Internet Recovery - OS X: About OS X Recovery - Apple Support - and click on Utilities -> Terminal and run diskutil repairDisk disk0 (and post the output) then boot normally, run SMC/NVRAM Reset. Now re-try BCA.

Reply

Answer 4

Nikarishi Author

Level 1

0 points

Jan 3, 2016 2:24 PM in response to Loner T

This did not solve my problem either.

I've been googling around and it seems that FileVault should be off when wanting to install Boot Camp. I've turned it off, so it has unencrypted the disk. But could it be so that the disk is too fragmented? Because I have an SSD I don't want to defrag it but I suspect that might be the problem. Is there any solution to this?

Reply

Answer 5

Loner T

Level 9

59,471 points

Jan 3, 2016 3:55 PM in response to Nikarishi

Before we go further, can you post the log from step 2?

Reply

Answer 6

Nikarishi Author

Level 1

0 points

Jan 3, 2016 4:17 PM in response to Loner T

-bash-3.2# diskutil repairDisk disk0

Repairing the partition map might erase disk0s1, proceed? (y/N) y

Started partition map repair on disk0

Checking prerequisites

Checking the partition list

Adjusting partition map to fit whole disk as required

Checking for an EFI system partition

Checking the EFI system partition's size

Checking the EFI system partition's file system

Checking the EFI system partition's folder content

Checking all HFS data partition loader spaces

Checking booter partitions

Checking booter partition disk0s3

Repairing file system

Checking Journaled HFS Plus volume

Checking extents overflow file

Checking catalog file

Checking multi-linked files

Checking catalog hierarchy

Checking extended attributes file

Checking volume bitmap

Checking volume information

Trimming unused blocks

The volume Recovery HD appears to be OK

File system check exit code is 0

Updating boot support partitions for the volume as required

Reviewing boot support loaders

Checking Core Storage Physical Volume partitions

Updating Windows boot.ini files as required

The partition map appears to be OK

Finished partition map repair on disk0

-bash-3.2#

Reply

Answer 7

Nikarishi Author

Level 1

0 points

Jan 3, 2016 4:19 PM in response to Nikarishi

Sorry, no line breaks. I'll try again (it shows line breaks in the editor).

-bash-3.2# diskutil repairDisk disk0

Repairing the partition map might erase disk0s1, proceed? (y/N) y

Started partition map repair on disk0

Checking prerequisites

Checking the partition list

Adjusting partition map to fit whole disk as required

Checking for an EFI system partition

Checking the EFI system partition's size

Checking the EFI system partition's file system

Checking the EFI system partition's folder content

Checking all HFS data partition loader spaces

Checking booter partitions

Checking booter partition disk0s3

Repairing file system

Checking Journaled HFS Plus volume

Checking extents overflow file

Checking catalog file

Checking multi-linked files

Checking catalog hierarchy

Checking extended attributes file

Checking volume bitmap

Checking volume information

Trimming unused blocks

The volume Recovery HD appears to be OK

File system check exit code is 0

Updating boot support partitions for the volume as required

Reviewing boot support loaders

Checking Core Storage Physical Volume partitions

Updating Windows boot.ini files as required

The partition map appears to be OK

Finished partition map repair on disk0

-bash-3.2#

Reply

Answer 8

Loner T

Level 9

59,471 points

Jan 3, 2016 4:33 PM in response to Nikarishi

Please try BC Assistant and post any error messages. FileVault2 is not related to your issue.

Reply

Answer 9

Nikarishi Author

Level 1

0 points

Jan 4, 2016 3:13 AM in response to Loner T

The only error message i got from BCA is the picture above. From the terminal I got the following (from startup to fail).

Last login: Mon Jan 4 12:01:33 on console

******-MacBook-Pro-2:~ ******$ /Applications/Utilities/Boot\ Camp\ Assistant.app/Contents/MacOS/Boot\ Camp\ Assistant ; exit;

2016-01-04 12:02:22.835 Boot Camp Assistant[508:6017] Failed to connect (optionContinue) outlet from (DAWindowController) to (NSButton): missing setter or instance variable

2016-01-04 12:02:22.836 Boot Camp Assistant[508:6017] Failed to connect (quitItem) outlet from (DAWindowController) to (NSMenuItem): missing setter or instance variable

2016-01-04 12:02:25.202 Boot Camp Assistant[508:6017] Selected disk's capacity: 4 GB, used space: 140734627716840 GB

2016-01-04 12:02:25.273 Boot Camp Assistant[508:6017] Selected disk's capacity: 4 GB, used space: 140734627716840 GB

2016-01-04 12:03:53.558 Boot Camp Assistant[508:6017] -[DAWindowController softwareUpdateDidBegin:]

2016-01-04 12:09:39.789 Boot Camp Assistant[508:6017] armWindowsInstallerPartitionRemoverOnBootCampWholeDisk returned 0

Reply

Answer 10

Loner T

Level 9

59,471 points

Jan 4, 2016 5:24 AM in response to Nikarishi

Can you post the output of the following Terminal commands?

diskutil list

diskutil cs list

sudo gpt -vv -r show /dev/disk0

sudo fdisk /dev/disk0

The "sudo" commands require your password, which will not be echoed back to you. It may also warn you about improper use of "sudo".

Reply

Answer 11

Nikarishi Author

Level 1

0 points

Jan 4, 2016 6:36 AM in response to Loner T

Last login: Mon Jan 4 12:02:22 on ttys000

******-MacBook-Pro-2:~ ******$ diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.3 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 499.4 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

/dev/disk3 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: WINDOWS10 +15.7 GB disk3 (this is the Windows 10 iso)

******-MacBook-Pro-2:~ ******$ diskutil cs list

No CoreStorage logical volume groups found

******-MacBook-Pro-2:~ ******$ sudo gpt -vv -r show /dev/disk0

Password:

gpt show: /dev/disk0: mediasize=500277790720; sectorsize=512; blocks=977105060

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 977105059

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 975425848 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

975835488 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

977105024 3

977105027 32 Sec GPT table

977105059 1 Sec GPT header

******-MacBook-Pro-2:~ ******$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 60821/255/63 [977105060 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

------------------------------------------------------------------------

1: EE 1023 254 63 - 1023 254 63 [ 1 - 977105059] <Unknown ID>

2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

******-MacBook-Pro-2:~ ******$

Reply

Answer 12

Loner T

Level 9

59,471 points

Jan 4, 2016 8:04 AM in response to Nikarishi

1. Is the WINDOWS10 a USB containing the W10 Installation files, or a single .ISO file?

2. Please copy the single .ISO to your Documents folder and disconnect the external disk. Do not mount the ISO. If you do not have a single-file ISO, you can download one from https://www.microsoft.com/en-us/software-download/home . The following MD5 is for the specific named file.

openssl md5 Win10_1511_English_x64.iso

MD5(Win10_1511_English_x64.iso)= a0d4271b7537732a060909fd39d54829

3. Run SMC/NVRAM Reset.

4. Run BCA and point to the ISO on the Documents folder when prompted.

5. Try to Install Windows, and post any error messages.

Reply

Answer 13

Nikarishi Author

Level 1

0 points

Jan 4, 2016 8:15 AM in response to Loner T

1. Single ISO made from Windows 10 USB from Microsoft

2. The .ISO is in the Documents folder. No external disk connected. (I have tried BCA with mounted and unmounted ISO, from Disk manager GUI and diskutil in Terminal)

3-5. This is the conditions I had in your first reply. So I have tried this and I got the same error message then as the ones I have posted.

Reply

Answer 14

Nikarishi Author

Level 1

0 points

Jan 4, 2016 8:36 AM in response to Loner T

I tried this now again (80GB partition with 310GB available on 500GB disk) and no difference. (I confirm the SMC/NVRAM Reset for the difference in the startup).

The only error message I get is the picture I posted, and it comes up about 1-2 seconds after it starts copying the Windows files.

Reply

Answer 15

Loner T

Level 9

59,471 points

Jan 4, 2016 11:19 AM in response to Nikarishi

Can you try with the directly downloaded ISO from Microsoft? I suspect the ISO from USB may be corrupt. Can you also post the MD5sum of the ISO that you currently have?

Reply