Windows 10, version 22H2
Find information on known issues and the status of the Windows 10, version 22H2 rollout. For immediate help with Windows update issues, click here if you are using a Windows device to open the Get Help app or go to support.microsoft.com. Follow @WindowsUpdate on X (formerly Twitter) for Windows release health updates. If you are an IT administrator and want to programmatically get information from this page, use the Windows Updates API in Microsoft Graph.
Known issues
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| Edge updates might cause Microsoft Copilot app to show up in Installed apps Edge updates might install a new package and users might see Microsoft Copilot app among the device's Installed apps | N/A | Confirmed | 2024-04-16 20:03 PT |
| Enterprise customers might be unable to use Microsoft Connected Cache This issue affects Windows devices which use the DHCP Option 235 to configure the Microsoft Connected Cache endpoint | OS Build 19045.3996 KB5034203 2024-01-23 | Mitigated | 2024-04-05 11:43 PT |
| Sysprep might fail after installing updates released November 30, 2023 and later Some Windows devices might be unable to use sysprep after installing updates released November 30, 2023 and later. | OS Build 19045.3758 KB5032278 2023-11-30 | Resolved KB5035941 | 2024-04-04 15:37 PT |
| The January 2024 Windows RE update might fail to install WinRE is the Windows Recovery Environment. The update fails if there's insufficient free space in the WinRE partition. | N/A KB5034441 2024-01-09 | Mitigated | 2024-02-09 17:04 PT |
| Desktop icons might move unexpectedly between monitors This issue is only observed if you are using more than one monitor when attempting to use Copilot in Windows. | OS Build 19045.3758 KB5032278 2023-11-30 | Confirmed | 2024-02-08 17:03 PT |
| BitLocker might incorrectly receive a 65000 error in MDMs "Requires Device Encryption" might incorrectly report as an error in some managed environments. | N/A | Mitigated | 2023-10-31 10:06 PT |
| Devices with locale set to Croatia might not utilize the expected currency This can affect applications which retrieve the device's currency for purchases or other transactions | N/A | Confirmed | 2023-10-31 10:06 PT |
Issue details
April 2024
Edge updates might cause Microsoft Copilot app to show up in Installed apps
| Status | Originating update | History | Confirmed | N/A | Last updated: 2024-04-16, 20:03 PT Opened: 2024-04-16, 18:23 PT |
|---|
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.
Next steps: We are working on a resolution and will provide an update in an upcoming release of Microsoft Edge.
Affected platforms:
Client: Windows 11, version 23H2, Windows 11, version 22H2, Windows 11, version 21H2, Windows 10, version 22H2
Server: Windows Server 2022
Enterprise customers might be unable to use Microsoft Connected Cache
| Status | Originating update | History | Mitigated | OS Build 19045.3996 KB5034203 2024-01-23 | Last updated: 2024-04-05, 11:43 PT Opened: 2024-04-05, 11:09 PT |
|---|
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.
Workaround:
- Option1: 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.
- Option2: This issue can also be mitigated using Group Policies available through our support channel. Organizations can request help through Support for business.
Next steps: We are working on a resolution and will provide an update in an upcoming release.
Affected platforms:
- Client: Windows 10, version 21H2, Windows 10, version 22H2
- Server: None
January 2024
Sysprep might fail after installing updates released November 30, 2023 and later
| Status | Originating update | History | Resolved KB5035941 | OS Build 19045.3758 KB5032278 2023-11-30 | Resolved: 2024-03-26, 14:00 PT Opened: 2024-01-23, 13:32 PT |
|---|
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 in the setupact.log.
To verify if your device is affected by this issue, see KB5034912: Sysprep error 0x80073cf2 after installing the November 30, 2023 updates or later for Windows 10, version 22H2.
Resolution: This issue was resolved in updates released March 26, 2024 (KB5035941) and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one.
Affected platforms:
- Client: Windows 10, version 22H2
- Server: None
The January 2024 Windows RE update might fail to install
| Status | Originating update | History | Mitigated | N/A KB5034441 2024-01-09 | Last updated: 2024-02-09, 17:04 PT Opened: 2024-01-12, 14:10 PT |
|---|
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"
Important: If your Windows device does not have a recovery environment configured, you do not need this update (KB5034441). In this case, the error can be ignored.
To determine whether your device has a recovery environment configured, inspect the WinRE status by following these steps:
- Open a Command Prompt window (cmd) as admin.
- To check the WinRE status, run reagentc /info. If the WinRE is configured, a "Windows RE status" field will appear in the output, with value "Enabled". If WinRE is not configured, this field will have the value "Disabled".
Workaround: 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. Devices which do not have sufficient free space in the recovery partition can use a script to extend the partition size. A sample script has been provided in the documentation for adding an update package to WinRE, Extend the Windows RE Partition. Guidance to manually change the WinRE partition size can additionally be found in KB5028997: Instructions to manually resize your partition to install the WinRE update.
Next steps: We are working on a resolution and will provide an update in an upcoming release.
Affected platforms:
- Client: Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2
- Server: Windows Server 2022
November 2023
Desktop icons might move unexpectedly between monitors
| Status | Originating update | History | Confirmed | OS Build 19045.3758 KB5032278 2023-11-30 | Last updated: 2024-02-08, 17:03 PT Opened: 2023-11-30, 17:09 PT |
|---|
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 multimonitor configuration. You might also not be able to update to Windows 11, version 23H2 as we have applied a compatibility hold on devices encountering this issue.
If your organization is using Windows Update for Business reports, the safeguard ID is 47615939.
Next steps: We are working on a resolution for this issue on Windows 10, version 22H2 and will provide an update in an upcoming release.
Safeguard Resolution: This issue was resolved on the service-side for Windows 11, version 23H2 and Windows 11, version 22H2 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 multimonitor configuration will not yet have Copilot for Windows available.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2
- Server: None
October 2023
BitLocker might incorrectly receive a 65000 error in MDMs
| Status | Originating update | History | Mitigated | N/A | Last updated: 2023-10-31, 10:06 PT Opened: 2023-10-09, 14:51 PT |
|---|
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 pe 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.
Workaround: 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.
Next steps: We are working on a resolution and will provide an update in an upcoming release.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10 Enterprise LTSC 2019
- Server: None
February 2023
Devices with locale set to Croatia might not utilize the expected currency
| Status | Originating update | History | Confirmed | N/A | Last updated: 2023-10-31, 10:06 PT Opened: 2023-02-23, 13:22 PT |
|---|
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.
Workaround: Changing the currency in Windows can help. This can be accomplished via the Windows Control Panel.
- Open the "Windows Region" settings. This can be done in one of the following ways:
- Open "Control Panel" from the start menu and select "Change date, time, or number formats" under "Clock and Region"
- On your keyboard, press and hold the Windows key, then press the letter R. This will open the "Run" window. Type INTL.CPL into the Open field,
- In the Region settings, choose one of the 2 locales for Croatia:
- Croatian (Bosnia & Herzegovina)
- Croatian (Croatia)
- In this same window, click the "Additional settings" button. Once there, click the "Currency" tab.
- Change the currency symbol from "KN" to Euro, "€"
Additional information can be seen here: Currency formatting - Globalization | Microsoft Learn.
Manually changing currency might also be an option in some applications. Although this won't change the device’s default currency, this could allow usage of the application with the desired currency preference. Some applications might not allow this manual change. Please view the settings and documentation for your applications.
Next steps: We are working on a resolution and will provide an update in an upcoming release.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 20H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB
- Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1809; Windows Server 2019; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Report a problem with Windows updates
To report an issue to Microsoft at any time, use the Feedback Hub app. To learn more, see Send feedback to Microsoft with the Feedback Hub app.
Need help with Windows updates?
Search, browse, or ask a question on the Microsoft Support Community. If you are an IT pro supporting an organization, visit Windows release health on the Microsoft 365 admin center for additional details.
For direct help with your home PC, use the Get Help app in Windows or contact Microsoft Support. Organizations can request immediate support through Support for business.
View this site in your language
This site is available in 11 languages: English, Chinese Traditional, Chinese Simplified, French (France), German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish (Spain). All text will appear in English if your browser default language is not one of the 11 supported languages. To manually change the display language, scroll down to the bottom of this page, click on the current language displayed on the bottom left of the page, and select one of the 11 supported languages from the list.