February 15, 2022—KB5010415 (OS Builds 19042.1566, 19043.1566, and 19044.1566) 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! Provides the ability to share cookies between Microsoft Edge IE mode and Microsoft Edge.
Updates an issue that causes Microsoft Edge IE mode to stop working when you press the F1 key.
Updates an issue that affects dialog boxes in Microsoft Edge IE mode.
Updates an issue that causes screen readers to describe a back button as "button" rather than "back button".
Updates an issue that sometimes causes the Chinese Simplified Input Method Editor (IME) to become completely unusable.

Improvements

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

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.
Introduces support for Windows Hello for Business Cloud Trust. This is a new deployment model for hybrid deployments of Windows Hello for Business. It uses the same technology and deployment steps that support on-premises single sign-on (SSO) for Fast IDentity Online (FIDO) security keys. Cloud Trust removes the public-key infrastructure (PKI) requirements for deploying Windows and simplifies the Windows Hello for Business deployment experience.

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.

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

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

New! Provides the ability to share cookies between Microsoft Edge IE mode and Microsoft Edge.
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 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 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 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 an issue that fails to show the Startup impact values in Task Manager.
Addresses an issue that affects OpenGL and GPU reparenting in indirect display scenarios.
Addresses an issue that prevents ShellWindows() from returning the InternetExplorer object when iexplore.exe runs in the Microsoft Edge IE mode context.
Addresses an issue that affects dialog boxes in Microsoft Edge IE mode.
Addresses an issue that causes Microsoft Edge IE mode to stop working when you press the F1 key.
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 might cause a device to stop working when you use more than 50 window trees.
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 affects applications that are written to only integrate with Azure Active Directory (AAD). These applications will not work on machines that are joined to Active Directory Federation Services (ADFS).
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 a remaining issue that might cause the Get-TPM PowerShell command to fail when it attempts to report Trusted Platform Module (TPM) information. The command fails with the error, “0x80090011 Microsoft.Tpm.Commands.TpmWmiException,Microsoft.Tpm.Commands.GetTpmCommand”.
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 causes a mismatch between a Remote Desktop session’s keyboard and the Remote Desktop Protocol (RDP) client when signing in.
Addresses an issue that sometimes causes the Chinese Simplified Input Method Editor (IME) to become completely unusable.
Addresses an issue that causes screen readers to describe a back button as "button" rather than "back button".
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 disconnects Offline Files on the network drive after you restart the OS and sign in. This issue occurs if the Distributed File System (DFS) path is mapped to the network drive.
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 an issue that displays the authentication dialog twice when you mount a network drive.
Addresses a memory leak in the Redirected Drive Buffering Subsystem (RDBSS) and the mrxsmb.sys drivers.
Addresses an issue that causes a deadlock in the WebDav redirector. This issue occurs when you attempt to read a file from the local TfsStore, which causes the system to stop responding.
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 - 19042.1525, 19043.1525, and 19044.1525

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.

