Related topics
×
Sign in with Microsoft
Sign in or create an account.

Release Date:

11/8/2022

Version:

Monthly Rollup

Summary

Learn more about this cumulative security 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 cumulative security update contains improvements that are part of update KB5017370 (released October 11, 2022) and includes key changes for the following:

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

Known issues in this update

Symptom

Next step

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 Windows updates released on or after November 8, 2022 on Windows Servers that use the Domain Controller role, you might have issues with Kerberos authentication. This issue might affect any Kerberos authentication in your environment. Some scenarios which might be affected:

When this issue is encountered you might receive a Microsoft-Windows-Kerberos-Key-Distribution-Center Event ID 4 error event in the System section of the event log on your Domain Controller with the below text.

Note Affected events will contain "the missing key has an ID of 1" string:

While processing an AS request for target service <service>, the account <account name> did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 1). The requested etypes : 18 3. The accounts available etypes : 23 18 17. Changing or resetting the password of <account name> will generate a proper key.

Note This issue is not an expected part of the security hardening for Netlogon and Kerberos starting with November 2022 security update. You will still have to follow the guidance in these articles even after this issue is resolved.

Windows devices used at home by consumers or devices which are not part of an on-premises domain are not affected by this issue. Azure Active Directory environments that are not hybrid and have no on-premises Active Directory servers are not affected.

This issue is addressed in update KB5021652.

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

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

Yes

None. This update will be downloaded and installed automatically from Windows Update.

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 Updates

File information

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

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!

×