Forum Discussion
Barbarank
Feb 21, 2025Iron Contributor
Windows 11 version 24H2 supported Intel processors
I just read that Microsoft will no longer support 8-10th Gen processors in regards to their Windows 11 version 24H2 update. So I have to ask if I bought a system that had a previously supported processor (but is not supported as of Feb 2025) does that mean the system will no longer get updates?
Hoping to get some clarity as to whether these previously supported CPU’s are no good now and are essentially paperweights which can get the latest update.
- Greg MessemerCopper Contributor
I was encountering an issue with installing Windows 11 version 24H2 on a virtual machine in our vSphere environment. We are running Intel Xeon Gold 5220 processors, which are on the approved CPU hardware compatibility list. However, when attempting to install Windows 11 24H2 on a VM configured with a virtual TPM, the installation fails. Notably, the same host with a virtual TPM installs other versions of Windows 11 (23H2, 22H2, and H1H2) without issue.
After thorough investigation, I discovered that Enhanced vMotion Compatibility (EVC) was enabled in our vSphere cluster and set to a compatibility level lower than what Windows 11 24H2 requires. So now I understand why I could not load 24H2. I'll remove or reset the EVC to an approved level.
This is the list of officially supported Windows 11 processors:
https://learn.microsoft.com/en-us/windows-hardware/design/minimum/supported/windows-11-supported-intel-processors
Can you check and confirm the processor you've is listed there? Alternatively, you can share the processor name so I can check for you.- Greg MessemerCopper Contributor
We're running Intel Xeon Gold 5220 processors, which are on the approved CPU hardware compatibility list. However, when we try to install Windows 11 version 24H2 on a virtual machine configured with a virtual TPM, the installation fails. Interestingly, the same host with a virtual TPM successfully installs other versions of Windows 11 (23H2, 22H2, and H1H2).
Has anyone encountered this issue or have any insights into what might be causing this discrepancy?