After we began this month of patching, I totally anticipated to return again by now with huge listings of functions that hated the February updates. That hasn’t been the case, although there have been some points associated to .NET this month.
In case you are questioning, .NET is a framework utilized by builders to construct functions. It makes for normal coding methods and “managed code” and might make an app safer. Builders primarily use Visual studio to develop software program that all of us use on our Home windows methods.
Recognized points affecting Visual Studio most dramatically appeared in updates first launched with the cumulative .NET updates starting final month. KB4598301 was launched Jan. 26 as an non-compulsory preview replace for .NET on Home windows 10 1909 and brought on Visible Studio to crash. Then KB4601056, launched Feb. 9, suffered from the identical concern. So Microsoft launched a preview replace per week later — KB4601556 — that fastened the underlying concern in Win10 1909.
The Patch Tuesday launch of KB4601887 for Home windows 10 1809 was later fastened by KB4602298, although not for all platforms. For instance, the launch of KB4601050 for Home windows 2004/20H2, KB4601054 for Win10 1803, and KB4601051 for Win10 1607 have been not fastened with later releases. I anticipate that for these platforms you’ll have to attend till the March updates arrive if you’re seeing utility crashes.
In any other case, I’ve been stunned by how few stories of points I’ve seen after these updates have been put in. In my very own private testing, I’ve not seen points — although there have been stories of issues from different customers. One report includes Autodesk’s Inventor 2020 and 2021, which crashes with these updates put in. However utility crashes have been few and much between; thus, I don’t anticipate you should have points this month.
One other report I’ve seen comes from the VMware forum, the place this patch was put in on Server 2016 deployments and blocked the power to totally enroll iOS units with Clever Hub 21.01. Because the VMware information base notes, a number of .NET updates launched in February trigger points with Workspace ONE UEM performance together with safe channel communication.
As famous on the VMware web page, all the following .NET patches set off this concern:
I personally haven’t seen any impression on considered one of my key functions constructed on .NET: Intuit’s QuickBooks. Neither the 2018, 2019, 202,zero or the 2021 variations of QuickBooks have had points.
The excellent news is that the safety concern fastened in these patches merely blocks an attacker from performing a denial of service. Sarcastically, because the patch makes the appliance crash, it successfully causes the identical factor it’s making an attempt to guard customers from. If you happen to should take away this replace, I don’t see it as a excessive threat if you happen to can’t set up it right now.
As a result of I haven’t seen many reported unintended effects (together with in my very own testing), subsequent week I’ll be recommending you put in the updates the Feb. 9 batch of patches except you’re instantly impacted by the .NET replace. Based mostly on my overview of the patch boards and venues, I’ve solely seen unintended effects with sure enterprise apps. The problems have been slim and never vast unfold. That’s the excellent news.
If you happen to discover you do must uninstall the replace, you’ll face a two step course of. First, go to Begin button, then Settings, then Replace and safety. Click on on view replace historical past after which on “Uninstall updates.”
MicrosoftScroll down and discover the Replace for Microsoft Home windows with the matching KB quantity that corresponds with the model of Home windows 10, eight or 7 you’ve got. For Home windows 10, for instance, you’ll must search for one of many following:
- Home windows 10 model 1607 – KB4601051
- Home windows 10 model 1809 – KB4601887
- Home windows 10 model 1909 – KB4601056
- Home windows 10 model 2004 or 20H2 – KB4601050
Now comes the more durable half: Particularly for Home windows 10, you’ll want to make sure that you set your system so it is not going to reinstall this replace you probably have been impacted. First, obtain the WUSHOWHIDE.DIAG device from Oldergeeks.com and set up it. (As it’s possible you’ll recall from my last blog post, this device is not accessible from Microsoft.) Now, search for the replace you want to cover or block from putting in and choose it.
WushowhideClick on on present or cover updates after which choose to cover the .NET replace and click on subsequent.
WushowhideThe appliance will point out that utility is “resolving” issues and can cover the replace from being supplied as much as your system. Another device is Windows Update Minitool, which lets you cover updates as effectively.
For a few years I have been cautious of .NET updates and would cringe after they have been launched. There have been a few years we’d have to make use of varied .NET repair instruments to uninstall and reinstall .NET. Since Microsoft launched .NET 4.eight and later, and included it in Home windows 10, it is develop into a lot better behaved — that means now we have not wanted to uninstall and manually reinstall .NET. This is likely one of the first occasions I can recall {that a} .NET replace has gone out with a identified concern in an extended whereas.
Backside line, the large patching concern I assumed would happen has been remoted. Fortunately, this time .NET has been typically effectively behaved; it hasn’t (but) brought on me to wince and cringe.
