Sorry for the late replay, I pulled a all nighter writing a new program, it is a envelope printer, done my style. I needed it for myself but I decided to put it out on tweaking.com as another free tool when I am done
The hardest part about Windows Repair is that there is always unknown variables on peoples machines. I do my best to cover them and as I find more odd variables that cause trouble I dig in and find a way to keep that variable from happening.
I had one user who ran all the repairs on 10 machines all worked perfectly, then on one of them, a older one, crap hit the fan. Outlook pst files missing and all kinds of very very odd behavior. So i connected to him because that was very odd and it turned out that the hard drive had a butt load of bad sectors and when all the repairs ran files where moved and such on the hard drive by windows and his outlook pst file landed on one, and so in that case it was bad hardware that was the killer variable.
But then there have been other times, especially with Windows 8, where the repairs worked great on so many other windows 8 systems and yet was killing others. i dug in and found the variables about the marsh handlers and a odd bug in Win 8 where it deleted them if the permissions where changed, and then once I thought I had the permissions working another update from MS for 8 then broke that and threw a fit about permissions. So I dug in and found a fix for that variable as well, thus v2.8.0
So thats why I want to look at your system and look over any errors that are happening. If the cause is not hardware then I want to find out what was different on your machine, what unknown variable there was that caused the side effect, then I can put in a fix for the sucker and make my program better
How the hell can I type so much when I have been up for 36 hours? Oh well, hope you dont mind listening to a tired talkative geek
Shane