I remember having this problem when Server 2012 R2 had just come out, but after searching online, I managed to solve it through some magical combination of GPO settings. Now we have a few Server 2016 ...

Two days after the patch rolled out, Microsoft provided instructions for dealing with reported problems -- but the new fixes don't work either Be glad you aren’t in charge of a Windows Server Update ...