Windows Boot Manager error, winload.exe

The command we used does not repair the GPT. To repair it, we need to run GPT FDisk in interactive menu. See https://www.rodsbooks.com/gdisk/gdisk.html for reference. A reboot can re-order disks, so be careful.

You need to run (do not type text like this). Let us try to repair disk0 (your macOS disk). Be careful, in each menu, the one-character command can mean different types of requests.

sudo gdisk /dev/disk0

2 (Choose 2, if prompted)

p (print)

x (Experts menu)

n (New Protective MBR)

o (print Protective MBR)

p (print GPT)

w (write the updated GPT)

y (confirm write)

q (quit, if necessary)

Do not reboot. Now post the output of

diskutil list

before we go further.

Much better. We need to correct disk1. Do not reboot yet, otherwise the disk order will change.

For current disk1 (do not type text like this), we will delete the current GPT, and rebuild the same entries in a different order. Check the Start/End values for any errors, before you execute the steps.

sudo gdisk /dev/disk1

m (main menu)

o (remove existing GPT/PMBR)

x (experts menu)

l ( this is lowercase L, set alignment to...)

1 (this is digit 1, 1 sector)

m (main menu)

n (New)

1 (GPT 1)

40 (Start)

409639 (End)

EF00 (EFI)

n (new)

2 (GPT 2)

409640 (Start)

410663 (End)

0C01 (EasyRE)

n (new)

3 (GPT 3)

411648 (Start)

976773119 (End)

0700 (NTFS)

p (print)

w (write)

y (confirm write)

q (quit, if necessary)

Now reboot, and check

diskutil list

and verify the order of partitions is EFI, EasyRE, NTFS on your Bootcamp disk. Once you confirm, we can go further.

As expected. Your GPT has been corrupted. We can try to correct this.

Can you install GPT Fdisk (https://sourceforge.net/projects/gptfdisk/) and post the output of

sudo gdisk -l /dev/disk0

sudo gdisk -l /dev/disk1

After GDisk is installed, run

sudo gdisk -l /dev/disk0

sudo gdisk -l /dev/disk1

and post the output.

Your disk0 and disk2 appear to be correct here. The Microsoft Reserved is unnecessary, but should not hurt anything if left as is. For you to see the Windows as bootable, we need to create a hybrid MBR on disk2. Too check what it has now, post the output of

sudo fdisk /dev/disk2

Some of the outputs are a bit confusing.

• For example, you original Bootcamp disk was

where Windows starts at sector 411648.

• Now, when you posted the GPT, I see

These are not the same disks. This is a regular Apple disk, but the GPT indices are are not in order.

We may need to get the output of the following commands

diskutil list

sudo gdisk -l /dev/disk0

sudo gdisk -l /dev/disk1

sudo gdisk -l /dev/disk2

sudo gdisk -l /dev/disk3

before we make any further changes.

The GPT entries have been reversed. 40-409600 should be GPT 1, 409640-976101344 should be GPT 2 and the last one should be GPT 3. We will need to recreate the GPT first using GDisk.

The GPT and MBR look good. Are you able to see Windows files in macOS Finder?

Can you post the output of

sudo gpt -vv -r show /dev/disk1

sudo fdisk /dev/disk1

Can you post the output of

sudo gpt -vv -r show /dev/disk0

sudo gpt -vv -r show /dev/disk1

It may be possible to get the GPT back.

Post the output of latest

sudo gpt -vv -r show /dev/disk2

We can derive the MBR from GPT to ensure they match.

Take a look at https://neosmart.net/wiki/0xc0000428/ .

Can you reboot and post the output of

diskutil list

Looks much better. Can you do the same steps on the bootcamp disk?

The Start/End values came from your GDisk output, and should match the provided values. We are not manipulating macOS disks, but the Windows disk, so macOS should continue to work. The changes made to GPT on the Windows disk are easily correctable and repeatable.

My recommendation is to correct these issues.