I don't know the cause, this is based on the numbers they reported to defend their decision to exclude older chips.

I think it has something to do with the modern instruction sets being kinder to the kernel and the fact that on computers with recent processors certain processor features are enabled in the UEFI config by default more often, but I couldn't tell you which features that would be. My hunch is that I has to to with stuff like virtualisation based security and the like?

This is a grade A bullshit, with a strong smell of marketing spin to it.

If a program crashes on an older CPU, it damn sure will crash on a modern CPU just as well.

> If a program crashes on an older CPU, it damn sure will crash on a modern CPU just as well.

Not necessarily; if the crash is caused by an instruction that's absent on older CPUs (for instance, trying to use an AVX2 instruction when the most the CPU has is SSE2), it will work on a modern CPU but crash on an older CPU.

Taken to the extreme, that’d be on par with an exe having a valid PE header but random noise for the code.

If foo can be launched on a platform that it’s not meant for, it’s an issue with foo, not the platform.

> I don't know the cause, this is based on the numbers they reported to defend their decision to exclude older chips.

Why would you present Microsoft PR as fact?