steet wrote:
I think you're going way too far : this sort of problem can very well happen when you reboot your computer without closing it properly, for example. In that case, the software won't be able to boot because there is a session already existing or something like this. Again, the best thing to do would be to reinstall it.
I'm not saying to entirely reinstall Windows just to remove some software that has some simplistic method to solving; I'm only implying it. The files already exist though. I guess the files existing will be replaced, but reinstalling 'might' solve the problem- or make it worse.
Sessions don't normally exist after rebooting (processes yes, but not sessions). If seesions were still running you would know, because you would be getting the great "blue screen of death" with one of those fatal errors occurring and begins memory dumps. It could be that these few process are still running and need to be closed (like the set of a bad pair).
I dunno. I still think you may have a bad cluster though.