James,

Thank you very much for letting everyone know about the exact KB number. Your input will help many users. Quite a few users have confirmed, via email as well as on this forum, that uninstalling KB mentioned by James solves the problem. 

Your Help

We need to report this to Microsoft. However, it is very difficult to explain this behavior unless we are able to reproduce this on our end. Can someone please give us a VM or access to a machine via RDP that is running into this issue so we can have Microsoft look at it.