October 11, 2022 - KB5018418 (OS Build 22000.1098)
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 11, version 21H2, see its
update history page.
Note Follow
@WindowsUpdate to find out when new content is published to the Windows release health dashboard.
For more information on our tip this month, see
How to use focus in Windows 11
The release notes video is moving! Next month, you can find us under the Windows 11, version 22H2 node of the navigation panel. You can also find the video by visiting our new YouTube channel,
Windows community.
Highlights
- We address security issues for your Windows operating system.
Improvements
This security update includes improvements that were a part of update
KB5017383 (released September 20, 2022). Key changes in this release include:
- We address 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
Security Update Guide website and the
October 2022 Security Updates.
Windows 11 servicing stack update - 22000.1035
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
| Applies to | Symptom | Workaround |
|---|
| All users | 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 KB5018483. 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. |
| IT admins | 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. |
How to get this update
Before installing this update
Microsoft 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.
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 11
Classification: Security Updates |
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 5018418.
For a list of the files that are provided in the servicing stack update, download the
file information for the SSU - version 22000.1035.
www.elevenforum.com
