Resize APFS partition and move it to another hard drive

This answer is not finished. Please do not edit!

This answer is based on the accepted answer to the question "Boot Camp Assistance is stuck on create a partition?". Modifications were made to include improvements suggested by user128216 to this answer.

Based on the lack of posted questions regarding using the Boot Camp Assistant to install Windows, I have assumed most users are successfully installing Windows on drives containing APFS partitions. When the Boot Camp Assistant fails, generally the problem is not with the Boot Camp Assistant, but rather with the APFS container. So, the usual solution is to backup your stuff, wipe the drive, and reload everything.

However, if you wish to install Windows without using the Boot Camp Assistant (except for creating the USB installation flash drive), you need to first determine how much space is available for Windows. This can be determined from the output of the command diskutil apfs resizecontainer diskXsY limits, where X is the drive number identifier and Y is the partition number of the APFS container.

These are the basic steps needed to install Windows 10 for an EFI boot.

Note: To get a better view of the images shown below, either click on an image or open an image in a new window.

1. Use the Boot Camp Assistant application to copy the Windows 10 installation files and the Boot Camp Support Software to a 16 GB or larger flash drive. A USB 3.0 flash drive would operate considerably faster than a USB 2.0 flash drive.

2. The command below will create the 70 GB "BOOTCAMP" partition on your internal SSD drive. The space occupied by this partition will be used for installing Windows.

   sudo  diskutil  apfs  resizeContainer  disk0s2  180.8G  FAT32  BOOTCAMP  70G
   

3. If you have not already done so, insert the flash drive containing the Windows 10 installation files and the Boot Camp Support Software.

4. Use the command shown below to rename the AutoUnattend.xml file.

   mv  /volumes/WINSTALL/AutoUnattend.xml  /volumes/WINSTALL/NoAutoUnattend.xml
   

5. Next, you need to boot from the volume where the Windows installation files reside. Hold down the option key immediately after restarting on your Mac. Release the option when the Startup Manager window appears. Select the icon labeled "EFI boot". Next, select the arrow below the "EFI boot" label.

6. Open a Windows Command Prompt window, by following the procedure outlined in this step. Below is an image of what is initially displayed by the Windows 10 installer. Select "Next".

   

   In the image shown below, select "Repair your computer".

   

   In the image shown below, select "Troubleshoot".

   

   In the image shown below, select "Command Prompt".

   

   The result should be the image shown below.

   

7. Use the command diskpart to finish partitioning disk0. The commands you need to enter are given below.

   Note: Sometimes it can take a while for the diskpart command to produce the first prompt. Be patient.

   diskpart
   list  volume
   

   From the output of the command list volume, determine the number for the volume with the label "BOOTCAMP". In this example, I will assume the number is 0. Your number could be different. The next command selects this partition.

   select  volume  0
   

   The next commands effect the "BOOTCAMP" volume. The format is changed to NTFS. Next, the size is shrunk by 600 MB.

   format  fs=ntfs  label=BOOTCAMP  quick
   shrink  desired=600
   

   Create a Windows Recovery Environment (WinRE) partition. The next commands create and initialize an empty 600 MB WinRE.

   create  partition  primary
   set  id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
   gpt  attributes=0x8000000000000001
   format  fs=ntfs  label=Recovery  quick
   

   The next command lists the current volumes. Take note of the drive letter (Ltr) for the volume with label "WINSTALL". In this example, I will assume the letter is D. Your letter could be different.

   list  volume
   

   The command below quits the command diskpart.

   exit
   

8. Enter the command below to start the Windows installation. If the drive letter, for the "WINSTALL" volume, is not D, then make the appropriate substitute when entering the command below.

   setup  /unattend:D:\NoAutoUnattend.xml
   

9. When a window similar to what is shown below appears, select the "BOOTCAMP" partition, then click on the "Next" button.

   

10. Continue with the installation of Windows 10. If the computer boots back to macOS, goto System Preferences and select Windows as your startup disk. Restart the computer to continue initializing Windows 10.

11. When finished, the Windows Support Software installer should automatically launch. If this does not occur, use the Windows File Explorer to open the Windows Support Software application named "Setup". This application can be found in the "BootCamp" folder on the "WINSTALL" drive. After the installer application completes, allow the computer to restart.

If asked, I can clarify any of the above steps.

Note: Posting images of the output from the Terminal application can often lead to users not posting an answer to a question. You should copy and paste the text to your question. Once pasted, highlight the text, then click on the code sample button {} to format the text.

Your current APFS partition (disk0s2) does not appear to be valid for several reasons. Below are three reasons.

1. The magic number stored in the header is incorrect. Also, the header defines the block size to be 2,385,839,421 bytes and the APFS container to be 2,777,634,813,198,357 TB in size. The magic number should be BSXN. The block size should be 4096 bytes and the container should be less than or equal to 883,222,061,056 bytes in size.
2. The APFS partition size of 1,725,043,095 logical sectors is not divisible by 8.
3. The APFS partition should appear either immediately and soon after the EFI partition (disk0s1). Here, the partition starts 116,773,068,800 bytes after the end of the EFI partition.

It appears that an APFS partition of 960,018,657,280 bytes in size did occur immediately after the EFI partition (disk0s1). The problem is the data stored in the APFS partition was partially overwritten by the data now stored in disk0s3. The type and location of disk0s3 would indicate that macOS Sierra may have been installed close or immediately before disk0s3. If this is true, then additional data stored in the APFS partition may have been overwritten.

Note: The partition entries stored in the GPT are not in ascending order. While this does not create problems for Ubuntu, this condition oftend leads to an incorrectly functioning macOS.

To correct the GPT, you need to remove the second and third entries. The commands are given below.

Note: You must unmount all volumes from disk0 before entering the commands given below.

sudo gpt remove -i 2 /dev/disk0
sudo gpt remove -i 3 /dev/disk0

The command below will add the APFS container to the GPT.

sudo gpt add -i 2 -b 409640 -s 1875036440 -t apfs /dev/disk0

There is no guarantee fixing the GPT will automatically lead to a correctly functioning APFS partition.

When finished, the output from sudo gpt -r show /dev/disk0 should appear as shown below.

     start        size  index  contents
         0           1         PMBR
         1           1         Pri GPT header
         2          32         Pri GPT table
        34           6         
        40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
    409640  1875036440      2  GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC
1875446080    78079055         
1953525135          32         Sec GPT table
1953525167           1         Sec GPT header