The issue is caused by a bug in the KB3057839 windows update. The bug has been reported to Microsoft and can be tracked at the following link: https://connect.microsoft.com/VisualStudio/feedback/details/1475291 Currently the only workaround is to revert the KB3057839 update on the production server.