Bootcamp Error: "Your disk could not be partitioned". Windows 10 installation - REPOST

I rebooted and reset NVRAM (Cmd + Option + P + R). Twice to be sure.

I rebooted and reset SMC (Shift + Control + Option). Twice to be sure.

BC Assistant returns the same error again.

To be clear, I don't know whether DU will allow me to create a FAT partition, because I haven't tried. In a former message today, I mentioned that, after deleting snapshots, DU allowed me, for the first time, to choose the size of a new FAT partition. However, I never actually created the FAT partition (I never got to click "Apply").

After receiving the error again, I have gone to DU and tried to create a 40 GB FAT partition. I could not complete the process. These are the details returned by DU after the failed operation. Please note that the "warning" appears again, and a "APFS Container Resize error code is 49187" message (I am googling it now):

Partitioning disk “APPLE SSD AP0512J Media” (disk0)

Running operation 1 of 2: Add “Untitled” 40 GB by splitting “1_LAPTOP 512GB” (disk0s2) from 499,96 GB to 459,96 GB…

Aligning shrink delta to 40.002.007.040 bytes and targeting a new physical store size of 459.961.167.872 bytes

Determined the minimum size for the targeted physical store of this APFS Container to be 398.257.344.512 bytes

Resizing APFS Container designated by APFS Container Reference disk1

The specific APFS Physical Store being resized is disk0s2

Verifying storage system

Using live mode.

Performing fsck_apfs -n -x -l -S /dev/disk0s2

Checking the container superblock.

Checking the EFI jumpstart record.

Checking the space manager.

Checking the space manager free queue trees.

Checking the object map.

Checking volume.

Checking the APFS volume superblock.

The volume 1_LAPTOP 512GB was formatted by newfs_apfs (748.77.8) and last modified by apfs_kext (945.200.129).

Checking the object map.

Checking the snapshot metadata tree.

Checking the snapshot metadata.

Checking the extent ref tree.

Checking the fsroot tree.

Checking volume.

Checking the APFS volume superblock.

The volume Preboot was formatted by newfs_apfs (748.77.8) and last modified by apfs_kext (945.200.129).

Checking the object map.

Checking the snapshot metadata tree.

Checking the snapshot metadata.

Checking the extent ref tree.

Checking the fsroot tree.

Checking volume.

Checking the APFS volume superblock.

The volume Recovery was formatted by newfs_apfs (748.77.8) and last modified by apfs_kext (945.200.129).

Checking the object map.

Checking the snapshot metadata tree.

Checking the snapshot metadata.

Checking the extent ref tree.

Checking the fsroot tree.

Checking volume.

Checking the APFS volume superblock.

The volume VM was formatted by newfs_apfs (748.77.8) and last modified by apfs_kext (945.200.129).

Checking the object map.

Checking the snapshot metadata tree.

Checking the snapshot metadata.

Checking the extent ref tree.

Checking the fsroot tree.

warning: found orphan file extents (id 328, size 85159936)

Verifying allocated space.

Performing deferred repairs.

The volume /dev/disk0s2 appears to be OK.

Storage system check exit code is 0.

Shrinking APFS Physical Store disk0s2 from 499.963.174.912 to 459.961.167.872 bytes

Shrinking APFS data structures

APFS Container Resize error code is 49187

A problem occurred while resizing APFS Container structures.

Operation failed…

Cmd + R > Terminal > "diskutil apfs convert disk0s2" output is:

It seems a success. However, now I cannot boot from my internal SSD (disks02, where I had my working macOS). Booting while clicking "Option" returns:

The output of "diskutil list" is:

/dev/disk0 (internal):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme 500.3 GB disk0

1: EFI EFI 314.6 MB disk0s1

2: Apple_APFS Container disk1 449.0 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 50.3 GB disk0s4

/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +449.0 GB disk1

Physical Store disk0s2

1: APFS Volume 1_LAPTOP 450GB 387.8 GB disk1s1

