You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Andrew_S_N Author

Level 1

8 points

Not enough space on disk to Partition: Windows Bootcamp

iMac (Retina 4K, 21.5-inch, Late 2015)

Processor: 3.1 GHz Intel Core i5

Memory: 6 GB 1867 MHz DDR3

Graphics: Intel Iris Pro Graphics 6200 1536 MB

OSX Version: 10.11.4

I've tried to download windows for my iMac. I've bought the full version via USB for it. I've followed these instructions: Create an ISO image for Boot Camp from Windows installation media - Apple Support to create my own ISO image. I've done that, and I've ejected the "WINDOWS10" disk image like it told me too.

When I go to download the support software and partition the disk, it will get past the Windows Support Software download, then about halfway into Partitioning the disk, it will say "The disk does not have enough space to be partitioned". (P.S) The image "BOOTCAMP" will show on the desktop before it says the message, and then will go away and the message will occur.

I've repaired the disk and defragged it. I've put 300 gigs for the Partition, that's plenty. I'm not sure what's going on.

I've also went into Disk Recovery and repaired it that way.

I'm on the forums before I decide to call Apple.

Thank you.

iMac, OS X El Capitan (10.11.4)

Posted on Apr 1, 2016 9:04 PM

22 replies

Andrew_S_N Author

Level 1

8 points

Apr 2, 2016 2:48 PM in response to Andrew_S_N

Dis-regard. I am now installing Windows Support Software, and partitioning the disk.

If this does not work, I will try to boot into Safe Mode and Internet Recovery.

Is there any other tips you have if this doesn't work?

Because if not, I will be contacting Apple.

Andrew_S_N Author

Level 1

8 points

Apr 2, 2016 3:02 PM in response to Loner T

The file is "Win10_1511_1_English_x64.iso"

Terminal Codes:

openssl md5 ~/Documents/Windows10Download.iso

openssl md5 ~/Documents/Win10_1511_1_English_x64.iso

MD5(/Users/(MYNAME)/Documents/Windows10Download.iso)= ddb6ec00e39829e3145057ada5d6919c

(MYNAME)-iMac:~ (MYNAME)$ openssl md5 ~/Documents/Win10_1511_1_English_x64.iso

MD5(/Users/(MYNAME)/Documents/Win10_1511_1_English_x64.iso)= a4fde74732557d75ffc5354d0271832e

(MYNAME)-iMac:~ (MYNAME)$

Loner T

Level 9

59,513 points

Apr 2, 2016 3:17 PM in response to Andrew_S_N

Your Win10_1511_1_English_x64.iso MD5sum matches what I have, so it is the correct file.

$ ls -lgh Win10_1511_1_English_x64.iso

-rw-r--r--@ 1 staff 4.1G Feb 21 13:51 Win10_1511_1_English_x64.iso

$ openssl md5 Win10_1511_1_English_x64.iso

MD5(Win10_1511_1_English_x64.iso)= a4fde74732557d75ffc5354d0271832e

What is the error you get when you use this file? Do not use the other file.

Andrew_S_N Author

Level 1

8 points

Apr 2, 2016 3:31 PM in response to Loner T

I believe I've reached victory.

I can install windows now, but I have a question.

Is the Partition I created named "BOOTCAMP" that I shall use for Windows, does that need to be NTSF Format? And can I format that in the Windows Installation process?

Loner T

Level 9

59,513 points

Apr 2, 2016 3:35 PM in response to Andrew_S_N

Yes, to both.

Andrew_S_N Author

Level 1

8 points

Apr 2, 2016 6:52 PM in response to Loner T

Thank you so much for helping me.

I've reached victory!!!

But, I know you have seen this new situation I've occurred.

The Intel Driver Update that crashes the system. -.-

Yeah, I use the Microsoft "Hide-Show Update" app to suspend it until it's fixed.

I also put my wifi on metered so I have to manually update things one by one.

I posted on Intel Support Communities to see if any answers come up.

Thank you again.

Andrew

Loner T

Level 9

59,513 points

Apr 2, 2016 7:15 PM in response to Andrew_S_N

I will exonerate Intel from this mess, but neither Apple nor Microsoft can wash their hands of this catastrophe.

1. Apple has created a variant of a GPU that they should have also modified the PID/VID and other identifiers of, to make it unique.

2. Microsoft is the other guilty party in overwriting a fully functional driver and forcing an update requiring users to go through contortions to stop them from crashing the machine. The worst part is that such crash reports are not being fed back to Microsoft, to make them stop, something which Apple does very well with crash reports. The W10 OS is not learning from such crashes either and cannot recover gracefully because the updates should create a System Restore point and recover to it, like many users have done manually.

Not enough space on disk to Partition: Windows Bootcamp