UPDATE 4/12: KB5012599 Windows 10 19042.1645, 19043.1645, 19044.1645

March 22, 2022 - KB5011543 (OS Builds 19042.1620, 19043.1620, and 19044.1620) Preview

^3/15/22
IMPORTANT Windows 10, version 20H2 will reach end of service on May 10, 2022 for devices running the Home, Pro, Pro Education, and Pro for Workstations editions. After May 10, 2022, these devices will no longer receive monthly security and quality updates that contain protection from the latest security threats. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows 10 or Windows 11.

We will continue to service the following editions: Enterprise, IoT Enterprise, Windows on Surface Hub, and Windows Server, version 20H2.

^01/11/22
REMINDER Windows 10, version 2004 reached end of servicing on December 14, 2021. To continue receiving security and quality updates, Microsoft recommends that you update to the latest version of Windows 10.

To update to one of the newer versions of Windows 10, we recommend that you use the appropriate Enablement Package KB (EKB). Using the EKB makes updating faster and easier and requires a single restart. To find the EKB for a specific OS, go to the Improvements section and click or tap the OS name to expand the collapsible section.

^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 20H2, see its update history page.

Note Follow @WindowsUpdate to find out when new content is published to the Windows release health dashboard.

Highlights

• New! Introducing search highlights
  
  Search highlights will present notable and interesting moments of what’s special about each day—like holidays, anniversaries, and other educational moments in time both globally and in your region. To see more details at a glance, hover, click, or tap on the illustration in the search box.
  
  For enterprise customers, search highlights will feature the latest updates from your organization and suggest people, files, and more.
  
  Search highlights will roll out to Windows 10 customers over the next several weeks. We are taking a phased and measured approach. Broad availability will occur in the coming months.
  
  Enterprise
  
  
  
  Consumer
  
• 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

Note: To view the list of addressed issues, click or tap the OS name to expand the collapsible section.

Windows 10, version 21H2

Important: Use EKB KB5003791 to update to Windows 10, version 21H2.

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

• This build includes all the improvements from Windows 10, version 20H2.
• No additional issues were documented for this release.

Windows 10, version 21H1

Important: Use EKB KB5000736 to update to Windows 10, version 21H1.

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

• This build includes all the improvements from Windows 10, version 20H2.
• No additional issues were documented for this release.

Windows 10, version 20H2

Important: Use EKB KB4562830 to update to Windows 10, version 20H2.

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

• New! Introducing search highlights
  
  Search highlights will present notable and interesting moments of what’s special about each day—like holidays, anniversaries, and other educational moments in time both globally and in your region. To see more details at a glance, hover, click, or tap on the illustration in the search box.
  
  For enterprise customers, search highlights will also feature the latest updates from your organization and suggest people, files, and more.
  
  Search highlights will roll out to Windows 10 customers over the next several weeks. We are taking a phased and measured approach. Broad availability will occur in the coming months.

• New! Provides the ability to change the color of toast buttons to identify success and critical scenarios more easily for apps that send notifications using Windows notifications in the OS. This feature also makes notifications more visually compact.
• New! Adds a new policy that expands an app’s top three notifications by default in the Action Center for apps that send notifications using Windows notifications in the OS. This feature displays multiple notifications that you can interact with simultaneously.
• Addresses an issue that causes searchindexer.exe to stop responding during a dismount operation in the Remote Desktop setup environment.
• Addresses an issue that affects searchindexer.exe and prevents Microsoft Outlook’s offline search from returning recent emails.
• Addresses an issue that might deactivate Windows when you change the National Language Support (NLS) version from 6.3 to 6.2.
• Addresses an issue in which modern browsers fail to correctly render HTML that is generated by gpresult/h.
• 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 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 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.
• Adds support for Microsoft Account (MSA) Pass-through scenarios in Azure Active Directory (AAD) Web Account Manager (WAM).
• 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 might unintentionally add a Trusted Platform Module (TPM) protector when you use the Silent BitLocker enablement policy.
• 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 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 prevents Event 4739 from displaying the new values of certain attributes after a policy change.
• 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 might cause domain joining to fail in environments that use disjoint DNS hostnames.
• 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 prevents you from accessing Server Message Block (SMB) shares using an IP Address when SMB hardening is enabled.
• 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 stop error 0x1E in the SMB Server (srv2.sys).
• 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.
• Addresses a known issue that might cause some devices to receive error messages on a blue screen when those devices are paired to Bluetooth devices. This issue occurs when certain configuration service provider (CSP) policies are in place that affect the Bluetooth A2dp profile.

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 - 19042.1613, 19043.1613, and 19044.1613

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

Symptoms	Workaround
Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later. Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the SSU and latest cumulative update (LCU) without any extra steps.	To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the SSU: Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab <destination path> Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path> You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU. If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business.
After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING".	For more information and a workaround, see KB5005322.
After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red.	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 non-managed personal 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, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Group Policy installation files: Windows Server 2022 Windows 10, version 2004, Windows 10, version 20H2, Windows 10, version 21H1, and Windows 10, version 21H2 Important Verify that you are using the correct Group Policy for your version of Windows.
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	We are working on a resolution and will provide an update in an upcoming release.

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). For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.

Prerequisite:

For Windows Server Update Services (WSUS) deployment or when installing the standalone package from Microsoft Update Catalog:

If your devices do not have the May 11, 2021 update (KB5003173) or later LCU, you must install the special standalone August 10, 2021 SSU (KB5005260).

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

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

Source: https://support.microsoft.com/en-us/...3-75339bc107a1


Direct download links for KB5011543 MSU file from Microsoft Update Catalog:

Download KB5011543 MSU for Windows 10 v20H2, v21H1, and v21H2 32-bit (x86) - 309.6 MB

Download KB5011543 MSU for Windows 10 v20H2, v21H1, and v21H2 64-bit (x64) - 661.0 MB

Download KB5011543 MSU for Windows 10 v20H2, v21H1, and v21H2 ARM64 - 689.7 MB


UUP Dump:

32-bit ISO download: Select language for Feature update to Windows 10, version 21H2 (19044.1620) x86 - UUP dump

64-bit ISO download: Select language for Feature update to Windows 10, version 21H2 (19044.1620) amd64 - UUP dump

ARM64 ISO download: Select language for Feature update to Windows 10, version 21H2 (19044.1620) arm64 - UUP dump

UUP Dump - Download Windows Insider ISO Tutorial | Windows 11 Forum

Posted By: Brink
22 Mar 2022