October 11, 2022—KB5018411 (OS Build 14393.5427)

^{NEW 10/11/22} IMPORTANT On January 10, 2023, the public extension for servicing devices that have the Intel Atom Clover Trail processor will end. The January 10, 2023 security update is the last update for these devices. After that date, they will not receive monthly security and quality updates. These updates protect you from the latest security threats. Unfortunately, these devices do not meet the hardware requirements to upgrade to a newer version of Windows 10 or Windows 11. We recommend that you consider a new device that has Windows 11.

^11/19/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 1607, see its update history page.

Highlights

It updates the start date for daylight saving time in Chile. It will start on September 11, 2022 instead of on September 4, 2022.
It addresses security issues for your Windows operating system.

Improvements

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

It updates the start date for daylight saving time in Chile. It will start on September 11, 2022 instead of on September 4, 2022.
It addresses an issue that affects some virtual machines. They drop User Datagram Protocol (UDP) packets.
It introduces a Group Policy that enables and disables Microsoft HTML Application (MSHTA) files.
It addresses an issue that affects a primary Active Directory Federation Services (AD FS) node. It might fail to register or update its heartbeat. Because of this, the node is removed from the farm.
It addresses an issue that affects robocopy. This issue occurs when you use the backup option (/B) to migrate or synchronize data to Azure Files.
It addresses an issue that affects robocopy. This issue occurs when you use the backup option (/B) to address data loss and the source location contains tiered files with Azure File Sync or tiered files with Cloud Files.
It addresses an issue that affects a Server Message Block (SMB) multichannel connection. This issue might lead to stop error 13A or C2.
It addresses a known issue that might affect file copies that use Group Policy Preferences. They might fail or might create empty shortcuts or files that have 0 (zero) bytes.

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 October 2022 Security Updates.

Known issues in this update

Symptom	Workaround
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 KB5019964.
After this and later updates are 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.	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.
After installing this update, some types of SSL (Secure Sockets Layer) and TLS (Transport Layer Security) connections might have handshake failures. Note for developers The affected connections are likely to be sending multiple frames within a single input buffer, specifically one or more complete records with a partial record that is less than 5 bytes all sent in a single buffer. When this issue is encountered, your app will receive SEC_E_ILLEGAL_MESSAGE when the connection fails.	This issue is addressed in KB5020439. We recommend you install the latest security update for your device. Note KB5020439 will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install.

Symptom

Workaround

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

After this and later updates are 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.

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.

After installing this update, some types of SSL (Secure Sockets Layer) and TLS (Transport Layer Security) connections might have handshake failures.

Note for developers The affected connections are likely to be sending multiple frames within a single input buffer, specifically one or more complete records with a partial record that is less than 5 bytes all sent in a single buffer. When this issue is encountered, your app will receive SEC_E_ILLEGAL_MESSAGE when the connection fails.

This issue is addressed in KB5020439. We recommend you install the latest security update for your device.

Note KB5020439 will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install.

How to get this update

Before installing this update

Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest cumulative update (LCU). SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU and applying Microsoft security updates. For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.

If you are using Windows Update, the latest SSU (KB5017396) will be offered to you automatically. To get the standalone package for the latest SSU, search for it in the Microsoft Update Catalog.

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	Yes	None. This update will be downloaded and installed automatically from Windows Update in accordance with configured policies.
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 10 Classification: Security Updates

File information

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

October 11, 2022—KB5018411 (OS Build 14393.5427)

Highlights

Improvements

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!