Boot Camp not enough space when there is

  • mid 2011 MBA with 128GB drive
  • High Sierra 10.13.4
  • 45GB used 74GB free
  • APFS volume


I am trying to install W7 but BCA reports there is not enough space on my drive. I have tried First Aid and restarted to no avail. The Erase option is blanked out. When trying to add a partition it says there is only 18GB available which is untitled.


What are my next options to try and get BCA to use the free space available?


Many thanks.

MacBook Air (13-inch Mid 2011), macOS High Sierra (10.13.4), null

Posted on Apr 7, 2018 11:34 PM

Reply
114 replies

Apr 29, 2018 6:01 AM in response to fsa259

I have the same issue here, but mine shows even before I get to any partition option. As soon as I hit "Continue" on the first window I get the error message saying I need at least 40GB of free space. I currently have 332GB free on a 500GB drive!


Local snapshots simply cannot explain that in my case, as I barely have any. Apart from a clear install, what else can I try?

May 30, 2018 11:00 PM in response to Daniel500

Hi, I am trying to install boot camp and I get the same error message that you did saying that I need at least 40GB of free space.

I saw that you followed these instructions "Local Snapshots first, and try before we look for other APFS-related issues. You also need contiguous disk space for partitioning." However I have no idea what any of that means.

Could you help me out?


Thanks

Jun 3, 2018 6:20 AM in response to Loner T

this is my output....help plz?

com.apple.TimeMachine.2018-06-02-182923

com.apple.TimeMachine.2018-06-02-192930

com.apple.TimeMachine.2018-06-02-202922

com.apple.TimeMachine.2018-06-02-212953

com.apple.TimeMachine.2018-06-02-222918

com.apple.TimeMachine.2018-06-02-232923

com.apple.TimeMachine.2018-06-03-002919

com.apple.TimeMachine.2018-06-03-013105

com.apple.TimeMachine.2018-06-03-022921

com.apple.TimeMachine.2018-06-03-033055

com.apple.TimeMachine.2018-06-03-043019

com.apple.TimeMachine.2018-06-03-052956

com.apple.TimeMachine.2018-06-03-063306

com.apple.TimeMachine.2018-06-03-072953

com.apple.TimeMachine.2018-06-03-083027

com.apple.TimeMachine.2018-06-03-164633

com.apple.TimeMachine.2018-06-03-174646

Jun 13, 2018 5:28 AM in response to uafridi1179

com.apple.TimeMachine.2018-06-02-182923

com.apple.TimeMachine.2018-06-02-192930

com.apple.TimeMachine.2018-06-02-202922

com.apple.TimeMachine.2018-06-02-212953

com.apple.TimeMachine.2018-06-02-222918

com.apple.TimeMachine.2018-06-02-232923

com.apple.TimeMachine.2018-06-03-002919

com.apple.TimeMachine.2018-06-03-013105

com.apple.TimeMachine.2018-06-03-022921

com.apple.TimeMachine.2018-06-03-033055

com.apple.TimeMachine.2018-06-03-043019

com.apple.TimeMachine.2018-06-03-052956

com.apple.TimeMachine.2018-06-03-063306

com.apple.TimeMachine.2018-06-03-072953

com.apple.TimeMachine.2018-06-03-083027

com.apple.TimeMachine.2018-06-03-164633

com.apple.TimeMachine.--------- 8335578555

Jun 13, 2018 5:33 AM in response to uafridi1179

com.apple.TimeMachine.2018-06-02-192930

com.apple.TimeMachine.2018-06-02-202922

com.apple.TimeMachine.2018-06-02-212953

com.apple.TimeMachine.2018-06-02-222918

com.apple.TimeMachine.2018-06-02-232923

8335578555

com.apple.TimeMachine.2018-06-02-192930

com.apple.TimeMachine.2018-06-02-202922

com.apple.TimeMachine.2018-06-02-212953

