{"id":28384,"date":"2023-01-12T13:19:38","date_gmt":"2023-01-12T12:19:38","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=28384"},"modified":"2023-01-13T10:41:02","modified_gmt":"2023-01-13T09:41:02","slug":"windows-january-2023-patchday-issues","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2023\/01\/12\/windows-january-2023-patchday-issues\/","title":{"rendered":"Windows January 2023 patchday issues"},"content":{"rendered":"

\"Windows\"[German<\/a>]The security updates released by Microsoft on January 10, 2023 for the various Windows versions (clients, servers) do close some critical vulnerabilities. However, there are a number of user messages that report installation problems. In addition, it looks like the fixed bugs like ODBC connection errors on SQL databases are not fixed for all users.<\/p>\n

<\/p>\n

Windows Patchday January 2023<\/h2>\n

\"\"As of of January 10, 2023, Microsoft has released security updates for the various Windows versions (clients, servers) that are also intended to close vulnerabilities that are considered critical. I provide an overview of the most critical vulnerabilities in the blog post Microsoft Security Update Summary (January 10, 2023)<\/a> and in the blog posts about Windows update linked at the end of the article.<\/p>\n

ODBC driver SQL connection error<\/h2>\n

In all security updates, Microsoft states that the, already confirmed (see Windows: November 2022 updates cause ODBC connection problems with SQL databases<\/a>), ODBC-SQL database connection bug should be fixed:<\/p>\n

This update addresses a known issue that affects apps that use Microsoft Open Database Connectivity (ODBC) SQL Server Driver (sqlsrv32.dll<\/b>) to connect to databases. The connection might fail. You might also receive an error in the app, or you might receive an error from the SQL Server.<\/p><\/blockquote>\n

In this German comment<\/a> a blog reader reported that this error still occurs with him. Unfortunately, there is no response to the question about details and whether the replacement of the driver (see Windows: Microsoft Workaround for ODBC SQL connection issues (Jan. 5, 2023)<\/a>) helps. Anyone else who hasn't had the ODBC problems fixed?<\/p>\n

In a\u00a0second comment<\/a> German blog reader Eiko also reported issues with SQL Server (2017) on Windows Server 2012\u00a0 in connection with update KB5022348:<\/p>\n

I have here two servers 2012, one runs the SQL server and on the other the application that uses the SQL. Since the update (KB5022348) the connection to the SQL server does not work and the application reports SSL errors when connecting. I'll see if it works again when I uninstall the update.<\/p><\/blockquote>\n

So far there is no feedback if the uninstallation helped.<\/p>\n

Is the BlueScreen 0xc000021a fixed?<\/h2>\n

The December 2022 security updates could cause a BlueScreen (Stop error) on Windows systems. Microsoft had confirmed the BlueScreen bug in Dec 2022 for Windows 10 20H2-22H2 (see Windows 10 20H2-22H2: Update KB5021233 from 13. Dec. 2022 causes BlueScreen<\/a>). Within the blog post a workaround to fix the BSOD is given. However, it seems to have hit Windows 11 as well, as the colleagues from Bleeping Computer write here<\/a>.<\/p>\n

Microsoft claims to have fixed BSOD<\/h3>\n

In this German comment<\/a> and here<\/a> reader Birgit asks if the bluescreen problem (from the December 2022 Windows Cumulative Update) is now fixed with the January patch. In the update description for Windows 10, Microsoft states:<\/p>\n

This update addresses a known issue that might affect startup on some Windows devices. They might receive an error (0xc000021a) and have a blue screen.<\/p><\/blockquote>\n

So they have been working on this problem and believe they have solved it.<\/p>\n

0xc000021a on Windows Server 2016<\/h3>\n

However, there are some voices that still complain about a stop error 0xc000021a. On German site administrator.de there is the thread WS 2016 BSOD 0xc000021a nach Security Update<\/a>, where someone reports the stop error for Windows Server 2016.<\/p>\n

An old known BSOD is back again.
\nI have 3 (Exchange) servers. (Exchange does not matter here).
\n2 of them were successfully installed with the 2022-12 Windows Updates.
\none has a BSOD after the update.<\/p>\n

[…]<\/p>\n

Each time the same thing.
\nInstallation goes through without a problem.
\nwhen shutting down he installs yes still one or the other.
\nAs soon as he \"really\" restarts, the server no longer comes up. BSOD.<\/p><\/blockquote>\n

But since it is Windows Server 2016, there could be another cause, because the support article of update KB5022289<\/a> does not mention the fix for the stop code 0xc000021a. The measures mentioned in the German Windows FAQ<\/a> do not help either.<\/p>\n

Installation errors<\/h2>\n

Furthermore, some people report that updates cannot install and a rollback occurs.<\/p>\n

Windows 10 Update KB5022282<\/h3>\n

On Facebook, there is a German comment<\/a> on my article\u00a0Patchday: Windows 10-Updates (10. Januar 2023)<\/a> reporting an installation error in 22H2 (translated):<\/p>\n

The update KB5022282 fails for me. Error code: 0x80073701.<\/p>\n

3 attempts, failed 3 times. Anyone else having problems with this? What can be done?<\/p><\/blockquote>\n

The usual approaches with dism \/online \/cleanup-image \/startcomponentcleanup<\/em>, download and manual installation also failed. Statement:<\/p>\n

Downloaded manually and tried to install. After reaching 100% terse error message \"The update was not installed.\"<\/p>\n

Tried sfc \/scannow, finds no errors.<\/p>\n

Event Viewer reports \"Package KB5022282 failed to be changed to the Installed state. Status: 0x80073701.2\"<\/p><\/blockquote>\n

My question about what is in the CBS.log was answered as follows:<\/p>\n

There are very, very many error messages in the CBS. Example:<\/p>\n

\"Extraction of file: update.ses failed because it is not present in the container\".<\/p>\n

To put it mildly, the update archive is not complete.<\/p>\n

When installing it is noticeable, it goes to 10%, then to 20%, then to 44% and then very quickly to 100%, as if something is missing. After that the error message. But that does not have to mean anything, are often such jumps in the installation progress in it.<\/p><\/blockquote>\n

There is a similar report<\/a> in German Windows 10 forum. The user contacted me again on Facebook and writes:<\/p>\n

I have uninstalled KB5021233 and reinstalled it via the update catalog. This is a problem update that sometimes led to a BSOD. Whether this update was changed afterwards, I can not say. In any case, I did not have a new BSOD. But the crucial thing: Afterwards KB5022282 could be installed without any problems.<\/p>\n

If someone else has the problem, this is probably a workaround.<\/p><\/blockquote>\n

At this point thanks to the reader for the hint – maybe it helps.<\/p>\n

Windows Module Installer Worker error<\/h3>\n

A German comment<\/a> addresses another issue with the update KB5022282 with the Windows Module Installer Worker error.<\/p>\n

Windows Modules Installer Worker<\/p>\n

The update to 19045.2486 (KB5022282) went smoothly, but logged \"Windows Error Reporting\" EventID 1001<\/p>\n

Windows Modules Installer Worker<\/p>\n

INVALID REQUEST
\n0
\nWindowsServicingFailureInfo
\nNot available
\n0
\n10.0.19041.2300:1
\n0x800F0984 0x800F0984 Matching binary: LxssManager.dll missing for component: amd64_microsoft-windows-lxss-manager_31bf3856ad364e35_10.0.19041.2486_none_f31086c4800002aa
\nP3: \u6946\u656c\u203a\u7473\u726f\u6c65\u7961\u756f\u2e74\u7063\u2870\u3631\u3439
\n\u202d\u6f43\u706d\u6e6f\u6e65\u5374\u6f74\u6572\u3a3a\u5243\u7761\u7453\u726f\u4c65\u7961\u756f\u3a74\u483a\u6479\u6172\u6574\u6946\u656c\u7355\u6e69\u4667\u726f\u6177\u6472\u6e41\u5264\u7665\u7265\u6573\u6544\u746c\u7361<\/p><\/blockquote>\n

There is this German comment<\/a> by DK2000 on German site deskmodder.de with some explanations. Here's my translation:<\/p>\n

The error only says that a LxssManager.dll was found, but not the version that was expected (PSFX_E_MATCHING_BINARY_MISSING). In any case, everything seems to have been installed correctly [at my system].<\/p>\n

And why there is a part in Chinese, I don't know. Google seems to have problems translating it (\"Destroy the soup, but keep tapping, shaving and sleeping.\"). Do not think that the translation fits so.<\/p><\/blockquote>\n

Windows Server 2022 Update KB5021249<\/h3>\n

German blog reader Christian reported in this ccomment<\/a> install issues since December 2022 with cumulative updates (since KB5021249) on Windows Server 2022 running in Hyper-V VMs, if the VMs has been installed with a SYSPREP image. The installation aborts with the download error 0x800f081f. The error 0x800f081f indicates a problem in the Windows Update Manager. Often important update files are missing. He linked to this reddit.com post<\/a> where something similar is described for the cumulative update KB5021249 from January 2023.<\/p>\n

Windows Server 2012 R2 Update KB5022352 hangs<\/h3>\n

Update KB5022352 for Windows 8.1 as well as Windows Server 2012 R2 seems to have installation problems, which are described e.g. in this comment<\/a>.<\/p>\n

Does anyone else have the problem that kb 5022352 hangs at 95% download?
\nThis is what happened on 2 servers for me.<\/p>\n

I am now trying the manual method….<\/p><\/blockquote>\n

This is confirmed in this German comment<\/a>. In this German comment<\/a>, blog reader Larsen also reports that update KB5022352<\/a> for Windows Server 2012 R2 would not install and hung:<\/p>\n

2012R2: Download hangs at 95% at first. After restarting and retrying, error 80070570 occurred on two servers running 2012R2 (one as a VM, one still physical).<\/p><\/blockquote>\n

In this case it helped to download the update KB5018922<\/a> from the Microsoft Update Catalog and then to install the SSU KB5018922<\/a> and afterwards the update KB5022352<\/a> in the mentioned order.<\/p>\n

In this German comment<\/a> there is a note that the package may be corrupted on the Microsoft servers (CRC error on WSUS download). The reader has described a workaround (reject update, run server cleanup, reapprove update). Also described here<\/a> is an approach for Windows Server 2012 R2 by deleting the folder:<\/p>\n

Windows\\SoftwareDistribution<\/em><\/p>\n

Maybe it helps. Addenum:<\/strong> Within my German blog Dave reported,<\/a> that they was affected on 108 servers. They used the following solution (with a script):<\/p>\n

1. cancel installation
\n2. use sfc \/scannow
\n3. delete everything in the directory C:\\Windows\\SoftwareDistribution\\Download<\/em>
\n4. restart
\n5. start installation and now it should run.<\/p>\n

No other TMP directories needed to be deleted. Hope it helps affected administrators.<\/p>\n

KB5022352 throws download error 0x8024002<\/h3>\n

In this comment<\/a>, someone is also reporting installation problems on Windows Server 2012 R2 and writes:<\/p>\n

I'm facing errors (0x80240022) while trying to download updates for Windows 2012 R2 servers. I have SSU KB5018922 all over the place and still can't patch any of Windows 2012\/R2 servers.<\/p><\/blockquote>\n

The error code 0x80240022 is generic and stands for WU_E_ALL_UPDATES_FAILED, Operation failed for all the updates (see Windows 10: Update errors 0x8024xxxx detailed<\/a>). I had addressed the 2016 error code in the German blog post Windows Update-Fehler 0x80240022 (Defender)<\/a> related to Defender. The explanation may be helpful, as the code states that the updates failed to load.<\/p>\n

A possible causes are a missing system file, an incorrect system setting (e.g. date, time zone, time) or a problem with a registry file. So check time zones, date and time – if necessary exclude a mobile connection (metered connection) for the update download on notebooks. But this will probably not apply to the server.<\/p>\n

During a search, however, I often found Defender (or Microsoft Security Essentials) to be the cause (see also here<\/a>, although the reference to the repair tool should be ignored if possible). If Windows Defender (or a third-party antivirus solution) can be ruled out as the cause (disable it if necessary, see also e.g. the German Windows FAQ<\/a>), I would try to check the system for damaged files via sfc and dism (see Check and repair Windows system files and component store<\/a>).<\/p>\n

Furthermore, resetting Windows Update would be an option – see also my German blog post WUReset zum Zur\u00fccksetzen von Windows Update<\/a> and the blog posts linked there. Otherwise, evaluate in the CBS.log<\/em> in the Windows folder and in the Event Viewer, hoping that there is something to find.<\/p>\n

Similar articles:<\/strong>
\nMicrosoft Office Updates (January 3, 2022)<\/a>
\nMicrosoft Security Update Summary (January 10, 2023)<\/a>
\nPatchday: Windows 10 Updates (January 10, 2023)<\/a>
\nPatchday: Windows 11\/Server 2022 Updates (January 10, 2023)<\/a>
\nWindows 7\/Server 2008 R2; Windows 8.1\/Server 2012 R2: Updates (January 10, 2023)<\/a>
\nPatchday: Microsoft Office Updates (January 10, 2023)<\/a>
\nExchange Server Security Updates (January 10, 2023)<\/a>
\nMicrosoft Exchange January 2023 patchday issues<\/a>
\nWindows: November 2022 updates cause ODBC connection problems with SQL databases<\/a>
\nWindows: Microsoft Workaround for ODBC SQL connection issues (Jan. 5, 2023)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]The security updates released by Microsoft on January 10, 2023 for the various Windows versions (clients, servers) do close some critical vulnerabilities. However, there are a number of user messages that report installation problems. In addition, it looks like the … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,580,22,2],"tags":[166,2765,195,194],"class_list":["post-28384","post","type-post","status-publish","format-standard","hentry","category-issue","category-security","category-update","category-windows","tag-issues","tag-patchday-1-2023","tag-update","tag-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/28384","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=28384"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/28384\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=28384"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=28384"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=28384"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}