That is certainly strange! I can't seem to find much online about the issue, though I saw a couple of recommendations about disabling Secure Boot. I'm not sure why that would make a difference (especially given Microsoft's involvement with OEMs and Secure Boot...) and it probably wouldn't be the best thing to keep turned off permanently (or rather, as a "disclaimer": if you haven't already, do a bit of light researching on secure boot and why it exists) but it wouldn't hurt to try turning it off temporarily (if its not already off) to see if that gets past the error.

I did get a chuckle out of this bit from Microsoft's docs on the error:

Cause: This problem occurs because the boot firmware on the computer generates lots of memory fragmentation.

Workaround: We recommend that you do not let boot firmware create large amounts of fragmentation. Large memory fragmentation degrades the overall startup performance and causes problems.

Ah that's real helpful Microsoft, thank you!