Reliability History not functioning

As the heading says.
Since the SP1 update, I have had issues with Win7.
The first one, not shutting down until 4-5 minutes later, resolved itself after I uninstalled a faulty program I had just installed (today).
My Network Meter gadget (version 6.5) stopped displaying the internal IP of my computer (I am behind a router), instead it says 'No Device Connected'. Yet it still reads the speeds correctly from the internal network card (the selected device for speed)
Now I discover (not sure for how long it was non functional) Reliability History not showing any information.

Does anyone have any solutions/suggestions?

See if this helps:

No more “reliability history after system recovery?” - Microsoft Answers

A Guy

It appears the issue lies not with Reliability Monitor, but rather with the Task Scheduler.
The task that records the info used by reliability Monitor is currently not found in Task Sceduler.
Please see attached files: error(1-7).jpg. Sometimes I will see the errors (see error0.jpg and error00.jpg), at which point it freezes, and I must use Task Manager to close it.
These are seen at startup of Task Scheduler.
Since I haven't done anything to this file, I don't know what would have caused it.

Ahhh, you have scheduled task problems to be sure. Did you ever play around in the Task Scheduler? If not, the question arises why so many error. It may be one, then their dependencies like dominoes. I'd think SFC wouldn't correct that, but a Repair Install likely would.

Repair Install

I can find a list of the default scheduled tasks in Vista, but not Seven

Description of the scheduled tasks in Windows Vista

But that doesn't tell you how to correctly reschedule them in any case.

A Guy

I've got a couple of PDF's I refer to when I work on the task manager and reliablility index. I'll up load the if you want me too.

Since I can't do a repair install (my Retail is pre-SP1), and last time I tried to uninstall SP1 I received errors and the uninstall rolled back to an installed state (maybe this had something to do with this happening?).
I would be happy to check the PDF's.

One of these is for the task manager. The other is for corrupt catalogue files.(third one is most important corrupted log.txt)
When stopping WMI I would get a succesful message returned but I would have to reenter the command a second time to get it to work. May have been me I don't know.
As for the corrupt files it corrected everything out. But it would occur again in about a week. I began to suspect that there was another problem. The take ownership of the two directories (C:\windows logs and C:\windows\system32\log files) made me think that there was some kind of permission problem.
I made a change in a security policy setting and it quit failing. The machine I did it on is down at present and I wont have it running until the end of the coming week so I can't be more specific right now.

Attachment 161914

Attachment 161915

Attachment 161916

Attachment 161917

Good Luck

I can't review them immediately, so I saved them under Google Docs.
Thank you. I will post back with results.