Wednesday, October 22nd 2025
Intel "Nova Lake" Could Arrive Without AVX10, APX, and AMX Support
Intel is still finalizing its next-generation "Nova Lake" specifications. However, the core microarchitecture has been done, the NPU design is finished and upgraded, and the instruction set is finalized. It could be the case that these consumer CPUs will again lack support for Intel's AVX10, APX, and AMX instruction set—designed to encompass 512-bit acceleration and fast vector/matrix multiplication for tasks like content creation, encoding/decoding, AI, and much more—remaining exclusive to Intel Xeon processors. According to the latest GCC compiler patch, the initial Nova Lake enablement patch does not include AVX10, AMX, or APX. This might suggest that support for these new x86 instructions could be missing from the next-generation CPU. Initially, Intel decided to disable AVX-512 for "Alder Lake" and "Raptor Lake" client-oriented CPU lineups, meaning that only server-grade Xeon CPUs got the accelerated 512-bit data paths.
This GCC patch seems to contradict the findings from August, when Intel introduced AVX10.2 support for "future Intel Core processors" in the oneDNN software library, likely targeting the Nova Lake series. We need to wait for more information from other enablement patches or direct confirmation from Intel regarding whether AVX10, APX, and AMX will be included in the 52-core Nova Lake SKUs. Enabling fast vector and matrix acceleration on 52 cores would be ideal for consumers, content creators, gamers, and workstation users alike. In comparison, AMD introduced full AVX-512 support with its "Zen 5" cores across its product range, providing a performance boost in optimized applications for both desktop and server CPUs. This marked the first time AMD did not emulate 512-bit AVX, which previously required splitting 512-bit data into two 256-bit units to be processed over two cycles.The latest patch states the following instructions are now supported:
Source:
Phoronix
This GCC patch seems to contradict the findings from August, when Intel introduced AVX10.2 support for "future Intel Core processors" in the oneDNN software library, likely targeting the Nova Lake series. We need to wait for more information from other enablement patches or direct confirmation from Intel regarding whether AVX10, APX, and AMX will be included in the 52-core Nova Lake SKUs. Enabling fast vector and matrix acceleration on 52 cores would be ideal for consumers, content creators, gamers, and workstation users alike. In comparison, AMD introduced full AVX-512 support with its "Zen 5" cores across its product range, providing a performance boost in optimized applications for both desktop and server CPUs. This marked the first time AMD did not emulate 512-bit AVX, which previously required splitting 512-bit data into two 256-bit units to be processed over two cycles.The latest patch states the following instructions are now supported:
Intel Nova Lake CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AES, PREFETCHW, PCLMUL, RDRND, XSAVE, XSAVEC, XSAVES, XSAVEOPT, FSGSBASE, PTWRITE, RDPID, SGX, GFNI-SSE, CLWB, MOVDIRI, MOVDIR64B, WAITPKG, ADCX, AVX, AVX2, BMI, BMI2, F16C, FMA, LZCNT, PCONFIG, PKU, VAES, VPCLMULQDQ, SERIALIZE, HRESET, AVX-VNNI, UINTR, AVXIFMA, AVXVNNIINT8, AVXNECONVERT, CMPCCXADD, AVXVNNIINT16, SHA512, SM3, SM4 and PREFETCHI instruction set support.

61 Comments on Intel "Nova Lake" Could Arrive Without AVX10, APX, and AMX Support
If going to AVX and AVX2 in that older Celeron and Pentiums, yes that was product segmentation. Equally as how HyperThreading (SMT) was reserved for segmentation purpouses by Intel as baseline only for Core i7 (i7 9700 be cursed without HT to favor the i9 9900 by Intel) or better in desktop back then, with only some specific desktop i3 SKUs exceptions having HT back then and HT being active in the whole Core i lineup only in mobile until Comet Lake that made it standard on all Comet Lake-S models.
Either way, it's very unfortunate for consumers that instructions meant for general use are segmented, not to mention a headache for developers.
Nova Lake listed as supporting AVX 10.2
The famous "all core turbo" exploit for Xeon E5 v3 processors actually requires you to initialize the processor raw, and then apply the microcode on top, which triggers the bug that the core 0 turbo multiplier (which is always the highest) gets applied to all cores. Windows will load mcupdate_GenuineIntel.dll upon boot, which has a newish (around the age of the OS) microcode, if you delete that it boots into Windows raw and you can use the VMware-provided driver to load any MCU version you want. Staying on 1F and below will preserve TSX functionality in E5 v3 CPUs, of course with the hardware bugs that led Intel to disable it.
Thanks for the insult, btw. Let me return it unused.
I understand why market segmentation exists, though some of these really make no sense to me. I think the most egregious case today is the Threadripper Pro processor. AMD got really greedy really fast there, since they have the HEDT market in a chokehold since Intel discontinued the X299 platform and phased the i9-10980XE out.
github.com/uxlfoundation/oneDNNThat's interesting, because I have a Comet Lake system deployed for some side things that aren't that primary to me and since someone else also is using that system from time to time that has Windows 11 installed right now, and I just updated it this week from 23H2 to 24H2 from Windows Update just fine. Microsoft it's even listing those CPUs in their 24H2 compatible CPUs list.
learn.microsoft.com/en-us/windows-hardware/design/minimum/supported/windows-11-24h2-supported-intel-processors
I do believe you, but I wonder what was preventing you from installing and updating. I know with the 400 and 500 Intel chipsets some motherboard vendors used to turn off some things like SecureBoot in their default settingin some models, I wonder if it could be a motherboard default setting turning off something and Microsoft's lately more agressive checks to some things they want putting off or I guess with Windows 11 track record lately, Microsoft could have just broken something temporarily for a bit too.