Resource Monitor Widget Fixed in Windows 10

A while ago I asked if anyone could test the steampunk resource monitor for me on a Windows 10 system? Nobody responded to my pleas so I did the testing myself. I had to assume it was broken for all users under win10 but I was wrong.



The widget is here:
lightquick.co.uk/downloads/ste…

This Widget did NOT run on my version of Windows 10. First of all I thought that this was because Microsoft has changed the method required to access (Windows Management Instrumentation) classes on Windows 10 to allow the extraction of individual cpu information but I was wrong.

What occurred was that the performance data that is collected by the performance manager (%SystemRoot%/system32/perfmon.exe) was either corrupted or the pointers to collect the information had been damaged during the upgrade from Windows 8 to windows 10. I had spent hours trying to analyse and repair the WMI classes and subsystem that collect performance data but each and every time I tried I found empty data sets. I could not figure out what the problem was.

In the end a stroke of genius on my part, I realised that the information must not be being collected by Windows and that something, some component must not be doing the collecting. Knowing that the performance monitoring tool collects data on a continual basis I guessed that it is the component that should be filling the repository with data.

I ran the performance monitoring tool and received error messages about not being able to collect certain types of data. This was a big hint that it was the culprit that was causing my widget to fail. A quick search on the net brought up the solution.

To repair the pointers I did the following:

Clicked Start, typed cmd (right click cmd.exe, and select Run as administrator)
At the prompt, type lodctr /R and press ENTER. This repaired the pointers (stored in the registry).

If it is successful then the following message appears:
C:\Windows\system32>lodctr /r Info: Successfully rebuilt performance counter setting from system backup store

What did the error do to my widget? Well the bottom large gauges did not receive the WMI information they need to show CPU usage for each CPU on a dual/tri/quad core system. The widget then hung and needed to be closed and deleted. Now the pointers in Windows are fixed the widget should work successfully.

I will upload a new version of the widget shortly that should help in working in case of this error.

Note: install yahoo widgets first, then install the widget. The engine is here: lightquick.co.uk/jdownloads/ya…