Windows 10 21H2 and 22H2 Known Issues and Workarounds – April 28, 2024

In this article, we’ll discuss about all known issues present in two feature updates for Windows 10 operating system: 2021 Update (21H2) and 2022 Update (22H2).

These feature updates added lots of new features, improvements and fixes to Windows 10 but some known issues were also discovered in these updates by many users while installing the updates in their computer systems. These issues can block or restrict users from upgrading their Windows 10 devices to the new feature updates.

Microsoft has officially acknowledged some known issues in Windows 10 21H2 and 22H2 updates and in this article, we are going to discuss about those known issues and workarounds or solutions to fix or bypass those issues.

We’ll also list all previous known issues which have been resolved or fixed by Microsoft.

ISSUE: Edge Updates might Cause Microsoft Copilot App to Show up in Installed Apps

Date: April 26, 2024

Details: Updates to Edge browser version 123.0.2420.65, released on March 28, 2024 and later, might incorrectly install a new package (MSIX) called ‘Microsoft chat provider for Copilot in Windows’ on Windows devices. Resulting from this, the Microsoft Copilot app might appear in the Installed apps in Settings menu.

It is important to note that the Microsoft chat provider for Copilot in Windows does not execute any code or process, and does not acquire, analyze, or transmit device or environment data in any capacity.

This package is intended to prepare some Windows devices for future Windows Copilot enablement and is not intended for all devices. Although the component installed as part of this issue can cause the Microsoft Copilot app to be shown as part of the Installed apps, this component does not fully install or enable Microsoft Copilot.

As part of the upcoming resolution of this issue, the chat provider for Copilot in Windows component will be removed from devices where Microsoft Copilot is not intended to be enabled or installed. This includes most Windows Server devices.

Note: Edge browser version 124.0.2478.51, released on April 18, 2024, contains a change by which the chat provider for Copilot in Windows will not continue to be installed on every device.

Status: Mitigated

Workaround or Fix: More details about the issue are available in our exclusive article. Microsoft is working on a resolution for all affected clients and servers. An upcoming version of Microsoft Edge is expected to remove or adjust the installation of this component on specific devices.

Resolution: This issue is now resolved with Edge browser updates released on April 26, 2024. Edge version 124.0.2478.67 removes the package ‘Microsoft chat provider for Copilot in Windows’ from all servers affected by this issue. The ‘Microsoft Copilot’ entry will not show in the Installed apps list in the Settings menu once the Edge browser is updated. An upcoming version of Microsoft Edge is expected to remove or adjust the installation of this component on specific client devices.

ISSUE: Enterprise Customers might be Unable to Use Microsoft Connected Cache

Date: April 05, 2024

Details: After installing the January 2024 non-security update (KB5034203), released January 23, 2024, or later updates, some Windows devices which use the DHCP Option 235 for discovery of Microsoft Connected Cache (MCC) nodes in their network might be unable to use the MCC nodes. Instead, these Windows devices will download updates and apps from the public internet and IT administrators would see increased download traffic on their internet routes. Home users of Windows are unlikely to experience this issue, as Microsoft Connected Cache configured via DHCP Option 235 is more commonly used in enterprise environments.

Status: Mitigated

Workaround or Fix 1: Configure Microsoft Connected Cache endpoint in DOCacheHost policy as indicated in Cache hostname. Additionally, DOCacheHostSource has to be set to 1 or removed as indicated in Cache hostname source. Note that by default, the DOCacheHost and DOCacheHostSource policies have no value.

Workaround or Fix 2: This issue can also be mitigated using Group Policies available through Microsoft support channel. Organizations can request help through Support for business.

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

ISSUE: Desktop Icons might Move Unexpectedly between Monitors

Date: February 07, 2024

Details: Windows devices using more than one (1) monitor might experience issues with desktop icons moving unexpectedly between monitors or other icon alignment issues when attempting to use Copilot in Windows (in preview). To prevent users from encountering this issue, Copilot in Windows might not be available on devices that have been used or are currently being used in a multi-monitor configuration. You might also not be able to update to Windows 11, version 23H2 as Microsoft has applied a compatibility hold on devices encountering this issue. If your organization is using Windows Update for Business reports, the safeguard ID is 47615939.

Microsoft recommends that you do not attempt to manually update to Windows 11, version 23H2 using the Update now button or the Media Creation Tool until this issue has been resolved and the safeguard removed.

Status: Confirmed

Workaround or Fix: Microsoft is working on a resolution and will provide an update in an upcoming release.

