November 8, 2022—KB5020023 (Monthly Rollup)

Symptom

Next step

After this update or a later Windows update is 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.

This issue is resolved in KB5023765.

After installing Windows updates released on or after November 8, 2022 on Windows Servers that use the Domain Controller role, you might have issues with Kerberos authentication. This issue might affect any Kerberos authentication in your environment. Some scenarios which might be affected:

• Domain user sign in might fail. This might also 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 4 error event in the System section of the event log on your Domain Controller with the below text.

Note Affected events will contain "the missing key has an ID of 1" string:

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 have to follow the guidance in these articles even after this issue is resolved.

Windows devices used at home by consumers or devices which are not part of an on-premises domain are not affected by this issue. Azure Active Directory environments that are not hybrid and have no on-premises Active Directory servers are not affected.

This issue is addressed in update KB5021653.

After installing this update or a later update on a domain controller (DC), you might experience a memory leak with the Local Security Authority Subsystem Service (LSASS,exe). Depending on the workload of your DC and the amount of time since the last restart of the server, LSASS might continually increase memory usage with the up time of the server and the server might become unresponsive or automatically restart.

Note The out-of-band updates for DCs released November 17, 2022 and November 18, 2022 might be affected by this issue.

To mitigate this issue, open a Command Prompt as an Administrator and use the following command to set the registry key KrbtgtFullPacSignature to 0:

reg add "HKLM\System\CurrentControlSet\services\KDC" -v "KrbtgtFullPacSignature" -d 0 -t REG_DWORD

Note After this known issue is resolved, you should set KrbtgtFullPacSignature to a higher setting, depending on what your environment will allow. We recommend that you enable Enforcement mode as soon as your environment is ready.

For more information about this registry key, please see KB5020805: How to manage Kerberos protocol changes related to CVE-2022-37967.

We are working on a resolution and will provide an update in an upcoming release.

After installing this update, apps which use ODBC connections through Microsoft ODBC SQL Server Driver (sqlsrv32.dll) to access databases might not connect. Additionally, you might receive an error in the app, or you might receive an error from the SQL Server. Errors you might receive include the following messages:

• The EMS System encountered a problem.
  Message: [Microsoft][ODBC SQL Server Driver] Protocol error in TDS Stream.

• The EMS System encountered a problem.
  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 than 4 bytes (such as SQL_C_FLOAT).

To decide whether you are using an affected app, open the app which connects to a database. Open a Command Prompt window, type the following command and then press Enter:

tasklist /m sqlsrv32.dll

If the command returns a task, then the app might be affected.

To mitigate this issue, you can do one of the following:

• If your app is already using or able to use Data Source Name (DSN) to select ODBC connections, install Microsoft ODBC Driver 17 for SQL Server and select it for use with your app using DSN.
  
  Note: We recommend the latest version of Microsoft ODBC Driver 17 for SQL Server, as it is more compatible with apps currently using the legacy Microsoft ODBC SQL Server Driver (sqlsrv32.dll) than Microsoft ODBC Driver 18 for SQL Server.

• If your app is unable to use DSN, the app will need to be modified to allow for DSN or to use a newer ODBC driver than Microsoft ODBC SQL Server Driver (sqlsrv32.dll).

This issue was resolved in KB5022352. If you have implemented the above workaround, it is recommended to continue using the configuration in the workaround.

Release Channel

Available

Next Step

Windows Update and Microsoft Update

Yes

None. This update will be downloaded and installed automatically from Windows Update.

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 8.1, Windows Server 2012 R2, Windows Embedded 8.1 Industry Enterprise, Windows Embedded 8.1 Industry Pro

Classification: Security Updates