Boot Camp not enough space when there is

** 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.

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.

srna513006 wrote:

Thank you for the response and explanation.

I have reset the SSD drive to factory status and do not use Windows on the MB anymore.

Problem solved...😉

Yes, that is one way to address the issue. 😉

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

Zeroing a SSD is not recommended, unless you plan a secure erase to sell the SSD. APFS snapshots are the first place to look. If there are none, then a TM backup/restore 'defragments' the drive. APFS in High Sierra is the 1.0 release with many bugs and the inability to correct some overallocation issues. Mojave may be better. BC Assistant also has bugs, which compounds the issues.

Hi

Thanks for the reply.

I forgot to mention I don't run time machine at all and have never had it switched on. I did run a command to erase any time machine snapshots but none were found.

Would boot camp let me install windows 10 if I already did the manual labour with regards to disk partitioning etc myself beforehand? Only trouble is Disk Utility doesn't let you format as NTFS.

As I've had it installed before, when I hold Alt/Option on startup the option to boot into Windows is still there even though technically there's no Windows partition any more. I guess I'd have to make a bootable Windows usb pen drive and install from that but would need the Bootcamp Mac/Windows drivers too. Don't know if I could download those separately either.

2015 and later models support EFI Boot, and the Macs do not support USB Installation properly. A manually-created partition does not always work. On 2014 and older Macs, it does work. The NTFS formatting is done in the Windows installer, not via Disk Utility. Using third-party tools leads to new issues.

Hello Kostas

I’m not sure if you’re referring to me and my post or someone else’s but if it is in relation to my issue, then I have since found out what was wrong.

As I have an SSD I have to have 40GB of contiguous space available and not just 40GB of free space on my volume (which would have been fine had I been using a traditional old fashioned spinning hard drive).

I think the only way I’ll be able to get it to work is by starting over and doing a full disk format and restore, installing Mac OS from scratch and getting everything how I want it on the Mac side and then go into Boot Camp and creating my partition then and installing Windows 10 at that point while the contiguous space is available.

Hope that’s of some help.

Dougie

ManuCostaRica wrote:

I was having this exact same issue. I run "CleanMyMac" and boom, issue solved.

CleanMyMac is a dangerous tool on Macs and can cause problems. It does not correctly remove files and can leave macOS un-bootable.

Hello, I have this issue also. It says I need at least 40GB and I have 140GB available. I have run sudo tmutil listlocalsnapshots / but I just get the prompt again so I assume I have no snapshots.

I have run Disk Utility First Aid and everything is okay. Still can't get past the 40GB warning. What is the next step? Thanks. -Derryl

I am trying to install Win 10 on a Mac Pro OSX 13.6 with a 500GB SSD.

Hello. I'm having the same trouble. I tried the remove localsnapshot solution, and now the list is empty, but still says I need at least 40GB. Finder says I have 68GB and disk Utility says 51GB. I have iCloud and I unchecked optimize Mac storage in iCloud Drive. It's checked in Photos as I have about 98 GB used in iCloud and don't have that space in my SSD. I'm using a 2011 iMac with High Sierra 10.13.6.

When running

sudo tmutil listlocalsnapshots /

I'm prompted once to enter my password but no other responses are given once my password is entered.

After I run again:

sudo tmutil listlocalsnapshots /

no responses are given.

I'm so lost, please help

ur also gonna have problem with new mac file system, with the windows 10 iso with a file install.wim which shows larger than 4gb and can't copy by bootcamp on ur mac if its running mojave.

Mojave 10.14.2 is supposed to address the issue. You can also use W10 1803 (April) and then in-place upgrade Windows.

i did it, installed the latest version, by using my friend's windows laptop to make the bootable usb and and then used it with bootcamp. no issues faced with drivers etc but only problem is i can't use the option "startup disk" in either OS, it can't detect one another. i have to manually press and hold alt to select the OS i want to run, everytime, otherwise it restarts to macos automatically. thats the only solution for now.

I have tried almost everything to solve this problem and I realized that the bootcamp assistant gives me a wrong error. It shows me that there is not enough space on my disk, but I have 200GB. I choose a 128GB pendrive and then start transferring windows files. After 5-10 minutes it shows the "not enough space" dialog and when I open the pendrive I find that it always stop at the same large file. I know that with FAT32 you cannot move large files but the bootcamp always format the usb storage to FAT32. This is the error in this scenario. I format the pendrive to exFAT copy the windows files and install it manually not selecting all the options. Hope this helps