- KB5021237: 2022-12 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems
- KB5021235: 2022-12 Cumulative Update for Windows Server 2016 for x64-based Systems
- KB5021294: 2022-12 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems
- KB5021285: 2022-12 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems
Impacted Products:
- Microsoft Windows
- Microsoft Windows
- Microsoft Edge (Edge HTML-based)
- Microsoft Edge (Chromium-based)
- Internet Explorer
- Microsoft Office and Microsoft Office Services and Web Apps
- Windows Defender
- Visual Studio
- ASP.NET Core
- Chakra Core
- Online Services
- Microsoft Dynamics
- .NET Framework
- .NET Core
Please note the following information regarding the security updates:
- For information regarding enabling Windows 10, version 1809 features and later, please see Windows 10, version 1909 delivery options. Note that Windows 10, versions 1903 and 1909 share a common core operating system with an identical set of system files. They will also share the same security update KBs. There is no change to the cumulative monthly security update
- Windows 10 updates are cumulative. The monthly security release includes all security fixes for vulnerabilities that affect Windows 10, in addition to non-security updates. The updates are available via the Microsoft Update Catalog.
- For information on lifecycle and support dates for Windows 10 operating systems, please see Windows Lifecycle Facts Sheet.
- A list of the latest servicing stack updates for each operating system can be found in ADV990001. This list will be updated whenever a new servicing stack update is released. It is important to install the latest servicing stack update.
- Updates for Windows RT 8.1 and Microsoft Office RT software are only available via Windows Update.
- In addition to security changes for the vulnerabilities, updates include defense-in-depth updates to help improve security-related features.
Known Issues:
KB5021237: Applies to Windows 10 Enterprise 2019 LTSC Windows 10 IoT Enterprise 2019 LTSC Windows 10 IoT Core 2019 LTSC
Improvements
This security update includes improvements. When you install this KB:
This update addresses an issue that might affect applications that run on the Windows Lock Down Policy (WLDP). They might stop working.
This update addresses an issue that affects remote networks. This issue stops you from reconnecting to them using DirectAccess.
This update addresses a known issue that might affect the Local Security Authority Subsystem Service (LSASS.exe). It might leak memory on Windows domain controllers. This issue might occur when you install Windows updates dated November 8, 2022, or later.
This update addresses a known issue that affects Direct Access. The issue might stop you from reconnecting to it after temporarily losing network connectivity. The issue might also occur when you switch between Wi-Fi networks or access points.
Symptom
After installing KB5001342 or later, the Cluster Service might fail to start because a Cluster Network Driver is not found.
After installing this update, apps that 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.
To decide whether you are using an affected app, open the app that connects to a database. Open a Command Prompt window, type the following command and then press Enter:
tasklist /m sqlsrv32.dll
If the command lists a task, then the app might be affected.
Workaround
This issue occurs because of an update to the PnP class drivers used by this service. After about 20 minutes, you should be able to restart your device and not encounter this issue.
For more information about the specific errors, cause, and workaround for this issue, please see KB5003571.
We are working on a resolution and will provide an update in an upcoming release.
This issue is addressed in KB5022554.
KB5021235: Applies to Windows 10, version 1607, all editions Windows Server 2016, all editions
Improvements
This update addresses a known issue that might affect the Local Security Authority Subsystem Service (LSASS.exe). It might leak memory on Windows domain controllers. This issue might occur when you install Windows updates dated November 8, 2022, or later.
After installing this update, apps that 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.
To decide whether you are using an affected app, open the app that connects to a database. Open a Command Prompt window, type the following command and then press Enter:
tasklist /m sqlsrv32.dll
If the command lists a task, then the app might be affected.
Symptom
After installing this update, apps that 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.
To decide whether you are using an affected app, open the app that connects to a database. Open a Command Prompt window, type the following command and then press Enter:
tasklist /m sqlsrv32.dll
If the command lists a task, then the app might be affected.
Workaround
Microsoft is working on a resolution and will provide an update in an upcoming release.
KB5021294: Applies to Windows Server 2012 Windows Embedded 8 Standard
REMINDER
Windows 8.1 will reach end of support on January 10, 2023, at which point technical assistance and software updates will no longer be provided. If you have devices running Windows 8.1, we recommend upgrading them to a more current, in-service, and supported Windows release. If devices do not meet the technical requirements to run a more current release of Windows, we recommend that you replace the device with one that supports Windows 11.
Microsoft will not be offering an Extended Security Update (ESU) program for Windows 8.1. Continuing to use Windows 8.1 after January 10, 2023 may increase an organization’s exposure to security risks or impact its ability to meet compliance obligations.
Improvements
This cumulative security update includes improvements that are part of update KB5020023 (released November 8, 2022) and update KB5021653 (released November 17, 2022). This update also makes improvements for the following issues:
By order of the Fijian government, Fiji will not observe daylight saving time (DST) in 2022. Therefore, clocks do not change by an hour at 02:00 on November 13, 2022.
A memory leak in the Local Security Authority Subsystem Service (LSASS.exe) occurs on Windows domain controllers. This issue is known to occur after installing Windows updates dated November 8, 2022, or later.
Symptoms
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.
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.
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.
Next step
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.
KB5021285: Windows Server 2012 Windows Embedded 8 Standard
REMINDER Windows Server 2012 has reached the end of mainstream support and is now in extended support. Starting in July 2020, there will no longer be optional releases (known as “C” or “D” releases) for this operating system. Operating systems in extended support have only cumulative monthly security updates (known as the “B” or Update Tuesday release).
Verify that you have installed the required updates listed in the How to get this update section before installing this update.
Improvements
This cumulative security update contains improvements that are part of update KB5020009 (released November 8, 2022) and update KB5021652 (released November 17, 2022). This update also makes improvements for the following issues:
By order of the Fijian government, Fiji will not observe daylight saving time (DST) in 2022. Therefore, clocks do not change by an hour at 02:00 on November 13, 2022.
A memory leak in the Local Security Authority Subsystem Service (LSASS.exe) occurs on Windows domain controllers. This issue is known to occur after installing Windows updates dated November 8, 2022, or later.
Symptom
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.
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.
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.
Next step
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.