October 17, 2022—KB5020435 (OS Builds 19042.2132, 19043.2132, and 19044.2132) Out-of-band

^10/11/22 IMPORTANT All editions of Windows 10, version 21H1 will reach 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.

^8/26/22 REMINDER Windows Server, version 20H2 reached end of service on August 9, 2022. These devices no longer receive monthly security and quality updates that contain protection from the latest security threats. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows Server.

We will continue to service the following editions: Windows 10 Enterprise and Education, Windows 10 IoT Enterprise, Windows 10 Enterprise multi-session, and Windows 10 on Surface Hub.

^5/10/22 REMINDER To update to one of the newer versions of Windows 10, we recommend that you use the appropriate Enablement Package KB (EKB). Using the EKB makes updating faster and easier and requires a single restart. To find the EKB for a specific OS, go to the Improvements section and click or tap the OS name to expand the collapsible section.

^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

It addresses an issue that might affect some types of Secure Sockets Layer (SSL) and Transport Layer Security (TLS) connections. These connections might have handshake failures. For developers, the affected connections are likely to receive one or more records followed by a partial record with a size of less than 5 bytes within a single input buffer. If the connection fails, your app will receive the error, “SEC_E_ILLEGAL_MESSAGE”.

Improvements

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

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

This non-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.

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

This non-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.

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

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

It addresses an issue that might affect some types of Secure Sockets Layer (SSL) and Transport Layer Security (TLS) connections. These connections might have handshake failures. For developers, the affected connections are likely to receive one or more records followed by a partial record with a size of less than 5 bytes within a single input buffer. If the connection fails, your app will receive the error, “SEC_E_ILLEGAL_MESSAGE”.

If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.

Windows 10 servicing stack update - 19042.1940, 19043.1940 and 19044.1940

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

Symptoms	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: 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> Extract the SSU from the previously extracted cab via this command line: *expand Windows10.0-KB5000842-x64.cab /f: <destination path> 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.
On October 5, 2022, the Jordanian government made an official announcement ending the winter-time Daylight Saving Time (DST) time zone change. Starting at 12:00 a.m. Friday, October 28, 2022, the official time will not advance by an hour and will permanently shift to the UTC + 3 time zone. The impact of this change is as follows: Clocks will not be advanced by an hour at 12:00 a.m. on October 28, 2022 for the Jordan time zone. The Jordan time zone will permanently shift to the UTC + 3 time zone. Symptoms if no update is installed and the workaround is not used on devices in the Jordan time zone on October 28, 2022 or later: Time shown in Windows and apps will not be correct. Apps and cloud services which use date and time for integral functions, such as Microsoft Teams and Microsoft Outlook, notifications and scheduling of meetings might be 60 minutes off. Automation using date and time, such as Scheduled tasks, might not run at the expected time. Timestamp on transactions, files, and logs will be 60 minutes off. Operations that rely on time-dependent protocols such as Kerberos might cause authentication failures when attempting to logon or access resources. Windows devices and apps outside of Jordan might also be affected if they are connecting to servers or devices in Jordan or if they are scheduling or attending meetings taking place in Jordan from another location or time zone. Windows devices outside of Jordan should not use the workaround, as it would change their local time on the device.	This issue is addressed in KB5018482. This update will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install. If you cannot install this update, you can mitigate this issue on devices in Jordan by doing either of the following on October 28, 2022: Select the Windows logo key, type "Date and time", and select Date and time settings. From the Date & time settings page, toggle Adjust for daylight saving time automatically to Off. Go to Control Panel > Clock and Region > Date and Time > Change time zone and uncheck the option for “Automatically adjust clock for Daylight Saving Time”. Important: We recommend using ONLY the above workaround to mitigate the issue with time created by the new Daylight Savings Time in Jordan. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if done incorrectly. We are working on a resolution and estimate a solution will be available in late October optional preview releases for the following versions of Windows: Windows 11, version 22H2 Windows 11, version 21H2 Windows Server 2022 Windows 10, version 21H2 Windows 10, version 21H1 Windows 10, version 20H2 (Enterprise and Education editions only) Note: Microsoft plans to release an update to support this change and some versions are estimated to be available before October 28, 2022. However, if an update is not available for the version of Windows you are using, please use the workaround above.
After installing this update, Microsoft OneDrive might unexpectedly close, and you might receive an error when attempting to do the following: Sign out or unlink your account in the Microsoft OneDrive sync app. Unlink sites or folders from syncing to your device from Microsoft SharePoint or Microsoft Teams sites. Uninstalling the OneDrive sync app might fail. Note These issues might affect both OneDrive and OneDrive for Business.	We are working on a resolution and estimate a solution will be available in the coming week.