Safeguard Resolution: This issue was resolved on the service-side for Windows 11, version 23H2 on devices with updates released January 9, 2024 or later. Non-managed consumer Windows devices with no other compatibility hold should now have Copilot for Windows available. The safeguard hold has been removed as of February 7, 2024. Eligible Windows 10 and Windows 11 devices with no other safeguards should now be able to upgrade to Windows 11, version 23H2. Please note, it can take up to 48 hours before the update to Windows 11, version 23H2 is offered. Restarting your device might help it offer faster. Note: Managed devices in your environment that have been used or are currently being used in a multi-monitor configuration will not yet have Copilot for Windows available.

ISSUE: The January 2024 Windows RE update might fail to install

Date: January 12, 2024

Details: Devices attempting to install the January 2024 Windows Recovery Environment update (KB5034441) might display an error related to the size of the Recovery Environment’s partition. The Windows Recovery Environment (WinRE) is used to repair or recover from issues affecting Windows. Resulting from this error, the following message might be displayed:

0x80070643 – ERROR_INSTALL_FAILURE

Status: Confirmed

Workaround or Fix: It might be necessary to increase the size of the WinRE partition in order to avoid this issue and complete the installation. Note that 250 megabytes of free space is required in the recovery partition. More information and guidance to change the WinRE partition size can be found in following article:

Fix 0x80070643 Error Code from KB5034441 Update in Windows 10

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

ISSUE: Devices with Locale Set to Croatia might not Utilize the Expected Currency

Date: October 31, 2023

Details: The correct default currency might not display or be used in Windows devices which have locale set to Croatia. This can affect applications which retrieve the device’s currency for purchases or other transactions. Earlier this year, Croatia joined the Eurozone, changing its currency from the Kuna to Euro. Windows Locale data for Croatia will be updated for this change in the short term.

Status: Confirmed

Workaround or Fix: Users can change the currency manually using the Windows Control Panel or directly using intl.cpl command.

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

FIXED: Known Issues in Windows 10 21H2 and 22H2 which have been Resolved

Following known issues have been resolved in Windows 10 21H2 and 22H2 feature updates:

ISSUE: BitLocker might Incorrectly Receive a 65000 Error in MDMs

Date: April 26, 2024

Details: Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the “Require Device Encryption” setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or “Enforce drive encryption on fixed drives” policies set to enabled and selecting either “full encryption” or “used space only”. Microsoft Intune is affected by this issue but third-party MDMs might also be affected. Important: This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.

Status: Resolved

Workaround or Fix: To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or “Enforce drive encryption on fixed drives” policies to not configured.

Resolution: This issue was resolved by Windows updates released January 23, 2024 (KB5034203), and later. It contains important improvements and issue resolutions, including this one.

ISSUE: Sysprep might Fail after Installing Updates Released November 30, 2023 and Later

Date: April 04, 2024

Details: After installing updates released November 30, 2023 (KB5032278 or later), some Windows devices might be unable to complete preparation using System Preparation Tool (Sysprep.exe) due to issues with the status of a Microsoft Edge package. Affected Windows devices will receive a 0x80073cf2 error code in the setupact.log.

Status: Resolved

Workaround or Fix: To verify if your device is affected by this issue and how to apply the mitigation, check this help page.

Resolution: This issue was resolved in updates released March 26, 2024 (KB5035941) and later.

ISSUE: Printer Names and Icons might be Changed and HP Smart App Automatically Installs

Date: December 22, 2023

Details: Some issues related to printer configurations are being observed on Windows devices which have access to the Microsoft Store. Microsoft is investigating this issue and coordinating with partners on a solution. Symptoms can include the following:

• Some Windows 10 and Windows 11 devices are installing the HP Smart App.
• Printers are renamed as HP printers regardless of their manufacturer. Most are being named as the HP LaserJet M101-M106 model. Printer icons might also be changed.
• Double clicking on a printer displays the on-screen error “No tasks are available for this page”.

According to Microsoft’s investigation, this issue is not caused by an HP update. In most cases, it should be possible to use the printer as expected, including queueing printing jobs, as well as other features such as copy, scan, or fax. Printers on the device will continue to use the expected drivers for printer operations. However, this issue might affect associations with other manufacturer-supplied printer apps used to extend basic printer capabilities. If this is the case, some or all of those extended functions might not work.

Status: Resolved

Resolution: You can resolve this issue by downloading and executing one of the files listed in the article KB5034510 Printer Metadata Remediation Tool. In addition to this tool, a critical troubleshooter is being gradually rolled out to all affected Home and non-managed business devices. Critical troubleshooting happens automatically in the background and won’t get in the way of using your device.

We’ll keep updating this page whenever a new known issue is found. Keep checking this page regularly.

Also Check:

[Tip] Disable Windows 10 21H2 Automatic Upgrade to 22H2

How to Disable Windows 11 Automatic Upgrade in Windows 10

[Tip] Direct Download Links of Windows 10 Offline ISO Files

[Guide] Things to Do After Installing Feature Update in Windows 10

How to Prevent or Skip Feature Update Installation in Windows 10