Microsoft on Friday released fixes for addressing problems with the applications with .NET framework. The .NET framework was possibly last of the software giant’s solutions to have been updated for addressing software regressions which were introduced by July 10 updates of Microsoft.
Organizations have reported various problems with Microsoft’s update of July 10th. The company had previously noted that July 10 updates had caused issues for users of Skype and Exchange Server, SQL Server, and applications using .NET framework. Updates to fixes for SQL Server problems had been released on July 16th and 18th while on July 17th and 18th, updates to fixes for issues with Lync Server 2013, Exchange Server and Skype for Business Server 2015 were released.
For organizations, the patch advice offered by Microsoft was slightly different depending on their respective Windows Server product. Organizations with Windows Server 2016 that had issues with July 10th update shall have KB 4338814 or KB 4338824 installed.
According to Microsoft Blog, “For cluster running on Windows Server 2016 – the fix is a replacement to the July 10th version update, so installing the latest version should mitigate the problem. If your cluster is running the Patch Orchestration Application (POA), the POA may have updated your cluster. Please confirm that the OS is not running the impact KB (Knowledge Base ID) as shown below.”
On the contrary, organizations using Windows Server 2012 R2 will have problematic patch KB 4338815 installed. According to Microsoft Blog, “For clusters running on Windows Server 2012R2 – the fix is an additional upgrade on top of the version released in July. This means that if the nodes were not updated since before July 10th, you may need to apply the July 10th update first and then execute the Windows update again to resolve the problem.”
This means that if an organization had not installed the faulty July 10th patch, they will then have to install and update it. Those organizations which have large clusters where upgrading each node was not exactly an option were advised to contact Azure support.
Updates to the fixes for this issue will arrive later, most probably in the scheduled 14th August update, the second Tuesday of the month.