Symptoms

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:

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

On October 5, 2022, the Jordanian government made an official announcement ending the winter-time Daylight Saving Time (DST) time zone change. Starting at 12:00 a.m. Friday, October 28, 2022, the official time will not advance by an hour and will permanently shift to the UTC + 3 time zone.

The impact of this change is as follows:

Clocks will not be advanced by an hour at 12:00 a.m. on October 28, 2022 for the Jordan time zone.
The Jordan time zone will permanently shift to the UTC + 3 time zone.

Symptoms if no update is installed and the workaround is not used on devices in the Jordan time zone on October 28, 2022 or later:

Time shown in Windows and apps will not be correct.
Apps and cloud services which use date and time for integral functions, such as Microsoft Teams and Microsoft Outlook, notifications and scheduling of meetings might be 60 minutes off.
Automation using date and time, such as Scheduled tasks, might not run at the expected time.
Timestamp on transactions, files, and logs will be 60 minutes off.
Operations that rely on time-dependent protocols such as Kerberos might cause authentication failures when attempting to logon or access resources.
Windows devices and apps outside of Jordan might also be affected if they are connecting to servers or devices in Jordan or if they are scheduling or attending meetings taking place in Jordan from another location or time zone. Windows devices outside of Jordan should not use the workaround, as it would change their local time on the device.

This issue is addressed in KB5018482. This update will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install.

If you cannot install this update, you can mitigate this issue on devices in Jordan by doing either of the following on October 28, 2022:

Select the Windows logo key, type "Date and time", and select Date and time settings. From the Date & time settings page, toggle Adjust for daylight saving time automatically to Off.
Go to Control Panel > Clock and Region > Date and Time > Change time zone and uncheck the option for “Automatically adjust clock for Daylight Saving Time”.

Important: We recommend using ONLY the above workaround to mitigate the issue with time created by the new Daylight Savings Time in Jordan. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if done incorrectly.

We are working on a resolution and estimate a solution will be available in late October optional preview releases for the following versions of Windows:

Windows 11, version 22H2
Windows 11, version 21H2
Windows Server 2022
Windows 10, version 21H2
Windows 10, version 21H1
Windows 10, version 20H2 (Enterprise and Education editions only)

Note: Microsoft plans to release an update to support this change and some versions are estimated to be available before October 28, 2022. However, if an update is not available for the version of Windows you are using, please use the workaround above.

After installing this update, Microsoft OneDrive might unexpectedly close, and you might receive an error when attempting to do the following:

Sign out or unlink your account in the Microsoft OneDrive sync app.
Unlink sites or folders from syncing to your device from Microsoft SharePoint or Microsoft Teams sites.
Uninstalling the OneDrive sync app might fail.

Note These issues might affect both OneDrive and OneDrive for Business.

We are working on a resolution and estimate a solution will be available in the coming week.

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:

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.
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 or Microsoft Update	No	See the options below.
Windows Update for Business	No	See the options below.
Microsoft Update Catalog	Yes	To get the standalone package for this update, go to the Microsoft Update Catalog website.
Windows Server Update Services (WSUS)	No	See the options above.

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

For a list of the files that are provided in the servicing stack update, download the file information for the SSU - version 19042.1940, 19043.1940 and 19044.1940.

October 17, 2022—KB5020435 (OS Builds 19042.2132, 19043.2132, and 19044.2132) Out-of-band

Highlights

Improvements

Windows 10 servicing stack update - 19042.1940, 19043.1940 and 19044.1940

Known issues in this update

How to get this update

Need more help?

Want more options?

Was this information helpful?

Thank you for your feedback!

Highlights

Improvements

Windows 10, version 21H2

Windows 10, version 21H1

Windows 10, version 20H2 editions: Windows 10 Enterprise Multi-Session, Windows 10 Enterprise and Education, Windows 10 IoT Enterprise

Windows 10 servicing stack update - 19042.1940, 19043.1940 and 19044.1940

Known issues in this update

Click or tap to view the known issues

How to get this update

Need more help?

Want more options?

Was this information helpful?

Thank you for your feedback!