I installed KB3087916 on both my 8.1 and 10 machines and saw this problem immediately on my 8.1 machine as have many other 8.1 users. After uninstall the update the problem was resolved. I have not had this issue crop up on my W-10 machine, yet anyway, but that doesn't mean it won't and it might be interpreted as just another W-10 bug by some users.

A good example of the problems that could be created with W-10 auto/forced updates when flawed updates are released.