+1 here to. Windows Server 2012 R2. The above utility fixed it, not sure what did it.