@fincoder The OS level patch mitigations of Spectre/Meltdown aren't working, per the people I know that actually work on this junk
meltdownattack.com
The problem here is the way these attacks work, they essentially subvert the entire OS and enable arbitrary code to be executed directly. This leaves no logs! And allows an EXE to live in a space where it will embed itself into either the EFI firmware directly, or one of your attached storage devices.
Once a system is infected, it's near impossible to detect the infection, and near impossible to clear the infection. If you've ever had the pleasure of trying to remove EMOTET from a network, you'll have an idea how annoying this is.
To my knowledge the only thing between this thing being a huge deal and not, is privilege separation. You do need admin on the box you're running the test code on to get it to execute. But once you've gotten it to execute you can bypass any and all sandboxes.
Microsoft's specific guidance is here:
https://msrc.microsoft.com/update-guide/en-US/vulnerability/ADV180002
Microsoft Windows client customers
Customers using Windows client operating systems need to apply both firmware (microcode) and software updates. See Microsoft Knowledge Base Article 4073119 for additional information. Customers using AMD processors should review FAQ #15 in this advisory for additional action you need to take. Microsoft is making available Intel-validated microcode updates for Windows 10 operating systems. Please see Microsoft Knowledge Base Article 4093836 for the current Intel microcode updates.
You will note, they ask for software updates AND firmware updates. But there is no firmware to update if you're not on 8th gen or younger. And if there is, did the mainboard vendor turn it into the BIOS update it needed to become?
I'm not sure if older than 8th gen Intel systems can be fixed, what I do know is that according to Microsoft if I'm not running a BIOS that's dated younger than the Meltdown / Spectre security release (Jan 2018), it's not fixed. The most recent BIOS for this 4th gen unit I'm typing on is 2016. Many platforms need a BIOS from 2020.
So I don't know if these older platforms can be fixed, what I do know is it's easy to see that for whatever reason the vendors aren't fixing them.
Intel calls the drop dead date "Self-Service Support Beginning", which is hilarious but you can see this all here:
https://www.intel.com/content/www/us/en/support/articles/000022396/processors.html
5th gen is already dropped. The hole between I cannot fully explain is 6th and 7th, because these platforms are still getting microcode updates, and many business grade Dell systems in this category can have TPM 2.0 as well as the microcode. So for these platforms to not be supported there must be another reason. I've heard rumors within the HyperV dev group that 8th gen had some additional instructions available that assisted HyperV. I cannot confirm this, because both the 6th gen and 8th gen Intel chips I've looked up both list Intel® SSE4.1, Intel® SSE4.2, Intel® AVX2 as their instruction sets. So if Microsoft is using something new to build their sandboxes on, it's not immediately clear via Intel ARK pages.
And, let's not forget, that Intel ages ago said you needed at least a first generation iSeries to be compatible with Windows 10. And yet how many of us had or have G Series CPUs still in service? I know I do... there's one on my repair bench!
So will Windows 11 run on this hardware long term? That's up to Microsoft. Will Microsoft say one thing and do another? Oh yes... most certainly. Am I going to be upgrading an older than 8th gen machine to Windows 11 in the future? Probably! Will it be supportable enough to be used in any level of production? That's... the $1,000,000 question. My gut says it will be, but we just don't know right now and I don't care too much about it because the problem is a non-issue until 2024. During that time I'll be working through a huge refresh of equipment anyway. What is possible then? We'll find out.
But for now I have to make decisions based on what Microsoft tells me they're willing to support. In the meantime the new Android native execution features of Windows 11 are already known to not work on older CPUs. Which is funny because Bluestacks works fine! The whole thing needs to cook.
For all we know right now, Microsoft may be making older systems not "upgradable" but usable on "fresh installs" just because they want us all to do a N&P to clear out old crap that's still there from Win7! We haven't a clue... because MS isn't talking.
I'm simply making educated guesses based on Intel's tech, and Microsoft's announced future plans for Windows 11, extrapolated a bit with the new toys Apple has been playing with. There's a trajectory here we can plan for, but it's all at best... precision guesswork, based on incomplete information, with data from a questionable source.