Related topics
×
We couldn’t sign you in
Select the account you want to use.

Release Date:

10/11/2022

Version:

Security-only update

Summary

Learn more about this security-only update, including improvements, any known issues, and how to get the update.

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. 

Note For information about the various types of Windows updates, such as critical, security, driver, service packs, and so on, please see the following article. To view other notes and messages, see the Windows Server 2012 update history home page.

Improvements

This security-only update includes key changes for the following issue:

  • Addresses an issue that leads to User Datagram Protocol (UDP) packet drops from Linux virtual machines (VMs).

  • Updates daylight saving time (DST) in Chile to start on September 11, 2022 instead of September 4, 2022.

  • Addresses a known issue in which file copies which use Group Policy Preferences might fail or might create empty shortcuts or files that have 0 (zero) bytes.

For more information about the resolved security vulnerabilities, please refer to the Deployments | Security Update Guide and the October 2022 Security Updates.

Known issues in this update

Symptoms

Next step

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: 

  1. Clocks will not be advanced by an hour at 12:00 a.m. on October 28, 2022 for the Jordan time zone.

  2. 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 KB5020003. 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, clear the Adjust for daylight saving time automatically check box.

  • Go to Control Panel > Clock and Region > Date and Time > Change time zone and clear the Automatically adjust clock for Daylight Saving Time check box.

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.

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.

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 Secure Sockets Layer (SSL) and Transport Layer Security (TLS) connections might have handshake failures.

Note for developers: Affected connections might send multiple frames in a single input buffer. Specifically, one or more complete records with a partial record that is less than 5 bytes might be sent in a single buffer.

When encountering this issue, your app will receive SEC_E_ILLEGAL_MESSAGE when the connection fails.

To address this issue, install update KB5020449. Then, we recommend that you install the latest security update for your device.

Note Update KB5020449 will not install automatically. To apply this update, check for updates and then choose the Optional update to download and install.

How to get this update

Before installing this update

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

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

REMINDER If you are using Security-only updates, you will also need to install all previous Security-only updates and the latest cumulative update for Internet Explorer (KB5018413).

Language packs

If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.

Install this update

Release Channel

Available

Next Step

Windows Update and Microsoft Update

No

See the other 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)

Yes

This update will automatically sync with WSUS if you configure Products and Classifications as follows:

Product: Windows Server 2012, Windows Embedded 8 Standard

Classification: Security Update

File information

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

References

Learn about the standard terminology that is used to describe Microsoft software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×