Related topics
×
Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Release Date:

3/22/2022

Version:

OS Build 17763.2746

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 prevents Android device users from signing in to some Microsoft applications, such as Microsoft Outlook or Microsoft Teams. 

  • Updates an issue that causes the Back button of the credentials window, where you sign in, to become invisible in high contrast black mode.

Improvements

This non-security update includes quality improvements. Key changes include:

  • Addresses an issue that affects searchindexer.exe and prevents Microsoft Outlook’s offline search from returning recent emails.

  • Addresses an issue that causes searchindexer.exe to stop responding during a dismount operation in the Remote Desktop setup environment.

  • Addresses an issue in which modern browsers fail to correctly render HTML that is generated by gpresult/h.

  • Addresses an issue that might prevent a DNS Server query resolution policy from working as expected when you specify a fully qualified domain name (FQDN) and subnet conditions.

  • Addresses an issue that might unintentionally add a Trusted Platform Module (TPM) protector when you use the Silent BitLocker enablement policy.

  • Addresses an issue that prevents Event 4739 from displaying the new values of certain attributes after a policy change.

  • Addresses an issue that might cause domain joining to fail in environments that use disjoint DNS hostnames.

  • Addresses an issue that prevents you from accessing Server Message Block (SMB) shares using an IP Address when SMB hardening is enabled.

  • Addresses an issue that causes stop error 0x1E in the SMB Server (srv2.sys).

  • Addresses an issue that causes an “Access denied” exception for a file during a PowerShell test for AppLocker.

  • Addresses an issue that might cause the Group Policy Service to stop processing telemetry information for Group Policy Registry Preferences.

  • Addresses an issue that causes the Group Policy Management Console to stop working after you close it. The system logs Application Error Event ID 1000 and the error, 0xc0000005 (STATUS_ACCESS_VIOLATION); the failing module is GPOAdmin.dll.

  • Addresses a heap leak in PacRequestorEnforcement that degrades the performance of a domain controller.

  • Addresses an issue that affects the Key Distribution Center (KDC) Proxy. The KDC Proxy cannot properly obtain Kerberos tickets for signing in to Key Trust Windows Hello for Business.

  • Addresses an issue that logs Event ID 37 during certain password change scenarios, including failover cluster name object (CNO) or virtual computer object (VCO) password changes.

  • Addresses an issue that prevents the User Account Control (UAC) dialog from correctly showing the application that is requesting elevated privileges.

  • Addresses an issue that prevents Android device users from signing in to some Microsoft applications, such as Microsoft Outlook or Microsoft Teams. This issue occurs after rolling over token signing and decrypting certificates, resetting a user's password, or when an administrator has revoked refresh tokens.  

  • Addresses an issue that prevents the Back button of the credentials window, where you sign in, from being visible in high contrast black mode.

  • Addresses an issue that causes the Move-ADObject command to fail when you move computer accounts across domains. The error message is, “Multiple values were specified for an attribute that can have only one value”.

  • Addresses an issue that occurs when the Best Practices Analyzer (BPA) values for SMB have not been updated for more recent platforms.

  • Addresses an issue that causes a mismatch between NetBIOS and DNS Active Directory domain names when you create a cluster.

  • Addresses an issue that causes the Network File System (NFS) redirector to stop working (error 0x50) when you convert a text file to a PDF.

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.2744

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."

  1. Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10.

  2. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10.

Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows:

  1. Go to the Settings app > Recovery.

  2. Select Get Started under the Reset this PC recovery option.

  3. Select Keep my Files.

Microsoft is working on a resolution and will provide an update in an upcoming release.

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:

  • Windows Server 2022: 

  • Windows Server 2019: 

  • Windows Server 2016: 

  • Windows Server 2012 R2: 

  • Windows Server 2012:

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 5011551.

For a list of the files that are provided in the servicing stack update, download the file information for the SSU - version 17763.2744.

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.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×