By the looks of it that isn't correct either. Hmm. No matter. There is definatley something wrong here since when using the __cpuid and __cpuindex functions (from low level C++ and ASM) I was able to get this information so it clearly is there - it's just that WMI isn't reading it for whatever reason.

It is quite strange actually - I've never seen an issue like this before using WMI.