February 15, 2022—KB5010427 (OS Build 17763.2628) Preview
Applies To
Win 10 Ent LTSC 2019 Win 10 IoT Ent LTSC 2019 Windows 10 IoT Core LTSC Windows Server 2019Release Date:
2/15/2022
Version:
OS Build 17763.2628
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 an issue that causes screen readers to describe a back button as "button" rather than "back button".
Improvements
This non-security update includes quality improvements. Key changes include:
-
New! Adds support for hot adding and the removal of non-volatile memory (NVMe) namespaces.
-
Addresses an issue that occurs when Windows Server 2016 runs as a terminal server using certain cloud computing virtual desktop infrastructure (VDI). As result, the servers randomly stop responding after running for a period of time. This also addresses a regression that proactively checks to ensure that the CSharedLock in rpcss.exe is set correctly to avoid a deadlock.
-
Addresses an issue that returns an error message when you browse for a domain or organizational unit (OU). This issue occurs because of improper zeroing out of memory.
-
Addresses an issue in DxDiag.exe that affects machines that have a high logical core count and fails to show the correct numbers of cores.
-
Addresses an issue that causes the improper cleanup of Dynamic Data Exchange (DDE) objects. This prevents session teardown and causes a session to stop responding.
-
Addresses an issue that prevents printing from operating properly for some low integrity process apps.
-
Addresses an issue that causes certificate enrollment to fail with the error message,” 0x800700a0 (ERROR _BAD_ARGUMENTS)”.
-
Addresses an issue that might cause BitLocker to damage virtual machine (VM) system files if you expand the BitLocker partition while the VM is offline.
-
Addresses an issue that prevents you from unloading and reloading drivers when the drivers are protected Hypervisor-protected Code Integrity (HVCI).
-
Addresses a reliability issue that affects the use of the Remote Desktop app to mount a client’s local drive to a terminal server session.
-
Addresses an issue that occurs when you try to write a service principal name (SPN) alias (such as www/contoso) and HOST/NAME already exists on another object. If the RIGHT_DS_WRITE_PROPERTY is on the SPN attribute of the colliding object, you receive an “Access Denied” error.
-
Addresses an issue that prevents administrators and content owners from opening expired Active Directory Rights Management Services (AD RMS) content.
-
Addresses an issue that affects the Windows search service and occurs when you query using the proximity operator.
-
Addresses a memory leak in the wmipicmp.dll module that causes a lot of false alarms in the System Center Operations Manager (SCOM) datacenter monitoring system.
-
Addresses an issue that causes the Remote Desktop Service (RDS)server to become unstable when the number of signed in users exceeds 100. This prevents you from accessing published applications using RDS on Windows Server 2019.
-
Addresses an issue that might display a blank Remote Desktop session window.
-
Addresses an issue that causes a mismatch between a Remote Desktop session’s keyboard and the Remote Desktop Protocol (RDP) client when signing in.
-
Addresses an issue that causes screen readers to describe a back button as "button" rather than "back button".
-
Addresses an issue that affects Server Message Block (SMB) performance counters. When you use the wildcard (*) character to query data, the query does not work as expected.
-
Addresses an issue that causes VM Live Migration to fail because vhdmp.sys receives different file control block (FCB) object pointers for the same file.
-
Addresses a memory leak in the Redirected Drive Buffering Subsystem (RDBSS) and the mrxsmb.sys drivers.
-
Addresses an issue that prevents Work Folder sync from recovering from the error code 0x80c80003, “Server is currently busy" on the client. This issue occurs even when the HTTP request queue on the server does not indicate a load.
-
Addresses an issue that calls a context function in a page fault path, which causes a 7F error.
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 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 5010427.
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.
