News

Microsoft Addresses Botched .NET Framework Updates

Microsoft issued fixes to address problems with .NET Framework applications that were caused by July Windows patches.

Other Microsoft solutions had previously received fixed to address software regressions introduced by Microsoft's July 10 updates before the company last Friday announced the .NET Framework patches.

Microsoft's July 10 Windows patches have caused multiple problems for organizations using Microsoft software. Microsoft had earlier noted that the July 10 updates had caused problems for users of SQL Server, Skype and Exchange Server, and applications using .NET Framework.

Microsoft had released updates to fix SQL Server problems on July 16 and 18. It released updates to fix problems with Exchange Server, Lync Server 2013 and Skype for Business Server 2015 on July 17 and 18.

Microsoft offered slightly different patch advice to organizations dealing with the July 10 update issues, depending on their Windows Server product. Organizations using Windows Server 2016 that were affected will have the problematic patches KB 4338814 or KB 4338824 installed. Microsoft's solution is to install updated versions of those patches.

Organizations using Windows Server 2012 R2 that were affected by the Service Fabric problems will have the problematic patch KB 4338815 installed. Microsoft's advice to address this problem was a bit more nuanced:

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.

In other words, if an organization hadn't installed the problematic July 10 patch, then they'll have to install it and then update it.

Microsoft advised organizations with "very large clusters where upgrading each node is not an option" to contact Azure Support.

The updates with fixes for these problems also will be arriving later this month. Microsoft's monthly quality updates are "cumulative" updates, which means that they contain fixes for past months' releases. These updates arrive on the second Tuesday of each month. This month's "update Tuesday" event will happen on Aug. 14, and presumably these fixes will be included in the August update.

Microsoft recently described its monthly update process, and explained that it doesn't deliver new features with them.

About the Author

Kurt Mackie is senior news producer for the 1105 Enterprise Computing Group.

comments powered by Disqus

Featured

  • Visual Studio Code Dev Team Cleans Up

    The Visual Studio Code development team focused on some housekeeping in the October update, closing more than 4,000 issues on GitHub, where the cross-platform, open-source editor lives.

  • ML.NET Model Builder Update Boosts Image Classification

    Microsoft announced an update to the Model Builder component of its ML.NET machine learning framework, boosting image classification and adding "try your model" functionality for predictions with sample input.

  • How to Do Naive Bayes with Numeric Data Using C#

    Dr. James McCaffrey of Microsoft Research uses a full code sample and screenshots to demonstrate how to create a naive Bayes classification system when the predictor values are numeric, using the C# language without any special code libraries.

  • Vortex

    Open Source 'Infrastructure-as-Code' SDK Adds .NET Core Support for Working with Azure

    Pulumi, known for its "Infrastructure-as-Code" cloud development tooling, has added support for .NET Core, letting .NET-centric developers use C#, F# and VB.NET to create, deploy, and manage Azure infrastructure.

  • .NET Framework Not Forgotten: Repair Tool Updated

    Even though Microsoft's development focus has shifted to the open-source, cross-platform .NET Core initiative -- with the aging, traditional, Windows-only .NET Framework relegated primarily to fixes and maintenance such as quality and reliability improvements -- the latter is still getting some other attention, as exemplified in a repair tool update.

.NET Insight

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.

Upcoming Events