Can't create Boot Camp partition on brand new 15-inch MBP w/ High Sierra (10.13.5) and APFS. Is there any official fix?

/dev/disk0 (internal):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme 1.0 TB disk0

1: EFI EFI 314.6 MB
disk0s1

2: Apple_APFS Container disk1 1.0 TB disk0s2

3: Apple_Boot Boot OS X 134.2 MB
disk0s3

/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +1.0 TB disk1

Physical Store disk0s2

1: APFS Volume Macintosh HD 287.3 GB
disk1s1

2: APFS Volume Preboot 22.6 MB disk1s2

3: APFS Volume Recovery 518.1 MB
disk1s3

4: APFS Volume VM 1.1 GB disk1s4

My MBP is a 2017 15-inch model. Picked up from the Apple Store this week.

MacOS is High Sierra 10.13.5

I don't know what bootcamp.xml is (it's not on the aborted BOOTCAMP volume). But the product version of Boot Camp Assistant is: Version 6.1.0 (6067.60.1)

Things seem to be OK:

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

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

FWIW, I've disabled FileVault (and waited for it to fully decrypt) and still got the same partition error.

I've also been able to independently create a FAT partition using Disk Utility and then install Windows 10 using a USB boot drive, i.e. the method that the old version of BCA allowed. However, none of the laptop's input devices work (including the keyboard, trackpad, and wifi). And I also get an error message saying to the effect that this version of Windows is not compatible with this version of Boot Camp, or vice versa.

Also, `diskutil repairDisk disk0` finds no problems:

$diskutil repairDisk disk0

Repairing the partition map might erase disk0s1, proceed? (y/N) y

Started partition map repair on disk0

Checking prerequisites

Checking the partition list

Adjusting partition map to fit whole disk as required

Checking for an EFI system partition

Checking the EFI system partition's size

Checking the EFI system partition's file system

Checking the EFI system partition's folder content

Checking all HFS data partition loader spaces

Checking booter partitions

Checking booter partition disk0s3

Verifying file system

Volume is already unmounted

Performing fsck_hfs -fn -x /dev/rdisk0s3

Checking Journaled HFS Plus volume

Checking extents overflow file

Checking catalog file

Checking multi-linked files

Checking catalog hierarchy

Checking extended attributes file

Checking volume bitmap

Checking volume information

The volume Boot OS X appears to be OK

File system check exit code is 0

Restoring the original state found as unmounted

Reviewing boot support loaders

Checking Core Storage Physical Volume partitions

The partition map appears to be OK

Finished partition map repair on disk0

Just wanted to say that your answer solved my problem! This was also after I re-encrypted my drive with FileVault (because I had more or less given up).

This is what happened when I ran your suggested command of

diskutil eraseVolume fat32 BOOTCAMP disk0s3

I got the following output and apparent error message:

Started erase on disk0s3 Boot OS X

Unmounting disk

Erasing

newfs_msdos: 32416 clusters too few clusters for FAT32, need 65525

4096 bytes per physical sector

Mounting disk

Could not mount disk0s4 after erase

Error: -69832: File system formatter failed

However, I continued with your instructions to run BCA and was able to successfully create a 250GB partition and install Windows 10 on it. Thank you!

Since you seem to be the resident expert on this (you seem to have replied to every BCA question in this forum), do you have any idea what the cause is? Does it stem from an initial failed attempted at installing Boot Camp (hence the need to erase disk0s3 with diskutil)?

Yes, I can create a FAT partition using Disk Utility.

The output of `sudo tmutil listlocalsnapshots /` is blank.