Microsoft Februar 2022 Patch day review

[German]February 8, 2022 was Microsoft's patchday, where a number of security updates for various products were made available. I had reported about these updates in the blog. At first glance, there was little trouble with the February 2022 updates. But some collateral damage came to my attention, which I'll summarize in a review.

Issues with shares from NFS devices

The updates for Windows/Windows Server fix an information disclosure vulnerability in the network area (see CVE-2022-21993: Windows Services for NFS ONCRPC XDR Driver Information Disclosure Vulnerability). The patch can cause problems with shares on third-party devices that support the Network File System (NFS). Blog reader Chris reached out in this German comment and writes:

Attention. This update appears to have negative effects on non-Microsoft network services. In our case it has reproducibly caused problems with NFS shares. The ports are then "deaf" from the outside, although they should be reachable according to Netstat and firewall. After removing KB5010342 everything works again…

German blog reader Rene confirms this in a follow up comment, because their ESXi instances do not mount the NFS of the Veeam B&R with its PowerNFS after the Veeam Master was patched. Veeam is installed in version 11a. The whole thing refers to Windows Server 2012 R2.

Printer issues after patchday

In a private group for server administrators, someone reported that on their Windows Server 2008 R2, which is in use as a print server, the printers had disappeared after the update installation.

It says that a Microsoft Windows Server 2008 R2 used as a print server lost it's network printers after installing the Feb. 2022 update. German blog reader Dominik reported in this comment to the German article Windows 7/Server 2008R2; Windows 8.1/Server 2012R2: Updates (8. Februar 2022), that the SSU is always offered to him again after installation – he has to hide it. Blog reader Alex also complains about problems with the network printer in this comment.

Interesting, but with last Win10 Feb. 2022 patchday Microsoft has again caused us problem with network printer.

[…]

Our Win10 21H2 PC with Feb. 2022 patch installed again require admin rights when installing network printer driver.

And as of Feb 9, 2022, TheInspector has reported here error 0x0000011b on Windows 10 20H2 clients.

KB5010359 causes error 0x8024001E

Another message in a private administrators group on Facebook reports that update KB5010359 causes installation error 0x8024001E on a Windows Server 2016 and aborts. On Technet, there is this German forum post that could be from the same poster. A comment on Facebook might be missing the latest Servicing Stack update, but the thread creator denies that.

It is helpful to look at the explanation of the error code. In the blog post Windows 10: Update errors 0x8024xxxx detailed I have pulled out the details of this error:

0x8024001E WU_E_SERVICE_STOP Operation did not complete because the service or system was being shut down.

The transaction in question could not complete because the service or system was being shut down. The question remains, what causes this problem, because a shutdown of the server is probably rather excluded in the above case.

My blog post Windows Update Error 0x8024001E sheds some lights to a root cause. Possibly a setting in Internet Explorer (folder Temporary Internet Files undefined or permission conflicts) plays a role.

The person concerned has responded on Facebook to my tip to check the settings for the temporary Internet folder in Internet Explorer.

Dear Günter, thank you for your tip. I had already found and read that, but had paid too little attention to the IE settings. The folder specified in IE was present. Then I moved it to C:\Windows\Temp and after that I could really install the update. Thanks.

So it worked again. If permission problems when accessing the temporary folder of Internet Explorer play into it, the download does not seem to be executed successfully and there is the abort with the error code 0x8024001E. Since Internet Explorer will be replaced by Edge in the future, this could happen even more frequently.

Boot error 0xc0000185 with Windows 10

In a private message I got a report of a no longer booting ASUS notebook – the notebook was in a BlueScreen in the morning. Because of the temporal proximity and Windows 10, an accidental update is obvious.

When repairing the startup settings, error 0xc0000185 is reported, which is an indication of corrupted startup files. I had suggested a repair in German blog post Reparatur in Windows RE (or within Windows 10/Microsoft Surface: Boot error 0xc0000098). And I posted a link to this article to repair this issue. At the end of the day, booting the system with a Windows 10 installation stick, going into Computer Repair Options, letting the system repair automatically, and then still running chkdsk /r at the command prompt helped.

Access problems after Feb. 2022 updates

With the Feb. 1, 2022 update, Microsoft also addressed problems with Microsoft Access – where multiple users have not been able to work with an Access database since December 2021. There are isolated problems here, as a result of the February 2022 update, which can be found in the comments to theGerman  blog post Microsoft Office Updates (1. Februar 2022) korrigieren Access-Probleme. In a nutshell, the issues are still there.

Similar articles:
Microsoft Office Updates (February 1, 2022) fixes Access issues
Microsoft Security Update Summary (February 8, 2022)
Patchday: Windows 10 Updates (February 8, 2022)
Patchday: Windows 11/Server 2022 Updates (February 8, 2022)
Patchday: Microsoft Office Updates (February 8, 2022)