When attempting to reset a Windows device with apps that have folders with reparse data, such as OneDrive or OneDrive for Business, files which have been downloaded or synced locally from OneDrive might not be deleted when selecting the “Remove everything” option. This issue might be encountered when attempting a manual reset initiated within Windows or a remote reset. Remote resets might be initiated from Mobile Device Management (MDM) or other management applications, such as Microsoft Intune or third-party tools. OneDrive files that are “cloud only” or have not been downloaded or opened on the device are not affected and will not persist, as the files are not downloaded or synced locally. Note Some device manufacturers and some documentation might call the feature to reset your device, "Push Button Reset", "PBR", "Reset This PC", "Reset PC", or "Fresh Start".	This issue was addressed in KB5011487. Some devices might take up to seven (7) days after the installation of KB5011487 to fully address the issue and prevent files from persisting after a reset. For immediate effect, you can manually trigger Windows Update Troubleshooter using the instructions in Windows Update Troubleshooter. If you are part of an organization that manages devices or prepared OS images for deployment, you can also address this issue by applying a compatibility update for installing and recovering Windows. Doing that makes improvements to the "safe operating system" (SafeOS) that is used to update the Windows recovery environment (WinRE). You can deploy these updates using the instructions in Add an update package to Windows RE using KB5012419 for Windows 10, version 21H2, Windows 10, version 21H1, and Windows 10, version 20H2. Important If devices have already been reset and OneDrive files have persisted, you must use a workaround above or perform another reset after applying one of the workarounds above.
Some organizations that have Windows devices paired to Bluetooth devices might receive the error message, "Your device ran into a problem and needs to restart.” and the stop code, ”IRQ NOT LESS OR EQUAL." This issue occurs after installing KB5009596 or later updates, and the messages appear on a blue screen. The errors are in the System log in Event Viewer as, "Microsoft-Windows-WER-SystemErrorRe event 1001" and the text, "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a" appears. This issue occurs in one of the following scenarios when certain configuration service provider (CSP) policies are in place that affect the Bluetooth A2dp profile: The issue occurs during restart at the end of the update installation process if the Windows client device was previously paired with a mobile phone or other audio devices using Bluetooth. After updates are installed when users pair their updated Windows client device with a new mobile phone or audio device using Bluetooth. In the Windows Update history section of the Settings app, the text, "Failed to install on <date> - 0x800f0845" might appear after you roll back the update because it started up to an error after installation. CSP policies are not common outside of enterprise environments. We do not expect this issue to affect home users and personal devices.	This issue is addressed in KB5011543. If you install an update released March 22 2022 or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to address this issue. If you are using an update released before March 22, 2022, you can address this issue using a KIR and the information below. Important This mitigation contains information about modifying the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, see How to back up and restore the registry in Windows. To mitigate this issue, IT administrators that use Intune or other tools can modify the Windows registry using the steps below: Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Bluetooth\ Add the following registry entry: {0000110a-0000-1000-8000-00805f9b34fb} and {0000110b-0000-1000-8000-00805f9b34fb} to the ServicesAllowedList value Note If you have already installed the update and the blue screen error message appears during the device's restart, open Windows in SafeOS mode to add the registry entry. This issue is addressed using a Known Issue Rollback (KIR). This KIR will not propagate to devices automatically. Devices that have installed an affected update and encountered this issue can address it by installing and configuring a special Group Policy. After you download and install the special Group Policy, configure it using the following steps: Open Group Policy Editor and go to Local Computer Policy or the Domain policy on your domain controller. Then go to Administrative Templates > KB5009596 Issue 001 Rollback > Windows 10, versions 2004, 20H2, and 21H1, and set it to "Disabled". Restart the affected device. Note If you are setting this on a domain controller, you must wait for the Group Policy to propagate and then restart the affected devices. You don’t need to restart the domain controller after installing this KIR Group Policy. Allow Group Policy to refresh on the affected devices before installing the affected Windows update. For more information about deployment, see How to use Group Policy to deploy a Known Issue Rollback.
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 KB5014023.
We are receiving reports that the Snip & Sketch app might fail to capture a screenshot and might fail to open using the keyboard shortcut (Windows key+shift+S). This issue occurs after installing KB5010342 (February 8, 2022) and later updates.	This issue is addressed in KB5014666.

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.

When attempting to reset a Windows device with apps that have folders with reparse data, such as OneDrive or OneDrive for Business, files which have been downloaded or synced locally from OneDrive might not be deleted when selecting the “Remove everything” option. This issue might be encountered when attempting a manual reset initiated within Windows or a remote reset. Remote resets might be initiated from Mobile Device Management (MDM) or other management applications, such as Microsoft Intune or third-party tools. OneDrive files that are “cloud only” or have not been downloaded or opened on the device are not affected and will not persist, as the files are not downloaded or synced locally.

Note Some device manufacturers and some documentation might call the feature to reset your device, "Push Button Reset", "PBR", "Reset This PC", "Reset PC", or "Fresh Start".

