October 11, 2022—KB5018450 (Monthly Rollup)

Summary

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

REMINDER Windows Server 2008 Service Pack 2 (SP2) has reached the end of mainstream support and is now in extended support. Starting in July 2020, there will no longer be optional, non-security releases (known as “C” 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 in the How to get this update section before installing this update. Customers who have purchased the Extended Security Update (ESU) for on-premises versions of this OS must follow the procedures in KB4522133 to continue receiving security updates after extended support ended on January 14, 2020. For more information about ESU and which editions are supported, see KB4497181. Because ESU is available as a separate SKU for each of the years in which they are offered (2020, 2021, and 2022)—and because ESU can only be purchased in specific 12-month periods—you must purchase the third year of ESU coverage separately and activate a new key on each applicable device for your devices to continue receiving security updates in 2022.If your organization did not purchase the third year of ESU coverage, you must purchase Year 1, Year 2, and Year 3 ESU for your applicable Windows Server 2008 SP2 devices before you install and activate the Year 3 MAK keys to receive updates. The steps to install, activate, and deploy ESUs are the same for first, second, and third year coverage. For more information, see Obtaining Extended Security Updates for eligible Windows devices for the Volume Licensing process and Purchasing Windows 7 ESUs as a Cloud Solution Provider for the CSP process. For embedded devices, contact your original equipment manufacturer (OEM).For more information, see the ESU blog.

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 for Windows Server 2008 SP2, see the following update history home page.

Improvements

This cumulative security update contains improvements that are part of update KB5017358 (released September 13, 2022) and includes key changes for the following:

• 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

• If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181.
• If you do not have an ESU MAK add-on key installed and activated.
  If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the “How to get this update” section of this article.
  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 KB5020019. 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, typeDate and time, and selectDate and time settings. From theDate & time settingspage, clear theAdjust for daylight saving time automatically check box.

• Go to Control Panel >Clock and Region>Date and Time>Change time zoneand clear theAutomatically adjust clock for Daylight Saving Timecheck 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.| Please see KB5020276 for guidance on this issue.

How to get this update

Before installing this update****IMPORTANT Customers who have purchased the Extended Security Update (ESU) for on-premises versions of these operating systems must follow the procedures in KB4522133 to continue receiving security updates because extended support ended on January 14, 2020.For more information about ESU and which editions are supported, see KB4497181.Language packsIf 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.Prerequisite:You must install the updates listed below andrestart your device before installing the latest Rollup. Installing these updates improves the reliability of the update process and mitigates potential issues while installing the Rollup and applying Microsoft security fixes.

1. The April 9, 2019 servicing stack update (SSU) (KB4493730). To get the standalone package for this SSU, search for it in the Microsoft Update Catalog. This update is required to install updates that are only SHA-2 signed.
2. The latest SHA-2 update (KB4474419) released October 8, 2019. If you are using Windows Update, the latest SHA-2 update will be offered to you automatically. This update is required to install updates that are only SHA-2 signed. For more information on SHA-2 updates, see 2019 SHA-2 Code Signing Support requirement for Windows and WSUS.
3. The Extended Security Updates (ESU) Licensing Preparation Package (KB4538484) or the Update for the Extended Security Updates (ESU) Licensing Preparation Package (KB4575904). The ESU licensing preparation package will be offered to you from WSUS. To get the standalone package for ESU licensing preparation package, search for it in the Microsoft Update Catalog.
   After installing the items above, Microsoft strongly recommends that you install the latest SSU (KB5016129). If you are using Windows Update, the latest SSU will be offered to you automatically if you are an ESU customer. To get the standalone package for the latest SSU, search for it in the Microsoft Update Catalog. For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.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 if you are an ESU customer.
   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 2008 Service Pack 2Classification: Security Updates

File information

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

References

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