Boot Camp not enough space when there is

sudo tmutil deletelocalsnapshots 2018-06-02-182923

and repeat for each of the remaining entries.

Post the output of

sudo tmutil listlocalsnapshots /

See the last line of the last paragraph in About Time Machine local snapshots - Apple Support as a reference.

That's why Finder and Get Info windows don't include local snapshots in their calculations of the storage space available on a disk.

Run

sudo tmutil deletelocalsnapshots 2018-06-02-182923

and repeat for each entries.

355preetis wrote:

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

Also, is this a cut/paste error? 😕

daniel6876 wrote:

it says in terminal

com.apple.TimeMachine.2018-06-14-185120

com.apple.TimeMachine.2018-06-14-192927

Run

sudo tmutil deletelocalsnapshots 2018-06-14-185120

sudo tmutil deletelocalsnapshots 2018-06-14-192927

and retry.

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 🙂

Run

diskutil eraseVolume fat32 BOOTCAMP disk0s3

and run BC Assistant and click on Remove/Restore. Once it is restore back to a single macOS partition, re-run BCA and try to install Windows. The APFS implementation on High Sierra has many bugs.

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

Post the output of

sudo tmutil listlocalsnapshots /

This will help verify if that is really your issue or something else.

Run

sudo fsck_apfs -n -l /dev/rdisk1

and post the output.

Use this UNIX command pipeline in Terminal:

$ tmutil listlocalsnapshotdates | sed -e '1d' | xargs -L 1
tmutil deletelocalsnapshots

Works nicely for me!

—tonza

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.

Can you post the output of

sudo gpt -vv -r show /dev/disk0

If you get permission errors, see SIP - Enable and Disable steps .

From Terminal, post the output of

sudo tmutil listlocalsnapshots /

Did you run First Aid on the whole disk after the snapshots were deleted?

Can you post the output of

sudo tmutil listlocalsnapshots /