November 8, 2022—KB5019980 (OS Build 22621.819)

NEW 11/8/22
IMPORTANT Because of minimal operations during the holidays and the upcoming Western new year, there won’t be a non-security preview release for the month of December 2022. There will be a monthly security release (known as a “B” release) for December 2022. Normal monthly servicing for both B and non-security preview releases will resume in January 2023.

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 an issue that affects File Explorer. It fails to localize folders.
• It addresses security issues for your Windows operating system.

Improvements

This security update includes improvements that were a part of update KB5018496 (released October 25, 2022). When you install this KB:

• It addresses an issue that affects File Explorer. It fails to localize folders.
  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 November 2022 Security Updates.

Windows 11 servicing stack update - 22621.754

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

Applies to	Symptom	Workaround
IT admins	Using provisioning packages on Windows 11, version 22H2 (also called Windows 11 2022 Update) might not work as expected. Windows might only be partially configured, and the Out Of Box Experience might not finish or might restart unexpectedly. Provisioning packages are .PPKG files which are used to help configure new devices for use on business or school networks. Provisioning packages which are applied during initial setup are most likely to be impacted by this issue. For more information on provisioning packages, please see Provisioning packages for Windows. Note Provisioning Windows devices using Windows Autopilot is not affected by this issue.Windows devices used by consumers in their home or small offices are not likely to be affected by this issue.	This issue is addressed in KB5020044.
IT admins	Copying large multiple gigabyte (GB) files might take longer than expected to finish on Windows 11, version 22H2. You are more likely to experience this issue copying files to Windows 11, version 22H2 from a network share via Server Message Block (SMB) but local file copy might also be affected.Windows devices used by consumers in their home or small offices are not likely to be affected by this issue.	This issue is addressed in KB5022913.
IT admins	After installing updates released on November 8, 2022 or later on Windows Servers with the Domain Controller role, you might have issues with Kerberos authentication. This issue might affect any Kerberos authentication in your environment. Some scenarios that might be affected:

• Domain user sign in might fail. This also might affect Active Directory Federation Services (AD FS) authentication.
• Group Managed Service Accounts (gMSA) used for services such as Internet Information Services (IIS Web Server) might fail to authenticate.
• Remote Desktop connections using domain users might fail to connect.
• You might be unable to access shared folders on workstations and file shares on servers.
• Printing that requires domain user authentication might fail.
  When this issue is encountered you might receive a Microsoft-Windows-Kerberos-Key-Distribution-Center Event ID 14 error event in the System section of Event Log on your Domain Controller with the below text. Note: affected events will have “the missing key has an ID of 1”:`

While processing an AS request for target service <service>, the account <account name> did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 1). The requested etypes : 18 3. The accounts available etypes : 23 18 17. Changing or resetting the password of <account name> will generate a proper key.

`Note This issue is not an expected part of the security hardening for Netlogon and Kerberos starting with November 2022 security update. You will still need to follow the guidance in these articles even after this issue is resolved.Windows devices used at home by consumers or devices that are not part of a on-premises domain are not affected by this issue. Azure Active Directory environments that are not hybrid and do not have any on premises Active Directory servers are not affected.| This issue was addressed in out-of-band updates released November 17, 2022, for installation onallthe Domain Controllers (DCs) in your environment. You do not need to install any update or make any changes to other servers or client devices in your environment to resolve this issue. If you used any workaround or mitigations for this issue, they are no longer needed, and we recommend you remove them.To get the standalone package for these out-of-band updates, search for the KB number in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog.Note The below updates are not available from Windows Update and will not install automatically.Cumulative updates:

• Windows Server 2022: KB5021656

• Windows Server 2019: KB5021655

• Windows Server 2016: KB5021654
  Note You do not need to apply any previous update before installing these cumulative updates. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.Standalone Updates:

• Windows Server 2012 R2: KB5021653

• Windows Server 2012: KB5021652

• Windows Server 2008 R2 SP1: This update is not yet available. Please check here in the coming week for more information.

• Windows Server 2008 SP2: KB5021657
  Note If you are using security only updates for these versions of Windows Server, you only need to install these standalone updates for the month of November 2022. Security only updates are not cumulative, and you will also need to install all previous Security only updates to be fully up to date. Monthly rollup updates are cumulative and include security and all quality updates. If you are using Monthly rollup updates, you will need to install both the standalone updates listed above to resolve this issue, and install the Monthly rollups released November 8, 2022, to receive the quality updates for November 2022. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.
  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, apps that use ODBC connections utilizing the Microsoft ODBC SQL Server Driver (sqlsrv32.dll) to access databases might fail to connect. You might receive an error within the app or you might receive an error from SQL Server, such as “The EMS System encountered a problem” with “Message: [Microsoft][ODBC SQL Server Driver] Protocol error in TDS Stream” or “Message: [Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server”. Note for developers Apps affected by this issue might fail to fetch data, for example when using the SQLFetch function. This issue might occur when calling SQLBindCol function before SQLFetch or calling SQLGetData function after SQLFetch and when a value of 0 (zero) is given for the ‘BufferLength’ argument for fixed datatypes larger then 4 bytes (such as SQL_C_FLOAT).If you are unsure if you are using any affected apps, open any apps which use a database and then openCommand Prompt(select**Start then typecommand prompt **and select it) and type the following command: `

tasklist /m sqlsrv32.dll

`| This issue is addressed in KB5022303.

How to get this update

Before installing this updateMicrosoft combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.Install this update****Release Channel	Available	Next Step
Windows Update and Microsoft Update	Yes	None. This update will be downloaded and installed automatically from Windows Update.
Windows Update for Business	Yes	None. This update will be downloaded and installed automatically from Windows Update in accordance with configured policies.
Microsoft Update Catalog	Yes	To get the standalone package for this update, go to the Microsoft Update Catalog website.
Windows Server Update Services (WSUS)	Yes	This update will automatically sync with WSUS if you configure Products and Classifications as follows:Product: Windows 11Classification: Security Updates

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 5019980. For a list of the files that are provided in the servicing stack update, download the file information for the SSU - version 22621.754.