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 1105 Media's Converge360 group.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube