KB5010342

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:

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

2. Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path>

3. 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:

1. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Bluetooth\

2. 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:

1. Open Group Policy Editor and go to Local Computer Policy or the Domain policy on your domain controller.

2. Then go to Administrative Templates > KB5009596 Issue 001 Rollback > Windows 10, versions 2004, 20H2, and 21H1, and set it to "Disabled".

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

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