Just dropping by to say legacy CPU Usage seems to be functional and working properly again on Windows 11. I have only to thank @Martin for the time, patience and dedication.
Not yet! But, as a Windows 11 user, yesterday I downgraded to v7.42 (where the IdleTime patch was applied) and now CPU Usage is reporting much higher and realistic values than v7.44 (which was nearing 0% most times), just like @Vimes reported.
Please correct me if I'm wrong, but it seems Windows 11 is still broken when it comes to the legacy time-based CPU metrics. If the IdleTime workaround is not applied when using Windows 11, the legacy method will always report unrealistic low values, therefore being unreliable.
I mostly used the classic time-based CPU usage metric in the past to understand how my resources were being utilized during a game session. I would leave Hwinfo or Hwmonitor running in the background while gaming and then I would come back at the end to check the maximum values for CPU usage...
Thank you so much for the insight! It made things very much clearer for me now. Maybe you have explained this elsewhere, but if I may, I'd just like to understand why this fully legitimate legacy time-based usage, now applied to v7.44, still presents such low values. Are they the correct ones on...
I understand the difference between time-based CPU Usage and the new CPU Utility, but I think CPU Usage really is broken considering time-based metrics. Before the latest update, MSI Afterburner CPU usage numbers were perfectly matching the Total CPU Usage from HWinfo64. I just updated HWinfo...