Unable to boot bootcamp after resize

I would like to delete:

/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +64.0 GB disk1

Physical Store disk0s4

1: APFS Volume FREEdata 892.9 KB disk1s1

But disk utility will not let me delete it.

There is no windows bootcamp listed on the boot-selection screen. I was able to get to a DOS command prompt and pull some information about the disks that windows thinks are there:

I have the attached image as a Text readable PDF too

Thank You.

Late 2011 A1286, windows 8.1 (it is all bootcamp supports)

Can I follow the instructions previously to recreate the MBR at [Help] Can't boot to windows (8.1) after resizing partition

Its for a different version of macOS.

APFS Containers (2 found)

|

+-- Container disk1 4E75942C-A460-43D7-A8DB-578F18D2A33E

| ====================================================

| APFS Container Reference: disk1

| Size (Capacity Ceiling): 63999905792 B (64.0 GB)

| Minimum Size: 2572197888 B (2.6 GB)

| Capacity In Use By Volumes: 122880000 B (122.9 MB) (0.2% used)

| Capacity Not Allocated: 63877025792 B (63.9 GB) (99.8% free)

| |

| +-< Physical Store disk0s4 C2F319B7-ACC0-4576-B679-E85AABE57612

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

| | APFS Physical Store Disk: disk0s4

| | Size: 63999905792 B (64.0 GB)

| |

| +-> Volume disk1s1 43D2B8BC-09D6-4248-9BE6-550F20F183CB

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

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

| Name: FREEdata (Case-insensitive)

| Mount Point: /Volumes/FREEdata

| Capacity Consumed: 2379776 B (2.4 MB)

| FileVault: No

|

+-- Container disk2 A575CC31-7736-470B-8691-A524CB3530FF

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

APFS Container Reference: disk2

Size (Capacity Ceiling): 1816371318784 B (1.8 TB)

Minimum Size: 1442128662528 B (1.4 TB)

Capacity In Use By Volumes: 1075798605824 B (1.1 TB) (59.2% used)

Capacity Not Allocated: 740572712960 B (740.6 GB) (40.8% free)

|

+-< Physical Store disk0s2 EDB9E0F6-ABD6-4F6A-9203-B786B8203899

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

| APFS Physical Store Disk: disk0s2

| Size: 1816371318784 B (1.8 TB)

|

+-> Volume disk2s1 CF9DA54A-544F-3854-A759-9E5ACFDC964B

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

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

| Name: SSD (Case-insensitive)

| Mount Point: /

| Capacity Consumed: 1065348878336 B (1.1 TB)

| FileVault: Yes (Unlocked)

|

+-> Volume disk2s2 2215B4B0-8AB6-4D84-BE1D-656EB1ED8C51

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

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

| Name: Preboot (Case-insensitive)

| Mount Point: Not Mounted

| Capacity Consumed: 26464256 B (26.5 MB)

| FileVault: No

|

+-> Volume disk2s3 34262FAF-FBF4-44E8-9358-A6FB2E8DA872

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

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

| Name: Recovery (Case-insensitive)

| Mount Point: Not Mounted

| Capacity Consumed: 518778880 B (518.8 MB)

| FileVault: No

|

+-> Volume disk2s4 EDB13BAB-ACC9-4988-B315-F60AF284B700

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

APFS Volume Disk (Role): disk2s4 (VM)

Name: VM (Case-insensitive)

Mount Point: /private/var/vm

Capacity Consumed: 9663696896 B (9.7 GB)

FileVault: No

bash-3.2$ diskutil apfs deleteVolume 43D2B8BC-09D6-4248-9BE6-550F20F183CB

Started APFS operation

Deleting APFS Volume from its APFS Container

Unmounting disk1s1

Deleting Volume

Finished APFS operation

bash-3.2$ diskutil apfs deleteContainer 4E75942C-A460-43D7-A8DB-578F18D2A33E

Started APFS operation on disk1

Deleting APFS Container with all of its APFS Volumes

Unmounting Volumes

Deleting Volumes

Deleting Container

Wiping former APFS disks

Switching content types

Reformatting former APFS disks

Initialized /dev/rdisk0s4 as a 59 GB case-insensitive HFS Plus volume with a 8192k journal

Mounting disk

1 new disk created or changed due to APFS operation

Disk from APFS operation: disk0s4

Finished APFS operation on disk1

bash-3.2$ diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *2.0 TB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk2 1.8 TB disk0s2

3: Microsoft Basic Data BOOTCAMP 116.4 GB disk0s3

4: Apple_HFS Untitled 63.9 GB disk0s4

/dev/disk2 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +1.8 TB disk2

Physical Store disk0s2

1: APFS Volume SSD 1.1 TB disk2s1

2: APFS Volume Preboot 26.5 MB disk2s2

3: APFS Volume Recovery 518.8 MB disk2s3

4: APFS Volume VM 9.7 GB disk2s4

/dev/disk4 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme +20.0 GB disk4

1: EFI EFI 209.7 MB disk4s1

2: Apple_HFS Encrypted Data 19.7 GB disk4s2

Will we absorb "4: Apple_HFS Untitled 63.9 GB disk0s4" into "2: Apple_APFS Container disk2 1.8 TB disk0s2" and "1:APFS Volume SSD 1.1 TB disk2s1"?

Is there a way to create the partitions where we want to and use the Disk Utility Restore function to copy the Bootcamp drive like I did before.

Shed Disk space from disk0s2

Then add it to disk0s4

Then "RESTORE" disk0s3 to the new bigger disk0s4

Then absorb the free disk that was Bootcamp (disk0s3) into Physical Store disk0s2 and disk2s1 ?

I have previously used the Disk Utility Restore function to copy the Bootcamp drive to where it is.

Loner T wrote:

Did BC/Windows work after this operation? Windows is NTFS and moving it is very tricky.

I can not tell if the BC/Widows works; I can access any data on the Drive in macOS as if it were working normally. I opened images from the Windows Desktop to test.

Intervening partitions do not allow such operations. However, you can absorb disk0s3 into disk0s4 using Gparted.

I could live with disk0s3 into disk0s4 for now but that would make my BC excessively big as I got into this situation by doubling it from its original 64Gb.

Matt

I only get the option to boot Mac OS. My goal was to fix my inability to select bootcamp to boot into after I resized the bootcamp drive.

I can boot into my windows DVD and see if I can run a diagnostic on the Bootcamp partition.

bash-3.2$ sudo fdisk /dev/disk0

fdisk: /dev/disk0: Operation not permitted

bash-3.2$ sudo fdisk /dev/rdisk0

fdisk: /dev/rdisk0: Operation not permitted

I also tried some other permutations and got lots of "Operation not permitted"