Windows 7: Reliability Monitor - Reset

Under Windows 8 Pro.

I thought you might like to see this. The reg set command does not work. Apparently, there is no 'set' option for reg.exe in Windows 8. You have to create a .reg file and use IMPORT.... (at least I think that's the way you do it, not sure)

Secondly, The batch file cleared the logs and deleted the Reliability Monitor's database alright, but now two days later my reliability monitor seems to be broke. It's not collecting any data at all. Maybe it will in a few days.

Lastly, I'm not sure if this is related but in the task scheduler I see RACTask is running, and running, and running.... I think something is broke. I'm not sure what at this time.

reg set doesn't work in Windows 7 as well!

It must be:

Hello 8OHCO, and welcome to Seven Forums.

Thank you for bringing this to my attention.

The BAT file has been updated to correct the set/add issue. Please try it again to see how it works for you now.

The WMIEnable DWORD in the registry is set to 1 by default. The BAT is just making sure that it's still set that way.

I found the registry entry using regedit and verified it was there and set to 1. So I understood that part. I'm assuming that at some point there was a version of reg.exe that DID have a set option. Is that the case? Anyway, that's all beside the point.

My reliability monitor stopped displaying anything after running the batch file. Two days went by and still nothing showing up in there at all. No rating, no Info icons, no warnings - nothing. Apparently it doesn't like having its database deleted from %ProgramData%\Microsoft\RAC\... or something.

I have an Acronis full disk backup from 1/20/13. I'm thinking it might be best to simply restore it and move on.

This reliability rating is not some badge of honor and I don't really think it's worth resetting. It doesn't matter if the indexed was trashed to 1 after some installation went awry. Who cares, right? Thank you just the same, but I think I'll skip worrying about the reliability index in the future. I would rather have it intact and functioning than have it show a 10 that is in essence a falsehood, or worse yet, have it broken and showing no rating at all.

This is a clever, cool little batch file and I thank you for that, and I thank you for taking the time to reply.

If you ever find a way to delete some specific events from the Reliability Monitor's history let me know.

Best wishes. Beginning disk restoration now...

8OHCO,

Since this is for your Windows 8, did you run the .bat file twice, then restarted the computer?

In Windows 8, it will not work properly unless ran twice in a row first.

Yes, I did run it twice and reset the computer. It seemed to work great, but after a couple days I noticed that it wasn't logging anything at all.

I might be game to try it again tomorrow, but this time I'll do a full system backup right before I start. I just did my disk image restoration with Acronis True Image and all is well. I have a few individual files to restore from my online backup service before I get into trying the batch file again.

I was reading a forum somewhere else that said you don't need to clear the logs as the batch file does. That it worked to simply delete the RAC database in %ProgramData%... I was wondering if perhaps one could delete specific events from the Application log somehow. Then delete the RAC database. Then just let the system fly as usual. Would this be a method of purging specific events from the Reliability History? I'm not sure how to delete a specific event from a windows log. One either clears the entire log or changes nothing when using Event Viewer.

Without clearing the event logs as well, we found that sometimes the events will just show up again in Reliability Monitor within a few days.

I'm not aware of any way to delete specific events in a log in Event Viewer.

Please let me know how it went.

Ok, here's the deal. When you use the batch file it can take a very long time to rebuild the database and if there's no data for several months it could take so long that you might think it's broke, but it's not.

Today I restored my entire hard drive from a backup made on January 20th -- 11 days ago. It's taken 6 hours for the graph to even begin to show data for the time period of the 3 days following the backup.

The first graph below is set to show days. The second one shows weeks. Notice in the first graph that it only shows up to 1/23/2013. It took the system 6 hours to build the data for 3 days. So imagine how long it will take for the system to rebuild 6 weeks of data.

This all might sound convoluted. The bottom line is wait at least a week before you expect to see your graph rebuild itself in some cases. I just didn't wait long enough. I figured 48 hours was long enough. Nope! Not even close!

The batch file works fine. Just be aware that your graph might take forever and one day to rebuild itself. Nothing is broken.

Thank you for posting back and confirming 8OHCO.