CPU speed misdetected about whynotwin11 HOT 12 CLOSED

Are you running the application in the Hyper-V VM?

from whynotwin11.

Maybe this will help:
Get-CimInstance Win32_Processor | Select-Object -Expand MaxClockSpeed

from whynotwin11.

Maybe this will help:
Get-CimInstance Win32_Processor | Select-Object -Expand MaxClockSpeed

Pretty sure I'm already getting this value in Line 22 of \includes\WMIC.au3

from whynotwin11.

I'm not running it in a Hyper-V VM, but because of the way Hyper-V works, the "Host" OS is still a Guest, albeit one with a lot more access.

And for reference:

PS C:\WINDOWS\system32> Get-CimInstance Win32_Processor | Select-Object -Expand MaxClockSpeed
801
PS C:\WINDOWS\system32> Get-CimInstance Win32_Processor

DeviceID Name                                     Caption                              MaxClockSpeed SocketDesignation
-------- ----                                     -------                              ------------- -----------------
CPU0     Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel64 Family 6 Model 60 Stepping 3 801           SOCKET 1150


PS C:\WINDOWS\system32>

The reason I mentioned Hyper-V is: https://www.hanselman.com/blog/windows-task-manager-shows-wrong-cpu-speed-when-using-hyperv

Apparently there's a "Fix": https://docs.microsoft.com/en-US/troubleshoot/windows-client/performance/task-manager-shows-incorrect-cpu-speed - Use the "\Hyper-V Hypervisor Logical Processor\Frequency" performance counter.

from whynotwin11.

Hypervisor detection:
Get-CimInstance Win32_ComputerSystem | Select-Object -Expand HypervisorPresent
https://devblogs.microsoft.com/scripting/use-powershell-to-detect-if-hypervisor-is-present/

from whynotwin11.

Maybe this will help:
Get-CimInstance Win32_Processor | Select-Object -Expand MaxClockSpeed

This incorrectly detect 2101 MHz, my CPU can reach 4.8 GHz

from whynotwin11.

Spent a bit of time looking for a good solution to this and pretty sure there isn't one.
Removing the CPU Frequency check is probably fine, nobody legitimately fails it, all the complaints are either because the printed number is wrong or because of virtualisation. The CPU Compatibility check indirectly covers it anyway.

from whynotwin11.

Maybe
https://www.dell.com/community/Rack-Servers/Wmic-command-to-get-cpu-current-clock-speed-is-same/td-p/6108886

from whynotwin11.

Maybe
https://www.dell.com/community/Rack-Servers/Wmic-command-to-get-cpu-current-clock-speed-is-same/td-p/6108886

Nope

from whynotwin11.

What I'll do is grab the @ from the CPU string and report that if there's a discrepancy. Although this will only work for Intel CPUs

from whynotwin11.

What I'll do is grab the @ from the CPU string and report that if there's a discrepancy. Although this will only work for Intel CPUs

And only for non overclocked CPU. Look at mine, it report 2.10 GHZ, it actually runs between 800-4800 MHz.

from whynotwin11.

In my opinion only stock speeds should be supported, sure, you can oc many cpus to 5ghz but have fun trying to run that.

from whynotwin11.