It is a known issue confirmed by Microsoft.
Issue is caused by below KB security updates:
Issue is caused by below KB security updates:
KB3114351
KB3101496
Workaround solution is to uninstall the above patches.
Permanent solution is to wait till Feb or March CU
No comments:
Post a Comment