System Health Report

I tried it today on build 14393.187and it worked(this time)

Today was one of those days where it worked:)
This time I ran the command perfmon /report from PowerShell ISE.

I just wanted to update the thread, and let anyone who is still subscribed know, that since the Creators Update, every time I run perfmon /report it works.

Previously, as you all know, it was always hit & miss, but at least on my machines, it's working, and helping me find things that might need to be fixed(if they can be) or at least give me a little more clarity on some of the errors in Reliability History.



@Brink might find this one interesting, as I believe he has a tut for the winsat scores(unless I'm wrong)
Also something I never noticed before, is the Desktop Rating.


It is found when your run winsat formal in the command prompt, but to find the score, you had to dig down to C:\Windows\Performance\WinSAT\DataStore\ Formal.Assessment (Recent).WinSAT and find the scores in the XML file that popped up in the browser.

Hey Cliff, :)

So far Windows 10 can still use option 2 or 3 in the tutorial below for WEI score. It's just that the WEI score is really no longer used in Windows 10 anymore.

Windows Experience Index - Update or Refresh WEI Score in Windows 8

I'll work on getting a W10 tutorial for the System Health Report and WEI soon though.

Brink said:

Hey Cliff, :)

So far Windows 10 can still use option 2 or 3 in the tutorial below for WEI score. It's just that the WEI score is really no longer used in Windows 10 anymore.

Windows Experience Index - Update or Refresh WEI Score in Windows 8

Neither are all the benchmarks I run, but.... It's still fun to see what comes up
Running winsat formal is also needed when new hardware is installed(specially SSDs as a system disk) so the system can make needed adjustments to itself.
The desktop score is just a side effect is all.

The Health Report is what most people should use in conjunction with Reliability History to find "real problems", and use Event Viewer only to see if you can find out when it started, or if you are lucky, what is causing that specific problem.

Too many go strait to Event Viewer and see timeout errors, and start panicking over nothing.

fdegrove said:

Hi,

Works for me as well. Thanks, Cliff, I sorta had given up on it ever working again.
Ran it from cmd prompt admin.
best of all: not a single rat in sight....

Cheers,

Mine keeps complaining about the empty PS/2 Keyboard and PS/2 Mouse jacks, I could just uninstall the drivers for those useless things, I use USB. The other is a service for MSI Command Center MSIDDRService.exe, version: 3.0.0.10,, which is justified, as after the Creators Update, anything to do with RAM information will not work.

I fixed most of the "bugs" to 3rd party stuff, but this is beyond me, and needs to be fixed by MSI's devs.

I just use AIDA64 for the informational stuff & monitoring anyhow, and need Command Center only when I want to crank the fans all up to full speed.

I'm thinking it may be best to name the tutorial with "System Diagnostics Report" instead of "System Health Report" since that is actually the name for it.

and on mine its working :)

Cliff S said:

I tried it today on build 14393.187and it worked(this time)