Windows Server · 2022 · Release · Security update (Patch Tuesday)

October 11, 2022—KB5018421 (OS Build 20348.1129)

Windows Server 2022: Supported LTSC release

All 2022 builds JSON — this build from the builds API

Microsoft's known issues — KB5018421

  • Issue Known issue On October 5, 2022, the Jordanian government made an official announcement ending the winter-time Daylight Saving Time (DST) time zone change. Starting at 12:00 a.m. Friday, October 28, 2022, the official time will not advance by an hour and will permanently shift to the UTC + 3 time zone. The impact of this change is as follows: Clocks will not be advanced by an hour at 12:00 a.m. on October 28, 2022 for the Jordan time zone. The Jordan time zone will permanently shift to the UTC + 3 time zone. Symptoms if no update is installed and the workaround is not used on devices in the Jordan time zone on October 28, 2022 or later: Time shown in Windows and apps will not be correct. Apps and cloud s Workaround: This issue is addressed in KB5018485 . This update will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install. If you cannot install this update, you can mitigate this issue on devices in Jordan by doing either of the following on October 28, 2022: Select the Windows logo key , type "Date and time", and select Date and time settings . From the Date & time settings page, toggle Adjust for daylight saving time automatically to Off . Go to Control Panel > Clock and Region > Date and Time > Change time zone and uncheck the option for “Automatically adjust clock for Daylight Saving Time”. Important: We recommend using ON
  • Issue Known issue After this and later updates are installed, domain join operations might be unsuccessful and error "0xaac (2732): NERR_AccountReuseBlockedByPolicy" occurs. Additionally, text stating "An account with the same name exists in Active Directory. Re-using the account was blocked by security policy" might be displayed. Affected scenarios include some domain join or re-imaging operations where a computer account was created or pre-staged by a different identity than the identity used to join or re-join the computer to the domain. For more information about this issue, see KB5020276 - Netjoin: Domain join hardening changes . Note Consumer Desktop editions of Windows are unlikely to experience this i Workaround: We have added guidance to KB5020276 and are evaluating whether optimizations can be made in a future Windows Update. This guidance will be updated as soon as those changes are released.
  • Issue Known issue After installing this update, some types of SSL (Secure Sockets Layer) and TLS (Transport Layer Security) connections might have handshake failures. Note for developers The affected connections are likely to be sending multiple frames within a single input buffer, specifically one or more complete records with a partial record that is less than 5 bytes all sent in a single buffer. When this issue is encountered, your app will receive SEC_E_ILLEGAL_MESSAGE when the connection fails. Workaround: This issue is addressed in KB5020436 . We recommend you install the latest security update for your device. Note KB5020436 will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install.

Microsoft's release notes for KB5018421 ›

Known issues — reported on the forum

No problems reported on the forum for this build yet. Threads that name 20348.1129 or KB5018421 and describe a fault appear here automatically.

In the news

No article names 20348.1129 or KB5018421 yet, and nothing about Windows Server 2022 was published in its release window. Browse Windows news.

Discussed on the forum

Search the forum for 20348.1129 Ask about this build