com.apple.TimeMachine.2018-06-02-222918

com.apple.TimeMachine.2018-06-02-232923

Jun 18, 2018 6:03 AM in response to Loner T

Good news! I was finally able to partition the disc and install windows 10 successfully.


I was not able to move the dial beyond the 0.648 GB mark shown. When I put in the bigger number there, it would automatically revert itself to 0.648 GB.


Then I deleted the local snapshots again, ran first aid on the disc, and them ran the 'repair disc permissions task' on CleanMyMac 3. Restarted the Mac, and I was able to partition without a problem.


Thanks for your patience and all your help 🙂

Jun 24, 2018 8:22 AM in response to Loner T

** Checking volume.

** Checking the container superblock.

** Checking the EFI jumpstart record.

** Checking the space manager.

** Checking the object map.

** Checking the APFS volume superblock.

** Checking the object map.

dev_init:561: Using /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/fsck_apfs.1907.1/apfs and /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/fsck_apfs.1907.1/nx for device-io.

** Checking the fsroot tree.

** Checking the snapshot metadata tree.

** Checking the extent ref tree.

** Checking the snapshots.

** Checking the APFS volume superblock.

** Checking the object map.

** Checking the fsroot tree.

** Checking the snapshot metadata tree.

** Checking the extent ref tree.

** Checking the snapshots.

** Checking the APFS volume superblock.

** Checking the object map.

** Checking the fsroot tree.

** Checking the snapshot metadata tree.

** Checking the extent ref tree.

** Checking the snapshots.

** Checking the APFS volume superblock.

** Checking the object map.

** Checking the fsroot tree.

** Checking the snapshot metadata tree.

** Checking the extent ref tree.

** Checking the snapshots.

** Verifying allocated space.

** The volume /dev/rdisk1 appears to be OK.

Jul 21, 2018 5:51 AM in response to srna513006

The CCC snapshots should not interfere with the Bootcamp, unless they occupy unreasonable amount of space. The only snapshots you should be deleting should be com.apple.time_machine.* . Deleting the CCC snapshots will just bring them back, so it is unnecessary.


You may want to start a new discussion to avoid confusion, because you may have an APFS issue.

Aug 26, 2018 5:57 AM in response to Loner T

I noticed this thread when searching through a similar issue. I used Boot Camp last summer when I first got my current machine (have been using Macs since the early 90's) and successfully installed Windows 10 via Bootcamp with no issues whatsoever but it got to the point where I was running low on space on the Mac side and hardly ever using Windows so just removed Windows and the windows partition itself and carried on using my mac as normal. The space showed as available on the mac side and all added back up so all was well.


I've been having issues trying to put windows back on with boot camp saying that I don't have enough space even though I have more than enough. I am pretty sure that this is down to having an SSD and the way disk fragmentation works compared to your typical old fashioned spinning hard disk. I have 62GB free but Boot Camp says I can only create 40GB for windows (I can't make it any smaller than that) but it will only leave 4GB for the Mac side so if you do the numbers, that clearly does not add up. I should still have 18GB somewhere ...


You mentioned needing contiguous space to create a partition and I think that this must be the case. I don't use Time machine so don't have any snapshots taking up space and I also have about 1GB of purgeable space if that. All my Get Info's / Disk Utility / About This Mac etc etc all show the exact same space available so I am wanting to know if there's any way to make full use of the space I have left? I understand that the space is in fact there for normal files and that it must be the partitioning side of things but I have found APFS very flexible in that regard so far so I am disappointed with the issue I am having at present.


My next move is just a full format / zero all data / reinstall High Sierra from scratch from my pen drive, reinstall my Mac side and get it exactly how I want it, then go and do the Boot Camp thing and all will be well. It's just I'd rather not have to do that as my machine is running like a dream and I'm not (in theory!) running out of space.


Any suggestions welcome.


Regards

Dougie

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Boot Camp not enough space when there is

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.