Applies ToWindows 10 Enterprise Multi-Session, version 20H2 Windows 10 Enterprise and Education, version 20H2 Windows 10 IoT Enterprise, version 20H2 Windows 10 on Surface Hub Windows 10, version 21H1, all editions Windows 10, version 21H2, all editions Windows 10, version 22H2, all editions

Release Date:

12/13/2022

Version:

OS Builds 19042.2364, 19043.2364, 19044.2364, and 19045.2364

EXPIRATION NOTICE

IMPORTANT As of 9/12/2023, this KB is only available from Windows Update. It is no longer available from the Microsoft Update Catalog or other release channels.  We recommend that you update your devices to the latest security quality update. 

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 C releases will resume in January 2023. 

UPDATED 1/3/23 IMPORTANT The retired, out-of-support Internet Explorer 11 desktop application will be permanently turned off using a Microsoft Edge update on certain versions of Windows 10 on February 14, 2023. Go to Internet Explorer 11 desktop app retirement FAQ for more information.

12/13/22 REMINDER All editions of Windows 10, version 21H1 are at end of service on December 13, 2022. After this December 13, 2022 update, these devices will not receive monthly security and quality updates. These updates contain protections from the latest security threats. To continue receiving security and quality updates, we recommend that you update to the latest version of Windows.

11/17/20

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 10, version 20H2, see its update history page. 

Note Follow @WindowsUpdate to find out when new content is published to the Windows release health dashboard.

Highlights

  • This update addresses an issue that affects the Camera app. The app stops responding when memory is low.

Improvements 

Note To view the list of addressed issues, click or tap the OS name to expand the collapsible section.

: Use EKB KB5015684 to update to Windows 10, version 22H2.

This security update includes quality improvements. Key changes include: 

  • This build includes all the improvements from the supported Windows 10, version 20H2 editions.

  • No additional issues were documented for this release. 

: Use EKB KB5003791 to update to Windows 10, version 21H2.

This security update includes quality improvements. Key changes include: 

  • This build includes all the improvements from the supported Windows 10, version 20H2 editions.

  • No additional issues were documented for this release. 

: Use EKB KB5000736 to update to Windows 10, version 21H1.

This security update includes quality improvements. Key changes include: 

  • This build includes all the improvements from the supported Windows 10, version 20H2 editions.

  • No additional issues were documented for this release.

: Use EKB KB4562830 to update to the supported editions of Windows 10, version 20H2.

This security update includes improvements that were a part of update KB5020030 (released November 15, 2022). When you install this KB:

  • 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.

  • This update addresses security issues for your Windows operating system. 

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 new Security Update Guide website and the December 2022 Security Updates. 

Windows 10 servicing stack update - 19042.2300, 19043.2300, 19044.2300, and 19045.2300

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

Symptom

Workaround

Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later.

Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the SSU and latest cumulative update (LCU) without any extra steps. 

To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the SSU:

  1. Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab <destination path>

  2. Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path>

  3. You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU.

If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business.

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 open Command Prompt (select Start then type command prompt and select it) and type the following command:  

tasklist /m sqlsrv32.dll

This issue is addressed in KB5022282.

After installing this update, some Windows devices might start up to an error (0xc000021a) with a blue screen.

Technical note After installing this update, there might be a mismatch between the file versions of hidparse.sys in c:/windows/system32 and c:/windows/system32/drivers (assuming Windows is installed to your C: drive). This might cause signature validation to fail when cleanup occurs.

This issue is addressed in KB5022282. This update should prevent the issue from occurring. Windows devices in which this issue has already occurred will still need to follow the workaround below.

To mitigate this issue on devices already experiencing it, you will need to use Windows Recovery Environment (WinRE) with the following steps:

  1. You will need to enter Windows Recovery Environment. If your device has not automatically started up into WinRE, please see Entry points into WinRE.

  2. Select the Troubleshoot button.

  3. Select the Start recovery, troubleshooting, and diagnostic tools button.

  4. Select the Advanced Options button.

  5. Select the Command Prompt button and wait for your device to restart, if needed.

  6. Your device should restart to a Command Prompt window. You might need to sign into your device with your password before getting to the Command Prompt window.

  7. Run the following command xcopy C:\windows\system32\drivers\hidparse.sys C:\windows\system32\hidparse.sys

    (Important If Windows is not installed to C:\windows, you must modify the command for your environment.)

  8. Once the previous command completes, type exit

  9. Select the Continue button.

  10. Windows should now start up as expected.

Important It is not recommended to follow any other workaround than those recommended above. We do not recommend deleting the hidparse.sys from your Windows\System32folder.

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

How to get this update

Before installing this update

Microsoft now 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.

Prerequisite:

Based on your installation scenario, choose one of the following:

  1. For offline OS image servicing:

    If your image does not have the March 22, 2022 (KB5011543) or later LCU, you must install the special standalone May 10, 2022 SSU (KB5014032) before installing this update.

  2. For Windows Server Update Services (WSUS) deployment or when installing the standalone package from Microsoft Update Catalog: 

    If your devices do not have the May 11, 2021 (KB5003173) or later LCU, you must install the special standalone August 10, 2021 SSU (KB5005260) before installing this update.

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

No

No longer available.

Microsoft Update Catalog

No

No longer available.

Windows Server Update Services (WSUS)

No

No longer available.

If you want to remove the LCU

To 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 information

For a list of the files that are provided in this update, download the file information for cumulative update 5021233.

For a list of the files that are provided in the servicing stack update, download the file information for the SSU - version 19042.2300, 19043.2300, 19044.2300, and 19045.2300. 

Facebook LinkedIn Email
SUBSCRIBE RSS FEEDS

Need more help?

Want more options?

Discover Community

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Microsoft 365 subscription benefits

Microsoft 365 training

Microsoft security

Accessibility center

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Ask the Microsoft Community

Microsoft Tech Community

Windows Insiders

Microsoft 365 Insiders