July 21, 2022—KB5015880 (OS Build 17763.3232) Preview
Release Date:
21/07/2022
Version:
OS Build 17763.3232
7/12/22
After September 20, 2022, there will no longer be optional, non-security releases (known as "C" or preview releases) for the 2019 LTSC editions and Windows Server 2019. Only cumulative monthly security updates (known as the "B" or Update Tuesday release) will continue for the 2019 LTSC editions and Windows Server 2019.11/17/20 types of Windows updates and the monthly quality update types. For an overview of Windows 10, version 1809, see its update history page.
For information about Windows update terminology, see the article about theHighlights
-
Addresses an issue that prevents certain troubleshooting tools from opening.
Improvements
This non-security update includes quality improvements. Key changes include:
-
Addresses an issue that prevents certain troubleshooting tools from opening.
-
Addresses an issue that causes port mapping conflicts for containers.
-
Addresses an issue that causes Code Integrity to continue trusting a file after the file has been modified.
-
Provides the option to configure an alternate login ID for an Azure Multi-Factor Authentication (MFA) Active Directory Federation Services (AD FS) adapter for on-premises scenarios. You can disable the alternate login ID as required. To configure the Azure MFA ADFS adapter to ignore an alternate login ID, run the following PowerShell command:
-
Set-AdfsAzureMfaTenant -TenantId '<TenandID>' -ClientId ' 981f26a1-7f43-403b-a875-f8b09b8cd720' -IgnoreAlternateLoginId $true.
To restart the ADFS service on each server in the farm, use the Restart-Service adfssrv PowerShell command.
The adapter configuration will only ignore Alternate Login ID when IgnoreAlternateLoginId is explicitly set to $true using the command above. If you do not set IgnoreAlternateLoginId or if you set it to $false, the default behavior occurs, which causes the adapter to use the Alternate Logon ID settings.
-
-
Addresses an issue that triggers lockout policies faster when you use Remote Desktop Protocol (RDP) with fast reconnect and Network Level Authentication (NLA) is disabled. This issue occurs when you call LogonUser() with a blank password.
-
Addresses an issue that prevents the Storage Migration Service (SMS) from completing inventory on servers that have many shares. The system logs error event 2509 in Microsoft-Windows-StorageMigrationService/Admin channel (ErrorId=-2146233088/ErrorMessage="Invalid table id").
-
Addresses an issue that causes Microsoft’s deduplication driver to consume large amounts of nonpaged pool memory. Consequently, this depletes all the physical memory on the machine, which causes the server to stop responding.
-
Addresses an issue that prevents enterprise users from opening sites on-demand in IE mode using Microsoft Edge.
-
Enforces a hardening change that requires printers and scanners that use smart cards for authentication to have firmware that complies with section 3.2.1 of RFC 4556. If they do not comply, Active Directory domain controllers will not authenticate them. Mitigations that allowed non-compliant devices to authenticate will not exist after August 9, 2022. For more information about this change, see KB5005408.
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.3232
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." |
Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows:
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.KB5003571. For more information about the specific errors, cause, and workaround for this issue, please see |
After installing this or later updates on devices running 32-bit versions of Windows, you might be unable to open Microsoft Edge. |
This issue was resolved in the latest Microsoft Edge Stable channel release, version 103.0.1264.62. See Microsoft Edge release notes for Stable Channel for more information. Microsoft Edge should update in the background, but if you do not want to wait, you can download Microsoft Edge to update to the latest version immediately. |
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 5015880.
For a list of the files that are provided in the servicing stack update, download the file information for the SSU - version 17763.3232.