In January of last year MS put out a kb that would repeatedly reboot your machine if it was an active directory controller, or if it was a hyper-v host it would refuse to turn on VMs, if you were running 2012 R2.
Not only this is bullshot for a production os (like this is 5 minutes of testing, come on), it took them several months to put out a corrective KB. In the mean time, all you could do was not install it and try to uninstall it on hosts that would reboot repeatedly. It’s windows server so it doesn’t nag you for updates but still.
themoonisacheese@sh.itjust.works 10 months ago
In January of last year MS put out a kb that would repeatedly reboot your machine if it was an active directory controller, or if it was a hyper-v host it would refuse to turn on VMs, if you were running 2012 R2.
Not only this is bullshot for a production os (like this is 5 minutes of testing, come on), it took them several months to put out a corrective KB. In the mean time, all you could do was not install it and try to uninstall it on hosts that would reboot repeatedly. It’s windows server so it doesn’t nag you for updates but still.