windows 7 reliability monitor

the thread originated here https://www.wilderssecurity.com/showthread.php?p=1888483#post1888483

and had to conveniently re-initiate it due to "Sorry, that thread is too old to be replied to. Please look for a more current thread on the same subject or start a new thread for your post." A thread from June this year?

back on topic now

to my experience this has still not being fixed "with an automatic HIPS module update".

will it be or not?

 

Unfortunately there's nothing new on that matter as even replacing all blocking rules with one general rule allowing all operations in the code the issue persisted. It's still listed as an open bug and an in-depth analysis will be required.

 

just hope that this thread has not to come up when the final is released because the bug hasn't been fixed by then...