Boot Camp not enough space when there is

355preetis wrote:

chk this

com.apple.TimeMachine.---------8889904199

This looks like a corrupted entry. Can you try to install Windows, before we diagnose the issue with this specific entry?

masterthamara wrote:

On this screen can you either move the disk space 'dial' or type in a value in the Size box?

Run (please verify the output of diskutil list before using disk0s5 in the following command)

diskutil eraseVolume jhfs+ BC1 disk0s5

diskutil resizeVolume disk0s5 limits

If you delete the partition, and get all your disk space back into macOS, we can then retry to use BCA to try and partition the disk via BCA.

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

Can you start a new discussion, and post the year/model of your Mac (do not post the serial number), and the output of diskutil list on the new discussion?

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?

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

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

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

Hi Loner T,

Thanks for all your instructions. I've deleted all my local snapshots, but I still get the message saying I don't have 40 GB of free space. What else can I do to free up 40GB of contiguous space?

Thanks!

Ran First Aid. Still getting the same message.

Disk utility won't let me add a sizable new partition to the disk. When I click the '+' button, the maximum space it allows me to set for the new partition is 649 MB.

How can I add a partition in this case? (I'm on macOS High Sierra 10.13.5, is that helps.)

Please help me! I had the same issue.

I followed @Loner T:

but it still not work : (

After that I did try: "Run Disk Utility and create a FAT partition of the size you want Windows to be. Post any failures or corresponding screen shots." and the result:

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

I hope that my English is reasonably understandable, I am a Dutchman.

I am experiencing the same problem and I have implemented the instructions as mentioned in this topic.

It just does not work.

I see in the terminal that the first Local Snapshot has been removed, but when I request the overview again, the deleted record is still in the list, see Appendix 1.

Am I doing something wrong.

I use Carbon Copy Cleaner and it looks like it has created the Local Snapshots.

I see on my Harddisk that a "Other Volume" of 1.75 Gb is positioned behind the data partition, see appendix 2.

I have never seen this Volume before.

Your advice is what to do.