This bug keeps on coming and going for some user's and if you sit down and analyze it, you will realize that it's a Window and Manufacture software error bug. Microsoft will never admit it and the manufactures will deny it. But both parties are to blame for selling you a product that works when it wants to work. The reason for this is because either side don't sit down together to get work out the problem. It's easier to pass the buck and blame each other.
With this comes this great utility that hopefully will fix your problem for the time being until another major software update. Good luck.
Link