Bootcamp partitioning error in macOS 10.13
MacBook Pro (13-inch Mid 2012), macOS High Sierra (10.13)
I had the exact same problem with BootCamp Assistant and solved it with deleting local Time Machine snapshots.
Try my solution if you had turned on Time Machine Back Up Automatically.
tmutil listlocalsnapshots /tmutil deletelocalsnapshots <snapshot_date> (replace <snapshot_date> with the dates shown in the list, e.g. 2018-01-01-231501).Then start over in BootCamp.
Excellent. Can you post the output of diskutil list?
Please start a new discussion to avoid confusion, and post the output of
diskutil list
diskutil apfs list
diskutil cs list
on the new discussion.
I run the command and everythings seems to be ok.
Here is the output you ask.
MBPdeAlexandre:~ Alexandre$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *480.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 479.9 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +479.9 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD 200.2 GB disk1s1
2: APFS Volume Preboot 20.1 MB disk1s2
3: APFS Volume Recovery 517.4 MB disk1s3
4: APFS Volume VM 1.1 GB disk1s4
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *16.0 GB disk2
1: Apple_HFS Install macOS High S... 16.0 GB disk2s1
MBPdeAlexandre:~ Alexandre$
I have exactly the same issue on my MBA 128 SSD model. Gets this far then same message. I have 48gb free and am trying to allow 34gn for Windows 10. Have downloaded the anniversary rather than creator as directed by Microsoft. But can’t get last partition stage. Help!!
also running lastest Mac OS
Hi.
I Got apple support to help me and it worked. It is a LOCAL Time Machine "snapshot" issue. Even if TM is off and you disconnect the external drive...High Sierra saves "snapshots" to the local drive.
Here is the solution:
we’ll going to turn off Time Machine briefly and then after we finish Bootcamp setup we can turn the automatic backups back on. Though of course first question, do you have Time Machine setup?
colin benson
time machine is an external volume and is not connected.
Tiffany
Correct, but if you have it on at all, we need to delete the local Time Machine snapshots that may be saved which allows Boot Camp to partition the disk. These are the described more here. About Time Machine local snapshots
colin benson
time machine is neither connected nor on. i looked at what u sent me. how do i do that?
Tiffany
OK! Before moving further have you ever had it on, if so we will still have those snap shots. So we can go to Terminal, which is in the Utilities folder of your Applications folder then we’ll do the command to delete those.
Tiffany
Ahh I do see you had backups in the past so we definitely want to do this step.
colin benson
yes..last backup was yesterday evening.
colin benson
ok...i'm in terminal
Tiffany
Copy and paste the following command into Terminal, hitting enter after like usual:
tmutil thinlocalsnapshots / 9999999999999999
colin benson
done
Tiffany
Awesome! Now we should be good to go on that end so let’s go ahead and try to run Boot Camp again.
IT WORKS!
MBPdeAlexandre:~ Alexandre$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *480.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 380.0 GB disk0s2
3: Microsoft Basic Data BOOTCAMP 99.9 GB disk0s3
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +380.0 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD 144.8 GB disk1s1
2: APFS Volume Preboot 17.5 MB disk1s2
3: APFS Volume Recovery 517.4 MB disk1s3
4: APFS Volume VM 1.1 GB disk1s4
Your restore addresses multiple issues - file system corruption and the local snapshot occupying unnecessary disk space.
This indicates that the Apple BC Engineering and High Sierra Engineering do not regression test enough scenarios before launching products. Craig Federighi's organization needs to do better. The lack of automated switching between the OSes in HS is a big miss as well.
Hi,
I'm having the same problem, can you help me out please? I don't understand computer codes a lot, though. i'm running macOS 10.13.1 . I tried using the command tmutil thinlocalsnapshots / 9999999999999999 mentioned in one of the replies and then tried running bootcamp but got the same error again.
Thanks in advance! 🙂
Hello,
I have exactly same issue in High Sierra 10.13.2
I've already tryed all mentioned here as well as in other threads but problem still persist.
Is there any other way how to fix it unless reformatting/restoring whole system from scratch (which is something I don't want to do).
Disk Utility and cmd version are saying that on disk there is everything OK, TM is disabled and local snapshots thinned. I do have 1TB SSD, MacbookPro 13 with 16gb. Plenty of space.
Thanks for advice.
P.
Thank you! This worked for me. I really didn’t want to have to do a full erase and install.
This is a pretty disappointing bug tbh. Apple just doesn’t care as much about their desktop OS as they used to, and it shows.
I already try that and don’t work. And yes it is convert in APFS.
Switched off fire vault and I also typed tmutil thinlocalsnapshots / 9999999999999999 in the terminal
Still that bootcamp assistant won't let me create that bootcamp partition 😠
Any ideas?
I have tried that too, but it did not help. Looks like they did sometging wrong with High Sierra.
Thank this was help
Bootcamp partitioning error in macOS 10.13