[German]Update KB4345418 (or the .NET-Framework 4.7.2 Update KB4054566) released on July 16, 2018 seems to cause serious issues at Windows Server 2012 R2 and Windows Server 2016. There are reports of high CPU load using AADConnect. Also RDS connections may cause issues.
Microsoft released a series of updates for Windows 10 on July 16, 2018, which are supposed to fix Bluescreens among other things (see my blog post Windows 10: Update revisions July 16, 2018). Also included was Update KB4345418 for Windows 10 V1607 (LTSB) and Windows Server 2016, which should fix the following bugs:
- Addresses an issue that may cause some devices running network monitoring workloads to receive the 0xD1 Stop error because of a race condition after installing the July update.
- Addresses an issue with the DHCP Failover server that may cause enterprise clients to receive an invalid configuration when requesting a new IP address. This results in a loss of connectivity.
Addresses an issue that may cause the restart of the SQL Server service to fail occasionally with the error, “Tcp port is already in use”.
Addresses an issue that occurs when an administrator tries to stop the World Wide Web Publishing Service (W3SVC). The W3SVC remains in a “stopping” state, but cannot fully stop or it cannot be restarted.
The fixed issues mentioned were ‘deadly’ in production environments. The update was distributed via Windows Update, but is also available in the Microsoft Update Catalog. Administrators should have this update installed promptly.
AADConnect doesn’t work anymore
However, administrators quickly recognized, that AADConnect (Microsoft Azure Active Directory Connect) no longer works after installing this update. Cryta T. Lacey (@PhantomofMobile) drew my attention to the issue via Twitter.
Azure AD Connect Health Sync Monitor High CPU Usage
Thank You: @SBSDiva
ICYMI: @SBSDiva @AdminKirsty @woodyleonhard @thurrott @maryjofoley @bdsams @mehedih_ @ruthm @etguenni @SwiftOnSecurity @pcper @SGgrc @MalwareJake @GossiTheDog @ryanshrout @JobCacka pic.twitter.com/KaDWuG0Ngg
— Crysta T. Lacey (@PhantomofMobile) 18. Juli 2018
Another users mentioned the issue at askwoody.com and posted the following description.
Just wanted to let you know of another issue that seems to be biting a lot of people with the July updates.
Even with the updated patch on Server 2016 (KB4345418) is still causing an issue with AADConnect servers that triggers a 100% CPU spike on some of the Health and Reporting monitoring services, only fix at this point is to uninstall the latest update. It seems to impact at least 2012 and 2016 servers. …
We just cancelled of our Windows patching for the month, hope MS gets this sorted out soon. What a mess.
The user linked to this MSDN forum thread, where you can find more information about the error.
Hello. I have Azure AD Connect installed on my server to sync our on-premise domain with Office 365 and I’m noticing the Azure AD Connect Health Sync Monitoring Service is always running high CPU usage. The actual process is
Is there a reason for this or a way to fix it? Right now, I’m just stopping the Azure AD Connect Health Sync Monitoring Service(AzureADConnectHealthSyncMonitor) and my resources go back to normal. I’m running Azure AD Connect 1.1.819.0 so it is the latest version. If I restart the service, things are normal for a few minutes before this process spikes again.
This results in a high CPU load, which is also confirmed by other users. This applies to Windows Server 2016, which was mentioned in the original post, as well as Windows Server 2012 R2.
A user reports in the thread to the above problem that he also had the problem on Windows Server 2012 R2, but was able to solve it by uninstalling the.NET framework 4.7.2 update KB4054566. Maybe this will help you.
Black screen with RDS connections
Matt Wilkinson has posted a Tweet mentions another issue caused by update KB4345418:
@woodyleonhard KB 4345418 is causing issues on Server 2016 RDS with a black screen upon login. Have mitigated this issue with a script to delete firewall rules that are created per user. Black screen returned with this update.
— Matt Wilkinson (@bigfoot780) 18. Juli 2018
However, he talks about issues with Remote Desktop Services (RDS). Windows Server 2016 shows a black screen when you connect via RDS. Anyone who can confirm these issues?
.Net Framework-Update KB4340558 fehlerhaft (Error 0x80092004)?
Windows 10 Version 1607: DHCP-Bug in Update KB4338814
KB4018385 zurückgezogen & weitere Patchday-Probleme
IIS-Webserver streikt nach Update KB4338818
Microsoft und das Juli 2018-Patch-Desaster – Updates stoppen?