October 11, 2022—KB5018427 (OS Build 22621.674)

For information about Windows update terminology, see the article about the types of Windows updates and the monthly quality update types. For an overview of Windows 11, version 22H2, see its update history page.NoteFollow @WindowsUpdate to find out when new content is published to the Windows release health dashboard.

Highlights

• It addresses security issues for your Windows operating system.

Improvements

This security update includes improvements that were a part of update KB5017389 (released September 30, 2022). Key changes in this release include:

• Microsoft is now compliant with US Government (USG) version 6 revision 1 (USGv6-r1).
  If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.For more information about security vulnerabilities, please refer to the Security Update Guide website and the October 2022 Security Updates.

Windows 11 servicing stack update - 22621.378

This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates.

Known issues in this update

1. Clocks will not be advanced by an hour at 12:00 a.m. on October 28, 2022 for the Jordan time zone.
2. 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 services which use date and time for integral functions, such as Microsoft Teams and Microsoft Outlook, notifications and scheduling of meetings might be 60 minutes off.

• Automation using date and time, such as Scheduled tasks, might not run at the expected time.

• Timestamp on transactions, files, and logs will be 60 minutes off.

• Operations that rely on time-dependent protocols such as Kerberos might cause authentication failures when attempting to logon or access resources.

• Windows devices and apps outside of Jordan might also be affected if they are connecting to servers or devices in Jordan or if they are scheduling or attending meetings taking place in Jordan from another location or time zone. Windows devices outside of Jordan should not use the workaround, as it would change their local time on the device.
  | This issue is addressed in KB5018496. 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 selectDate and time settings. From theDate & timesettings page, toggleAdjust for daylight saving time automaticallytoOff.

• Go toControl Panel> Clock and Region> Date and Time> Change time zoneand uncheck the option for “Automatically adjust clock for Daylight Saving Time”.Important: We recommend using ONLY the above workaround to mitigate the issue with time created by the new Daylight Savings Time in Jordan. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if done incorrectly.
  IT admins| 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 issue.| 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.
  IT admins| After you install this or later updates, you might be unable to reconnect to Direct Access after temporarily losing network connectivity or transitioning between Wi-Fi networks or access points.Note This issue should not affect other remote access solutions such as VPN (sometimes called Remote Access Server or RAS) and Always On VPN (AOVPN).Windows devices used at home by consumers or devices in organizations which are not using Direct Access to remotely access the organization’s network resourcesare not affected.| This issue is addressed in updates released December 13, 2022 (KB5021255) and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one. If you install an update released December 13, 2022 (KB5021255) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to address this issue. If you are using an update released before December 13, 2022, and have this issue, you can address it by installing and configuring the special Group Policy listed below.The special Group Policy can be found inComputer Configuration->Administrative Templates-><Group Policy name listed below>.For information on deploying and configuring these special Group Policy, please seeHow to use Group Policy to deploy a Known Issue Rollback.Group Policy downloads with Group Policy name:

• Download for Windows 11, version 22H2 - KB5018427 221029_091533 Known Issue Rollback * Download for Windows 11, version 21H2 -KB5018483 220927_043051 Known Issue Rollback * Download for Windows Server 2022 -KB5018485 220927_043049 Known Issue Rollback * Download for Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2 -KB5018482 220927_043047 Known Issue Rollback****Important You mustinstall andconfigure the Group Policy for your version of Windows to resolve this issue.
  All users| Certain applications might stop responding when you use keyboard shortcuts to turn on, turn off, or change the input mode of the Input Method Editor (IME).Examples of actions that might cause this issue:

• For Japanese:

  • Using the Hankaku/Zenkaku (半角 / 全角) key on a Japanese keyboard
  • Using the default keyboard shortcut: holding down the Alt key and pressing**~** (tilde)

• For Chinese:

  • Using the default keyboard shortcut: holding down the Control key and pressingSpace

• For Korean:

  • Using the default keyboard shortcut: pressing the right Alt key
    This issue is observed for applications that load certain components of the Text Services Framework (TSF). Applications that don’t load these components should not experience this issue.| This issue is addressed in KB5020044.
    IT admins| 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.| This issue is addressed in KB5018496. We recommend you install the latest security update for your device.NoteKB5018496 will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install.
    IT admins| You might have intermittent issues saving, copying, or attaching files using 32-bit apps, which are large address aware and using the CopyFile API. Windows devices are more likely to be affected by this issue when using some commercial or enterprise security software that uses extended file attributes. Microsoft Office apps, such as Microsoft Word or Microsoft Excel are only affected when using 32-bit versions and you might receive the error, "Document not saved."This issue is unlikely to be experienced by consumers using Windows devices in their home or on non-managed commercial devices. Apps are not affected by this issue if they are 64-bit or 32-bit and NOT large address aware.| This issue is addressed in KB5027231.

How to get this update

If you want to remove the LCUTo remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command:DISM /online /get-packages.Running Windows Update Standalone Installer (wusa.exe) with the**/uninstall **switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation.

File informationFor a list of the files that are provided in this update, download the file information for cumulative update 5018427. For a list of the files that are provided in the servicing stack update, download the file information for the SSU - version 22621.378.