January 25, 2022—KB5009616 (OS Build 17763.2510) Preview
Applies To
Win 10 Ent LTSC 2019 Win 10 IoT Ent LTSC 2019 Windows 10 IoT Core LTSC Windows Server 2019Release Date:
25/01/2022
Version:
OS Build 17763.2510
11/17/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 1809, see its update history page.
Highlights
-
Updates daylight savings time to start in February 2022 instead of March 2022 in Jordan.
-
Updates the phone number for Windows Activation for locales that have the wrong phone number.
Improvements
This non-security update includes quality improvements. Key changes include:
-
Updates daylight savings time to start in February 2022 instead of March 2022 in Jordan.
-
Addresses an issue in CLSID_InternetExplorer.
-
Updates the phone number for Windows Activation for locales that have the wrong phone number.
-
Addresses an issue that might cause Remote Desktop Servers to leak memory.
-
Addresses an issue that causes Windows to stop working and generates the error, “IRQL_NOT_LESS_OR_EQUAL”.
-
Addresses a memory leak in TextInputHost.exe.
-
Adds support for configuring certain adapters to support redundant array of independent disks (RAID) for OS installations and provides pass-through on other connected drives for Microsoft Storage Spaces Direct (S2D).
-
Addresses an issue that causes the Test-Cluster PowerShell command to incorrectly fail, and the error message states the BusType is still set to RAID.
-
Addresses an issue that prevents Robocopy from retrying the file copy process.
-
Addresses an issue that might cause Kerberos.dll to stop working within the Local Security Authority Subsystem Service (LSASS). This occurs when LSASS processes simultaneous Service for User (S4U) user-to-user (U2U) requests for the same client user.
-
Addresses an issue that affects Windows Defender Application Control (WDAC) in Audit Mode. This issue generates events for managed code that causes performance issues when you load managed code.
-
Addresses an issue that causes lsass.exe to stop working and the device restarts. This issue occurs when you query Windows NT Directory Services (NTDS) counters after the NTDS service has stopped.
-
Addresses a known issue that affects versions of Windows Server that are in use as a Key Management Services (KMS) host. Client devices running Windows 10 Enterprise LTSC 2019 might not activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK) and after installing updates released April 22, 2021 or later.
-
Addresses an issue that might occur when you enable verbose Active Directory Federation Services (AD FS) audit logging and an invalid parameter is logged. As result, Event 207 is logged, which indicates that a failure to write to the audit log occurred.
-
Addresses a memory leak that occurs when you call WinVerifyTrust(). This issue occurs if verification fails for the first signature of a file that has multiple signatures.
-
Adds an audit event to Active Directory domain controllers that identifies clients that are not compliant with RFC 4456. For more information, see KB5005408: Smart card authentication might cause print and scan failures.
If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.
Windows 10 servicing stack update - 17763.2510
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
|
Symptom |
Workaround |
|---|---|
|
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND." |
This issue is addressed by updates released June 11, 2019 and later. We recommend you install the latest security updates for your device. Customers installing Windows Server 2019 using media should install the latest Servicing Stack Update (SSU) before installing the language pack or other optional components. If using the Volume Licensing Service Center (VLSC), acquire the latest Windows Server 2019 media available. The proper order of installation is as follows:
Note Updating your device will prevent this issue, but will have no effect on devices already affected by this issue. If this issue is present in your device, you will need to use the workaround steps to repair it. Workaround:
Note If reinstalling the language pack does not mitigate the issue, use the In-Place-Upgrade feature. For guidance, see How to do an in-place upgrade on Windows, and Perform an in-place upgrade of Windows Server. |
|
After installing KB5001342 or later, the Cluster Service might fail to start because a Cluster Network Driver is not found. |
This issue occurs because of an update to the PnP class drivers used by this service. After about 20 minutes, you should be able to restart your device and not encounter this issue. For more information about the specific errors, cause, and workaround for this issue, please see KB5003571. |
|
After installing the November 22, 2021 or later updates, recent emails might not appear in search results in the Microsoft Outlook desktop app. This issue is related to emails that have been stored locally in a PST or OST files. It might affect POP and IMAP accounts, as well as accounts hosted on Microsoft Exchange and Microsoft 365. If the default search in the Microsoft Outlook app is set to server search, the issue will only affect the advanced search. |
This issue is resolved in KB5010351. Alternate resolution if you have not installed updates dated February 8, 2022 or later This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, you can resolve this by installing and configuring a special Group Policy (preferred). Important Verify that you are using the correct Group Policy for your version of Windows. Group Policy: Windows 10, version 1809, Windows 10 Enterprise LTSC 2019, and Windows Server 2019 |
|
After installing updates released January 11, 2022 or later, apps that use the Microsoft .NET Framework to acquire or set Active Directory Forest Trust Information might have issues. The apps might fail or close or you might receive an error from the app or Windows. You might also receive an access violation (0xc0000005) error. Note for developers Affected apps use the System.DirectoryServices API. |
To resolve this issue manually, apply the out-of-band updates for the version of the .NET Framework used by the app. Note These out-of-band updates are not available from Windows Update and will not install automatically. To get the standalone package, search for the KB number for your version of Windows and .NET Framework in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog. For instructions on how to install this update for your operating system, see the KB articles listed below:
|
|
After installing updates released January 25, 2022 (KB5009616) and later on affected versions of Windows Server that are running the DNS Server role, DNS stub zones might not load correctly. As a result, DNS name resolution might fail. A stub zone is a copy of a DNS zone that contains only resource records that identify the DNS servers for that zone. |
This issue is addressed in KB5012647. |
|
After installing the Windows updates released January 11, 2022 or later Windows versions on an affected version of Windows, recovery discs (CD or DVD) created by using the Backup and Restore (Windows 7) app in Control Panel might be unable to start. Recovery discs that were created by using the Backup and Restore (Windows 7) app on devices which have installed Windows updates released before January 11, 2022 are not affected by this issue and should start as expected. Note No third-party backup or recovery apps are currently known to be affected by this issue |
This issue is addressed in KB5014022. |
|
Windows server computers might log Event ID 40 in the System event log each time a Group Policy is updated or refreshed on a server or client. The error is found with the Description, ”The event logging service encountered an error when attempting to apply one or more policy settings.” This issue occurs after installing Windows updates released on or after January 11, 2022. The gpupdate and Group Policy Object (GPO) refresh tasks will trigger this error when they run (default run times for these tasks is every 90-120 minutes on member servers or 5 minutes on domain controllers). This issue occurs specifically after you configure any setting under Computer Configuration > Windows Components > Event Log Service > Security. Settings under Computer Configuration > Policies > WindowsSettings > Security Settings > Event Log do not trigger this error and can be used. IMPORTANT The errors described in this issue do not prevent Security log changes from being applied. |
This issue is addressed in KB5014022. |
How to get this update
Before installing this update
Microsoft now combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU. For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.
Prerequisite:
You must install the August 10, 2021 SSU (KB5005112) before installing the LCU.
Install this update
|
Release Channel |
Available |
Next Step |
|---|---|---|
|
Windows Update or Microsoft Update |
Yes |
Go to Settings > Update & Security > Windows Update. In the Optional updates available area, you’ll find the link to download and install the update. |
|
Windows Update for Business |
No |
None. These changes will be included in the next security update to this channel. |
|
Microsoft Update Catalog |
Yes |
To get the standalone package for this update, go to the Microsoft Update Catalog website. |
|
Windows Server Update Services (WSUS) |
No |
You can import this update into WSUS manually. See the Microsoft Update Catalog for instructions. |
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 5009616.
For a list of the files that are provided in the servicing stack update, download the file information for the SSU - version 17763.2510.
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.
