The Windows 11 update you might need to uninstall

Although as a general rule, when talking about Windows 11 updates, mainly we tend to think about the big updates, like the still upcoming 22H1 and the future 22H2 Sun Valley 2, we are used to seeing many other “minor” updates in between. Either to solve a previously identified problem, to improve the performance of some function or even to modify some aspect of the operating system.

The problem with updates, both Windows 11 and other versions and other operating systems and applications, and this is not something new, is that sometimes they are not as polished as they should be or, in some cases, with some type of incompatibility that has not been detected in the testing phase. In this regard, it is true that the Windows Insiders program is of great help, since the testing field is extended by several orders of magnitude, but even so, on more than one occasion these gremlins that complicate everything.

Such is the case, as confirmed by the company itself, of the KB5012643 update. Perhaps, especially if you have a good numerical memory, it will be familiar to you, and we talked about it a week ago, more specifically about what solved a problem that caused Windows 11, in certain POS systems (point of sale terminal) could take up to 40 minutes to boot and restart. That was the lime one (or the sand one, I’ve never known which one is good and which one is bad), we found the sand one in this problem.

And it is that, as Microsoft has identified, Windows 11 with this update has compatibility issues with some components of the .NET Framework 3.5, and recommends that potentially affected users uninstall the update. Or, for those who prefer an alternative solution, Microsoft proposes to use the following commands in an open console with administrator permissions:

dism /online /enable-feature /featurename:netfx3 /all
dism /online /enable-feature /featurename:WCF-HTTP-Activation
dism /online /enable-feature /featurename:WCF-NonHTTP-Activation

At the moment there is no patch or update that solves this problembut given this manual option to reactivate the failing .NET Framework elements with this Windows 11 update, it seems quite likely that we won’t need to wait too long for a definitive fix.

The problem is that the vast majority of users do not know what common elements, such as these functions of the Microsoft framework, are used by the applications they use on their PC, so they don’t know if they are affected by this Windows 11 update. Microsoft claims that this issue will cause those apps to work erratically or at all. Thus, if you are a Windows 11 user, you have applied that update to your system and some application has stopped working, try uninstalling the update to verify if it is for that reason.