The .NET patch failing that wasn’t
This 30 days of patching whenever we started, The February updates i fully likely to come back right now with huge listings of applications that hated. That was not the case, though there were some presssing issues linked to .This month net.
In the event you’re wondering, .Internet is really a framework utilized by developers to create applications. It creates for standard coding strategies and “managed code” and will make an app better. Developers primarily use Visual studio to build up software that people all use upon our Windows systems.
Known issues affecting Visual Studio most dramatically appeared in updates first introduced with the cumulative .Month net updates beginning last. KB4598301 premiered Jan. 26 being an optional preview update for .NET on Windows 10 1909 and triggered Visual Studio to crash. Then KB4601056, released Feb. 9, experienced the same issue. Seven days later –   so Microsoft released a preview update;KB4601556 – that set the underlying issue in Win10 1909.
The Patch Tuesday release of KB4601887 for Windows 10 1809 was later fixed by KB4602298, though not for several platforms. For instance, the release of KB4601050 for Windows 2004/20H2, KB4601054 for Win10 1803, and KB4601051 for Win10 1607 were not fixed with later releases. I expect that for these platforms you’ll need to wait before March updates arrive if you’re seeing application crashes.
Otherwise, I’ve been surprised by how few reports of issues I’ve seen after these updates were installed. Within my personal testing, I have not seen issues though there have been reports of problems from other users -. One report involves Autodesk’s Inventor 2020 and 2021, which crashes with these updates installed. But application crashes have already been few and between far; thus, This month i don’t anticipate you should have issues.
Another report I’ve seen originates from the VMware forum, where this patch was installed on Server 2016 deployments and blocked the capability to fully enroll iOS devices with Intelligent Hub 21.01. Because the VMware knowledge base notes, several .NET updates released in February cause problems with Workspace ONE UEM functionality including secure channel communication.
As noted on the VMware page, every one of the following .NET patches trigger this matter:
I personally haven’t seen any effect on among my key applications built on .NET: Intuit’s QuickBooks. Neither the 2018, 2019, 202,0 or the 2021 versions of QuickBooks experienced issues.
The very good news is that the security issue fixed in these patches merely blocks an attacker from performing a denial of service. Ironically, because the application crash is manufactured by the patch, it effectively causes a similar thing it’s attempting to protect users from. If this update should be removed by you, I don’t view it as a higher risk in the event that you can’t install it as of this right time.
Because I haven’t seen many reported unwanted effects (including in my testing), week I’ll be recommending you install the updates the Feb next. 9 batch of patches unless you’re directly influenced by the .NET update. Predicated on my overview of the patch venues and forums, I’ve only seen unwanted effects with certain business apps. The presssing issues have already been narrow and not endemic. That’s the good thing.
If you’re found by you do have to uninstall the update, you’ll face a two step process. First, head to Start button, settings then, update and security then. Select view update history and on “Uninstall updates.”
Scroll down and discover the Update for Microsoft Windows with the matching KB number that corresponds with the version of Windows 10, 8 or 7 you have. For Windows 10, for instance, you’ll need to search for among the following:
- Windows 10 version 1607 – KB4601051
- Windows 10 version 1809 – KB4601887
- Windows 10 version 1909 – KB4601056
- Windows 10 version 2004 or 20H2 – KB4601050
Now comes the harder part: Specifically for Windows 10, you’ll must ensure that you set one’s body so it won’t reinstall this update when you have been impacted. First, download the WUSHOWHIDE.DIAG tool from Oldergeeks.com and set it up. (Because you can recall from my last blog post, this tool is longer available from Microsoft no.) Now, search for the update you intend to hide or block from installing and choose it.
Select show or hide updates and choose to cover up the then .NET update and click next.
The application form will indicate that application is “resolving” problems and can hide the update from on offer up to one’s body. An alternative solution tool is Windows Update Minitool, that allows one to hide updates aswell.
For many years I am cautious with .NET updates and would cringe if they were released. There have been many years need to use various we’d .NET repair tools to uninstall and reinstall .NET. Since Microsoft released .NET 4.8 and later, and included it in Windows 10, it’s become far better behaved – meaning we’ve unnecessary to uninstall and manually reinstall .NET. That is among the first times I could recall a .NET update went out with a known issue in an extended while.
Important thing, the big patching issue I thought would occur has been isolated. Thankfully, this right time .NET has been well behaved generally; it hasn’t (however) caused me to wince and cringe.