The updates KB4345418 and KB4054566 which Microsoft produced on July sixteen, 2018 feel to induce concerns these kinds of as large CPU load or RDS relationship concerns on Home windows Server 2012 R2 and Home windows Server 2016 in some scenarios.
The updates set concerns these kinds of as connectivity reduction scenarios, cease error 0xD1 when running network checking workloads, concerns that caused the restart of SQL servers to fall short, or concerns when attempting to cease the Globe Vast Web Publishing Provider.
The updates, KB4345418 for Home windows ten variation 1607 and Home windows Server 2016, and KB4054566, the Microsoft .Web Framework four.seven.two for Home windows eight.1, Home windows RT eight.1, and Home windows Server 2012 R2, have been developed to address the concerns explained. It seems that the updates may perhaps introduce concerns of their individual on techniques they are put in on.
Server directors started off to report concerns that they discovered following set up of the updates soon following release.
A person challenge was that Microsoft Azure Active Directory Hook up (AADConnect) stopped functioning following set up of the updates on Server 2016 and 2012 R2 devices.
A user on the Inquire Woody forum explained the challenge in the pursuing way:
Even with the current patch on Server 2016 (KB4345418) is however creating an challenge with AADConnect servers that triggers a a hundred% CPU spike on some of the Overall health and Reporting checking companies, only fix at this place is to uninstall the most up-to-date update. It appears to affect at least 2012 and 2016 servers. …
A forum thread on the Microsoft Developer Network forum confirms the challenge. A person user claimed that uninstallation of KB4054566 fixed the challenge in a Home windows Server 2012 R2 surroundings.
Restarting the companies delivers CPU usage back again to normal, and the only alternative proper now to resolve it seems to be to uninstall the most up-to-date updates.
But concerns with AADConnect have been not the only kinds that directors claimed following release of the patches.
Matt Wilkinson claimed on Twitter that KB4345418 was creating black screen upon login concerns when employing Remote Desktop Products and services on Server 2016.
KB 4345418 is creating concerns on Server 2016 RDS with a black screen upon login. Have mitigated this challenge with a script to delete firewall procedures that are created for each user. Black screen returned with this update.
Closing Words and phrases
The July 2018 updates caused a whole lot of concerns for consumers up until eventually now. It is not the initially time that updates that Microsoft releases induce concerns on techniques they are put in on.
I believe it is fair to say that consumers want to understand that any patch that Microsoft releases can have unexpected repercussions some will even wreak the method. The generation of backups is encouraged.
Now You: Did you run into concerns following setting up patches just lately? (by way of Born)