This issue was addressed in KB5011487. Some devices might take up to seven (7) days after the installation of KB5011487 to fully address the issue and prevent files from persisting after a reset. For immediate effect, you can manually trigger Windows Update Troubleshooter using the instructions in Windows Update Troubleshooter. If you are part of an organization that manages devices or prepared OS images for deployment, you can also address this issue by applying a compatibility update for installing and recovering Windows. Doing that makes improvements to the "safe operating system" (SafeOS) that is used to update the Windows recovery environment (WinRE). You can deploy these updates using the instructions in Add an update package to Windows RE using KB5012419 for Windows 10, version 21H2, Windows 10, version 21H1, and Windows 10, version 20H2.

Important If devices have already been reset and OneDrive files have persisted, you must use a workaround above or perform another reset after applying one of the workarounds above.

Some organizations that have Windows devices paired to Bluetooth devices might receive the error message, "Your device ran into a problem and needs to restart.” and the stop code, ”IRQ NOT LESS OR EQUAL." This issue occurs after installing KB5009596 or later updates, and the messages appear on a blue screen. The errors are in the System log in Event Viewer as, "Microsoft-Windows-WER-SystemErrorRe event 1001" and the text, "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a" appears.

This issue occurs in one of the following scenarios when certain configuration service provider (CSP) policies are in place that affect the Bluetooth A2dp profile:

The issue occurs during restart at the end of the update installation process if the Windows client device was previously paired with a mobile phone or other audio devices using Bluetooth.
After updates are installed when users pair their updated Windows client device with a new mobile phone or audio device using Bluetooth.

In the Windows Update history section of the Settings app, the text, "Failed to install on <date> - 0x800f0845" might appear after you roll back the update because it started up to an error after installation.

CSP policies are not common outside of enterprise environments. We do not expect this issue to affect home users and personal devices.

This issue is addressed in KB5011543. If you install an update released March 22 2022 or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to address this issue. If you are using an update released before March 22, 2022, you can address this issue using a KIR and the information below.

Important This mitigation contains information about modifying the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, see How to back up and restore the registry in Windows.

To mitigate this issue, IT administrators that use Intune or other tools can modify the Windows registry using the steps below:

Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Bluetooth\
Add the following registry entry: {0000110a-0000-1000-8000-00805f9b34fb} and {0000110b-0000-1000-8000-00805f9b34fb} to the ServicesAllowedList value

Note If you have already installed the update and the blue screen error message appears during the device's restart, open Windows in SafeOS mode to add the registry entry.

This issue is addressed using a Known Issue Rollback (KIR). This KIR will not propagate to devices automatically. Devices that have installed an affected update and encountered this issue can address it by installing and configuring a special Group Policy. After you download and install the special Group Policy, configure it using the following steps:

Open Group Policy Editor and go to Local Computer Policy or the Domain policy on your domain controller.
Then go to Administrative Templates > KB5009596 Issue 001 Rollback > Windows 10, versions 2004, 20H2, and 21H1, and set it to "Disabled".
Restart the affected device.

Note If you are setting this on a domain controller, you must wait for the Group Policy to propagate and then restart the affected devices. You don’t need to restart the domain controller after installing this KIR Group Policy.
Allow Group Policy to refresh on the affected devices before installing the affected Windows update.

For more information about deployment, see How to use Group Policy to deploy a Known Issue Rollback.

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

We are receiving reports that the Snip & Sketch app might fail to capture a screenshot and might fail to open using the keyboard shortcut (Windows key+shift+S). This issue occurs after installing KB5010342 (February 8, 2022) and later updates.

This issue is addressed in KB5014666.

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

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

February 15, 2022—KB5010415 (OS Builds 19042.1566, 19043.1566, and 19044.1566) Preview

Highlights

Improvements

Windows 10 servicing stack update - 19042.1525, 19043.1525, and 19044.1525

Known issues in this update

How to get this update

Need more help?

Want more options?

Was this information helpful?

Thank you for your feedback!

Highlights

Improvements

Windows 10, version 21H2

Windows 10, version 21H1

Windows 10, version 20H2

Windows 10 servicing stack update - 19042.1525, 19043.1525, and 19044.1525

Known issues in this update

Click or tap to view the known issues

How to get this update

Need more help?

Want more options?

Was this information helpful?

Thank you for your feedback!