"Going forward, as new silicon generations are introduced, they will require the latest Windows platform at that time for support....For example, Windows 10 will be the only supported Windows platform on Intel’s upcoming “Kaby Lake” silicon, Qualcomm’s upcoming “8996” silicon, and AMD’s upcoming “Bristol Ridge” silicon."
If windows 10 is the only supported OS, why not get rid of 16bit real mode and 32bit protected mode, leaving only 64bit long mode as the only execution environment?
Just looking at the list of Microsoft applications currently running on my 64-bit Win10 desktop, there's still at least a half-dozen different Windows desktop services that are running in 32-bit mode - including the "Microsoft Bing Service".
I'm sure they'll eventually want to reach a point where they can cut that off, presuming that a hybrid approach like x32 doesn't turn out to have phenomenal benefits, but it's not yet here.
I guess I should have said, "leaving only long mode" (which can be 64bit or 32bit)
I wonder how much they'd actually save, in die area, if they removed 32bit mode while leaving in the ability to run 32bit code in 64bit mode. If it's just decoding to similar microops with slightly different parameters depending on the mode they're returning to, probably not that much, except in the decoder itself...
1) Actual blacklisting of the CPU in a Win7 update.
This would be foolish at best, since people would just decline the patch or use modified install media.
2) Lack of support through lack of drivers for new hardware
Maybe the most likely, but still not guaranteed to prevent people from running Windows 7 and either working around missing support or disabling the signed driver requirement and hacking up newer drivers until they do what's desired on Win7.
3) Requiring Win7 backward-compat hooks in BIOS/UEFI not be present on Kaby Lake+ motherboards.
This would probably be the most effective, though it would require more coordination and signoff than I'd necessarily guess they'll muster.
I believe this is pretty much it. It is my understanding that there are a ton of features on a processor today that are not simply the x86/amd64 instruction set. These things require the Hardware Abstraction Layer (HAL) to be updated in order to support them. This is all code written in x86/amd64 ASM in order to interface with the processor and MSFT simply will no longer backport this code to its older OSes.