/dev/disk2 (external, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *240.1 GB disk2

1: EFI EFI 209.7 MB disk2s1

2: Apple_APFS Container disk3 239.8 GB disk2s2

/dev/disk3 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +239.8 GB disk3

Physical Store disk2s2

1: APFS Volume macOS Mojave 14.7 GB disk3s1

2: APFS Volume Preboot 44.8 MB disk3s2

3: APFS Volume Recovery 510.0 MB disk3s3

4: APFS Volume VM 8.6 GB disk3s4

/dev/disk4 (external, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *2.0 TB disk4

1: EFI EFI 209.7 MB disk4s1

2: Apple_HFS 4_HD_BACKUP 500GB 500.0 GB disk4s2

3: Apple_APFS Container disk5 500.0 GB disk4s3

4: Apple_HFS 2_HD_MEDIA 1TB 999.9 GB disk4s4

/dev/disk5 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +500.0 GB disk5

Physical Store disk4s3

1: APFS Volume 3_HD_BACKUP 500GB 12.4 GB disk5s1

2: APFS Volume Preboot 45.0 MB disk5s2

3: APFS Volume Recovery 510.0 MB disk5s3

4: APFS Volume VM 8.6 GB disk5s4

Please, let me know next steps. I work from home, from the partition that currently is not bootable. I am writing this message from the Windows partition. Should I?

1. Boot from my new external SSD.
2. Format disks02 with "Mac OS Journaled + GUI Partition"
3. Install macOS Mojave
4. Update to 10.14.5
5. Reboot in internet recovery
6. Restore backup from TM

Here is the output of "sudo fsck_apfs -n -l /dev/rdisk1":

** Checking the container superblock.

** Checking the EFI jumpstart record.

** Checking the space manager.

** Checking the space manager free queue trees.

** Checking the object map.

** Checking volume.

** Checking the APFS volume superblock.

** The volume 1_LAPTOP 512GB was formatted by newfs_apfs (748.77.8) and last modified by apfs_kext (945.200.129).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking snapshot 1 of 12.

** Checking snapshot 2 of 12.

** Checking snapshot 3 of 12.

** Checking snapshot 4 of 12.

** Checking snapshot 5 of 12.

** Checking snapshot 6 of 12.

** Checking snapshot 7 of 12.

** Checking snapshot 8 of 12.

** Checking snapshot 9 of 12.

** Checking snapshot 10 of 12.

** Checking snapshot 11 of 12.

** Checking snapshot 12 of 12.

** Checking the extent ref tree.

** Checking the fsroot tree.

** Checking volume.

** Checking the APFS volume superblock.

** The volume Preboot was formatted by newfs_apfs (748.77.8) and last modified by apfs_kext (945.200.129).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

** Checking volume.

** Checking the APFS volume superblock.

** The volume Recovery was formatted by newfs_apfs (748.77.8) and last modified by apfs_kext (945.200.129).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

** Checking volume.

** Checking the APFS volume superblock.

** The volume VM was formatted by newfs_apfs (748.77.8) and last modified by apfs_kext (945.200.129).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

warning: found orphan file extents (id 328, size 85159936)

** Verifying allocated space.

** Performing deferred repairs.

** The volume /dev/rdisk1 appears to be OK.

I see.

The output of "diskutil apfs list" is:

=====

APFS Container (1 found)

|

+-- Container disk1 117D5B08-FCF5-4587-9BD9-A137E0915504

    ====================================================

    APFS Container Reference:     disk1

    Size (Capacity Ceiling):      499963174912 B (500.0 GB)

    Capacity In Use By Volumes:   401470423040 B (401.5 GB) (80.3% used)

    Capacity Not Allocated:       98492751872 B (98.5 GB) (19.7% free)

    |

    +-< Physical Store disk0s2 FFCA686C-3DFC-4CE8-9721-9C8FE8A929FC

    |   -----------------------------------------------------------

    |   APFS Physical Store Disk:   disk0s2

    |   Size:                       499963174912 B (500.0 GB)

    |

    +-> Volume disk1s1 A184D8BA-56CB-4A9B-897F-147CB2F2B43E

    |   ---------------------------------------------------

    |   APFS Volume Disk (Role):   disk1s1 (No specific role)

    |   Name:                      1_LAPTOP 512GB (Case-insensitive)

    |   Mount Point:               /

    |   Capacity Consumed:         398518554624 B (398.5 GB)

    |   FileVault:                 No

    |

    +-> Volume disk1s2 31A0DFA8-EA0E-498F-974C-A2DB1EDD6508

    |   ---------------------------------------------------

    |   APFS Volume Disk (Role):   disk1s2 (Preboot)

    |   Name:                      Preboot (Case-insensitive)

    |   Mount Point:               Not Mounted

    |   Capacity Consumed:         81387520 B (81.4 MB)

    |   FileVault:                 No

    |

    +-> Volume disk1s3 12E6B6D2-768C-41D7-ABEA-2F6D6D0889AC

    |   ---------------------------------------------------

    |   APFS Volume Disk (Role):   disk1s3 (Recovery)

    |   Name:                      Recovery (Case-insensitive)

    |   Mount Point:               Not Mounted

    |   Capacity Consumed:         1549455360 B (1.5 GB)

    |   FileVault:                 No

    |

    +-> Volume disk1s4 4325FDC7-C1D3-4708-9CB4-F5D466F3783A

        ---------------------------------------------------

        APFS Volume Disk (Role):   disk1s4 (VM)

        Name:                      VM (Case-insensitive)

        Mount Point:               /private/var/vm

        Capacity Consumed:         1159479296 B (1.2 GB)

        FileVault:                 No

I did reboot in Single User Mode (Cmd + S) and "fsck_apfs -s -o -y /dev/rdisk1" before opening the first thread.

I have done it again now, after cleaning a new snapshot in my SSD. This is the output:

Sadly, BC Assistant returns the same error again: "Your disk could not be partitioned. An error occurred while partitioning the disk. Please run Disk Utility to check and fix the error".