Related topics
×
Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Release Date:

1/10/2023

Version:

OS Builds 19042.2486, 19044.2486, and 19045.2486

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. 

Important: For Windows Recovery Environment (WinRE) devices, see the updated (1/20/23) Special instructions for Windows Recovery Environment (WinRE) devices in the How to get this update section to address security vulnerabilities in CVE-2022-41099.

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. 

1/10/23
REMINDER All editions of Windows 10, version 21H1 reached end of service on December 13, 2022. After December 13, 2022, 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 security issues for your Windows operating system. 

Improvements 

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

Important: 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 are documented for this release. 

Important: 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 are documented for this release. 

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

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

  • This update addresses issues that affect the Local Session Manager (LSM). These issues might allow users who do not have admin rights to perform actions that only an admin can. 

  • This update addresses a known issue that affects apps that use Microsoft Open Database Connectivity (ODBC) SQL Server Driver (sqlsrv32.dll) to connect to databases. The connection might fail. You might also receive an error in the app, or you might receive an error from the SQL Server.

  • This update addresses a known issue that might affect startup on some Windows devices. They might receive an error (0xc000021a) and have a blue screen.

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 January 2023 Security Updates

Windows 10 servicing stack update - 19042.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.

The Start menu, Windows search, and Universal Windows Platform (UWP) apps might not work as expected or might have issues opening. Affected Windows devices might have damaged registry keys or data which might affect apps using Microsoft Office APIs to integrate with Windows, Microsoft Office, or Microsoft Outlook or Outlook Calendar. An example of an app affected by this issue is ClickShare. The underlying Issue is not caused by the installation of an update to Windows and might be exposed by an update to an affected app.

To mitigate this issue, you can uninstall apps which integrate with Windows, Microsoft Office, Microsoft Outlook or Outlook Calendar. Updates to affected apps or guidance from the developer of the app might also be available. If you are using ClickShare by Barco, please see Symptom: Start Menu and other shell components fail when Apps including Barco's ClickShare access Office APIs and Unresponsive Windows taskbar or user shell folder permissions issues with ClickShare App Calendar integration.

This issue is addressed in KB5027293.

After installing updates released January 10, 2023, and later, kiosk device profiles that have auto log on enabled might not sign in automatically. After Autopilot completes provisioning, affected devices will stay on the sign-in screen prompting for credentials.

This issue is addressed in KB5025221.

How to get this update

Special instructions for Windows Recovery Environment (WinRE) devices - updated 1/20/23

Devices with Windows Recovery Environment (WinRE) will need to update the WinRE partition to address security vulnerabilities in CVE-2022-41099. Installing the update normally into Windows will not address this security issue in WinRE. For guidance on how to address this issue in WinRE, please see CVE-2022-41099.

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

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

Need more help?

Want more options?

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

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

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×