Movatterモバイル変換

Applies To

Windows 10

Release Date:

11/8/2022

Version:

OS Build 10240.19567

EXPIRATION NOTICE

IMPORTANT As of January 27, 2026, this update is no longer available from the Microsoft Update Catalog or other release channels. We recommend that you update your devices to the latest version of Windows.

^12/8/20For information about Windows update terminology, see the article about the types of Windows updates and themonthly quality update types. For an overview of Windows 10, version 1507, see its update history page.

Highlights

It stops the start of daylight saving time in Jordan at the end of October 2022. The Jordan time zone will permanently shift to the UTC + 3 time zone.
It addresses security issues for your Windows operating system.

Improvements

This security update includes quality improvements. When you install this KB:

It addresses an issue that affects Distributed Component Object Model (DCOM) authentication hardening. We will automatically raise the authentication level for all non-anonymous activation requests from DCOM clients to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY. This occurs if the authentication level is below Packet Integrity.
It stops the start of daylight saving time in Jordan at the end of October 2022. The Jordan time zone will permanently shift to the UTC + 3 time zone.
It addresses an issue that affects the Microsoft Azure Active Directory (AAD) Application Proxy connector. It cannot retrieve a Kerberos ticket on behalf of the user. The error message is, “The handle specified is invalid (0x80090301).”

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 newSecurity Update Guide website and theNovember 2022 Security Updates.

Known issues in this update

Symptom	Workaround
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 affectActive Directory Federation Services (AD FS) authentication. Group Managed Service Accounts (gMSA) used for services such asInternet 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 thesecurity 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 onall the 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 theMicrosoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, seeWSUS and the Catalog Site. For Configuration Manger instructions, seeImport 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.
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 theSQLFetch function. This issue might occur when callingSQLBindCol function before SQLFetch or callingSQLGetData 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 (selectStartthen typecommand promptand select it) and type the following command: `tasklist /m sqlsrv32.dll`	This issue is addressed inKB5022297.

Symptom

Workaround

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 affectActive Directory Federation Services (AD FS) authentication.
Group Managed Service Accounts (gMSA) used for services such asInternet 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 thesecurity 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 onall the 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 theMicrosoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, seeWSUS and the Catalog Site. For Configuration Manger instructions, seeImport 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.

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 theSQLFetch function. This issue might occur when callingSQLBindCol function before SQLFetch or callingSQLGetData 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 (selectStartthen typecommand promptand select it) and type the following command:

tasklist /m sqlsrv32.dll

This issue is addressed inKB5022297.