Alright. Thanks for all this info. Makes sense this way, but at the moment I asked, I saw just the thing that there is a great difference between what Rainmeter reports and what I can see in Task Manager.I believe the differences you are seeing are due to the way "usage" is being calculated. Microsoft made a major change back in Win11 22H2, but it was even different before then.
In Windows 7 (and if you use Rainmeter's CPU measure or CPU alias on the Usage Monitor measure), you will be getting usage calculated based on a "percentage time" basis. The counter is "Process" and the instance is "% Processor Time".
Since Windows 8, and especially since Win11 22H2, Windows Task Manager does not report CPU or process usage using these legacy counters. CPU performance is reported using the "Process Information" counter's "% Processor Utility" instance, not the older "Processor" counter's "% Processor Time" instance. These are very different.
For processes, Task Manager now uses the "Process V2" counter, not "Process". This is why you are seeing differences.
Rainmeter has no way of using the "Process V2" counters, due to a glitch in the parsing logic of the UsageMonitor measure. I submitted a pull request on GitHub to resolve this issue, but I don't know if anyone has looked into it. It is a simple fix. Until then, there is no way for Rainmeter to report process usage like Task Manager does.
Yes, I had an impression I read about this on the forum, but couldn't find the post(s).By the way, this is old info. I've posted several times about this back when 22H2 came out, though it was mostly about the CPU measure(s).
Statistics: Posted by balala — Today, 3:38 pm
