I restored the image I took before running the tool and the problem was already in existence.
The solution at technet.microsoft.com resolved the problem.
I read the link and looks like it was just a file and folder permissions problem for the default user profile. What is odd is my windows repair is suppose to fix that, on the file permissions repair for 7, 8 and 10 it will put back the defaults on that folder. Well i should also say that v3.4.2 had the permissions redone and updated.
So if the file permissions repair didnt fix it I would love to find out why and update the program
I noticed a couple of things, the Netlogon service should have a default of manual; apparently it's only if you're on
a domain (the tool set it to automatic)
Yes, I had to set it to auto for users who run the repairs on a domain, since when you are on a domain it is set to auto and not manual. It is annoying to see that entry in the event viewer at startup. Perhaps I need to add some code to detect if the system if part of a domain, if it is it puts it to auto, if it isnt it puts it to manual.
Secondly, perhaps it's worth mentioning in the right pane that the Windows update repair removes all the update history and
does a complete reset.
Correct because the windows updates is wiped and reset, but the installed updates still show up in add/remove programs and windows updates does rebuild its database of what updates are installed after you run it again. Thats why the first time you run it after the repair it takes a while, WU is rebuilding its internal database
Shane