Resolved issues in Windows 11, version 22H2
Find information on recently resolved issues for Windows 11, version 22H2. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge). 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.
Resolved issues
| Summary | Originating update | Status | Date resolved |
|---|---|---|---|
| Microsoft is investigating reports of reboot issues Some users reported devices fail to restart after trying to install the September 2024 non-security preview update | OS Build 22621.4249 KB5043145 2024-09-26 | Resolved KB5044285 | 2024-10-08 10:00 PT |
| Devices might boot into BitLocker recovery with the July 2024 security update This issue is more likely to affect devices that have the Device Encryption option enabled | OS Build 22621.3880 KB5040442 2024-07-09 | Resolved KB5041585 | 2024-08-13 10:00 PT |
| CrowdStrike issue impacting Windows endpoints causing an error message Affected systems might restart repeatedly and require recovery operations in order to restore normal use. | N/A | Resolved External | 2024-08-05 16:07 PT |
| The June 2024 preview update might impact applications using Windows Update APIs This issue primarily impacts script callers using Windows Update Agent API to manage Windows Updates. | OS Build 22621.3810 KB5039302 2024-06-25 | Resolved KB5040527 | 2024-07-25 10:00 PT |
| Photos app might fail to start when BlockNonAdminUserInstall is enabled This issue might be observed after device updates the Photos app to version 2024.11050.29009.0 from the Microsoft store | N/A | Resolved | 2024-07-17 13:49 PT |
| Taskbar might not load after installing the June 2024 preview update This issue is only expected to occur in Windows N editions or if the ‘Media Features’ is turned off in Windows Features | OS Build 22621.3810 KB5039302 2024-06-25 | Resolved KB5040442 | 2024-07-09 10:00 PT |
| The June non-security preview update might cause devices to restart repeatedly This issue is more likely to affect devices utilizing virtual machines and nested virtualization features | OS Build 22621.3810 KB5039302 2024-06-25 | Resolved KB5040442 | 2024-07-09 10:00 PT |
| 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 | Resolved | 2024-06-13 14:21 PT |
| VPN connections might fail after installing the April 2024 security update We are investigating user reports, and we will provide more information in the coming days | OS Build 22621.3447 KB5036893 2024-04-09 | Resolved KB5037771 | 2024-05-14 10:00 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 | Resolved KB5034204 | 2024-01-23 14:00 PT |
| Compatibility issues with Intel Smart Sound Technology drivers and Windows 11 Windows 11 devices with the affected Intel SST driver might receive an error with a blue screen. | N/A | Resolved External | 2024-04-12 15:36 PT |
| The February 2024 security update might fail to install Some users reported the update’s download stops at 96% and fails to install on Windows 11 versions 22H2 and 23H2. | OS Build 22621.3155 KB5034765 2024-02-13 | Resolved KB5035853 | 2024-03-12 10:00 PT |
| Some apps might fail to playback, record, or capture video Apps and cameras using WVC1 codec might fail to function as expected. | OS Build 22621.1928 KB5027303 2023-06-27 | Resolved KB5034204 | 2024-01-23 14:00 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 22621.2361 KB5030310 2023-09-26 | Resolved | 2024-02-08 17:03 PT |
| Microsoft received reports about issues connecting to Wi-Fi networks We have confirmed this issue was caused by KB5032288 and KB5033375, released in December 2023 | OS Build 22621.2792 KB5032288 2023-12-04 | Resolved KB5034123 | 2024-01-09 10:00 PT |
| Printer names and icons might be changed and HP Smart app automatically installs In most cases, it is possible to use the printer for printing jobs and other features such as copy, scan, or fax. | N/A | Resolved | 2023-12-22 15:53 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 | Resolved KB5031455 | 2023-10-26 14:00 PT |
Issue details
September 2024
Microsoft is investigating reports of reboot issues
| Status | Originating update | History |
|---|---|---|
| Resolved KB5044285 | OS Build 22621.4249 KB5043145 2024-09-26 | Resolved: 2024-10-08, 10:00 PT Opened: 2024-09-27, 17:30 PT |
Microsoft has received some customer reports of devices restarting multiple times or becoming irresponsive with blue or green screens after trying to install the September 2024 non-security preview Windows update (KB5043145).
According to the reports, some devices automatically open the Automatic Repair tool after repeated reboot attempts. This tool tries to diagnose and resolve common issues that might prevent your device from booting properly. In some cases, BitLocker recovery can also be triggered.
This issue also causes USB and Bluetooth connections to fail in some devices. Hardware connected via USB and Bluetooth, such as keyboards, memory sticks, printers, and wireless mouses, no longer work after installing the update. In these cases, the USB Host Controller under the Device Manager displays a yellow exclamation mark.
Resolution:
This issue was resolved by Windows updates released October 8, 2024 (KB5044285), and later. We recommend you install the latest security update for your device as it contains important improvements and issue resolutions, including this one.
If you have an enterprise-managed device and have installed the update released October 8, 2024 (KB5044285) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before October 8, 2024, and have this issue, your IT administrator can resolve it by installing and configuring the special Group Policy listed below. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> <Group Policy name listed below>.
For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.
Group Policy downloads with Group Policy name:
- Download for Windows 11 23H2 and Windows 11 22H2: Windows 11 22H2 KB5043145 240904_041021 Known Issue Rollback
Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting.
Affected platforms:
- Client: Windows 11, version 23H2, Windows 11, version 22H2
- Server: none
July 2024
Devices might boot into BitLocker recovery with the July 2024 security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5041585 | OS Build 22621.3880 KB5040442 2024-07-09 | Resolved: 2024-08-13, 10:00 PT Opened: 2024-07-23, 13:57 PT |
After installing the July 2024 Windows security update, released July 9, 2024 (KB5040442), you might see a BitLocker recovery screen upon booting your device. This screen does not commonly appear after a Windows update. You are more likely to face this issue if you have the Device Encryption option enabled in Settings under Privacy & Security -> Device encryption. Resulting from this issue, you might be prompted to enter the recovery key from your Microsoft account to unlock your drive.
Resolution: This issue was resolved by Windows updates released August 13, 2024 (KB5041585), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
If you install an update released August 13, 2024 (KB5041585) or later, you do not need to use a workaround for this issue. If you are using an update released before August 13, 2024, and have this issue, your device should proceed to start up normally from the BitLocker recovery screen once the recovery key has been entered. You can retrieve the recovery key by logging into the BitLocker recovery screen portal with your Microsoft account. Detailed steps for finding the recovery key are listed here: Finding your BitLocker recovery key in Windows.
Affected platforms:
- Client: Windows 11 version 23H2, Windows 11 version 22H2, Windows 11 version 21H2, Windows 10 version 22H2, Windows 10 version 21H2, Windows 10 Enterprise 2015 LTSB
- Server: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008
CrowdStrike issue impacting Windows endpoints causing an error message
| Status | Originating update | History |
|---|---|---|
| Resolved External | N/A | Last updated: 2024-08-05, 16:07 PT Opened: 2024-07-19, 07:30 PT |
Microsoft has identified an issue impacting Windows endpoints which are running the CrowdStrike Falcon agent, developed by CrowdStrike Holdings. Following updates released and delivered by CrowdStrike on July 18, 2024, devices running the Falcon agent may encounter an error message on a blue screen and experience a continual restarting state.
Affected systems might restart repeatedly and require recovery operations in order to restore normal use.
Updated July 25, 2024: Microsoft released further guidance on Windows resiliency: Best practices and the path forward. Read more about how we are working in close cooperation to improve resiliency across the Windows ecosystem and explore best practices you can use to support resiliency in your organization.
Updated July 22, 2024: Microsoft has released a third mitigation option for this issue impacting Windows clients and servers. If devices are unable to recover with the two previous options mentioned below, IT admins can use PXE to remediate. See the revised New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints for detailed instructions on prerequisites and configurations to use PXE Recovery.
Updated July 21, 2024: As a follow-up to the CrowdStrike Falcon agent issue impacting Windows clients and servers, Microsoft has released an updated recovery tool with two repair options to help IT admins expedite the repair process. Based on customer feedback, this new release includes a new option for recovery using safe boot, the option to generate ISO or USB, a fix for ADK detection when the Windows Driver Kit is installed, and a fix for the USB disk size check. See the revised New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints for detailed instructions on using the signed Microsoft Recovery Tool.
Updated July 20, 2024: Microsoft has released KB5042426, which contains step-by-step guidance for Windows Servers hosted on-premises that are running the CrowdStrike Falcon agent and encountering a 0x50 or 0x7E error message on a blue screen. We will continue to work with CrowdStrike to provide the most up-to-date information available on this issue.
A new USB Recovery Tool is available to help IT admins expedite the repair process. The new tool can be found in the Microsoft Download Center. Read more about the new recovery tool and usage instructions at New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints.
Updated July 19, 2024: A new Knowledge Base article, KB5042421, with additional step-by-step guidance for Windows 11 and Windows 10 clients is now available. We will continue to work with CrowdStrike to provide up-to-date mitigation information as it becomes available.
To mitigate this issue ahead of additional resolution options, you can follow these steps:
- Start Windows into Safe Mode or the Windows Recovery Environment.
- Navigate to the C:\Windows\System32\drivers\CrowdStrike directory
- Locate the file matching “C-00000291*.sys” and delete it.
- Restart the device.
- Recovery of systems requires a Bitlocker key in some cases.
For Windows Virtual Machines running on Azure follow the mitigation steps in Azure status.
Additional details from CrowdStrike are available here: Statement on Windows Sensor Update - CrowdStrike Blog.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10 Enterprise LTSC 2019
- Server: Windows Server 2022; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
The June 2024 preview update might impact applications using Windows Update APIs
| Status | Originating update | History |
|---|---|---|
| Resolved KB5040527 | OS Build 22621.3810 KB5039302 2024-06-25 | Resolved: 2024-07-25, 10:00 PT Opened: 2024-07-12, 10:04 PT |
After installing the June 2024 Windows preview update, released June 25, 2024 (KB5039302) and later updates, you might face issues using Windows Update Agent API (WUA) from your script (PowerShell, VBScript, etc.) while searching for Windows updates. Due to this issue, you might get an empty result when querying the properties of IUpdate objects present in the IUpdateCollection and error code 0x8002802B (TYPE_E_ELEMENTNOTFOUND) when calling methods on the object from your script.
Organizations using Windows Automatic Updates are not impacted by this issue. Home users of Windows using Home or Pro editions are unlikely to face this issue as their devices are managed using Windows Automatic Updates that doesn't run into this issue.
Resolution:
This issue was resolved by Windows updates released July 25, 2024 (KB5040527), and later. We recommend you install the latest update for your device. It contains important improvements and issue resolutions, including this one.
If you install an update released July 25, 2024 (KB5040527) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before July 25, 2024, and have this issue, you can resolve it by installing and configuring the special Group Policy listed below. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> <Group Policy name listed below>.
For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.
Group Policy downloads with Group Policy name:
- Download for Windows 11, versions 23H2 and 22H2 - Windows 11 22H2 KB5039302 240711_20301 Known Issue Rollback
Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting. Note that the Group Policy will temporarily disable the change causing the script issue.
Affected platforms:
- Client: Windows 11 version 23H2, Windows 11 version 22H2
- Server: None
June 2024
Photos app might fail to start when BlockNonAdminUserInstall is enabled
| Status | Originating update | History |
|---|---|---|
| Resolved | N/A | Resolved: 2024-07-17, 13:49 PT Opened: 2024-06-18, 10:14 PT |
If your device has updated the Microsoft Photos app from the Windows store on or after June 4, 2024 (version 2024.11050.29009.0 and above), you might face issues starting the application. On launching the app, it might display a spinning circle, after which it might disappear. If you have the Procmon monitoring tool installed in your device, this error might display as Access Denied error on Process Exit (‘Exit Status: -2147024891’).
This issue is most likely to occur if you have enabled either the Prevent non-admin users from installing packaged Windows apps policy or its Configuration Service provider (CSP) equivalent policy, BlockNonAdminUserInstall.
Users with Windows Home edition are unlikely to experience this issue, as the policies which may cause this issue to happen are less likely to be applied in home environments.
Resolution:
This issue was resolved by Photos app version 2024.11070.15005.0 and newer, released to the Microsoft Store on July 17, 2024. Windows devices will automatically download the updated Photos application over the following weeks without user or admin interaction. You can also download the latest version of the Photos application immediately either by visiting the Microsoft Photos app page or by selecting Get updates option from the Microsoft Store.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2
- Server: None
Taskbar might not load after installing the June 2024 preview update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5040442 | OS Build 22621.3810 KB5039302 2024-06-25 | Resolved: 2024-07-09, 10:00 PT Opened: 2024-06-28, 13:14 PT |
After installing the June 2024 Windows preview update (KB5039302), released June 25, 2024, you are likely to face issues with the Taskbar. This issue is only expected to occur if you are using a Windows N edition device or if you turn off the ‘Media Features’ via Control Panel->Programs-> Programs and Features -> Turn Windows features on or off. N editions of Windows include the same functionality as other editions of Windows, except for media-related technologies, Windows Media Player, and certain preinstalled media apps.
You might not be able to view or interact with the Taskbar after logging in to your device once the update is installed. Other applications like File Explorer, Desktop and Settings will continue to work.
Resolution: This issue was resolved by Windows updates released July 9, 2024 (KB5040442), 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 11 version 23H2, Windows 11 version 22H2
- Server: None
The June non-security preview update might cause devices to restart repeatedly
| Status | Originating update | History |
|---|---|---|
| Resolved KB5040442 | OS Build 22621.3810 KB5039302 2024-06-25 | Resolved: 2024-07-09, 10:00 PT Opened: 2024-06-26, 19:25 PT |
After installing updates released June 26, 2024 (KB5039302), some devices might fail to start. Affected systems might restart repeatedly and require recovery operations in order to restore normal use.
This issue is more likely to affect devices utilizing virtual machines tools and nested virtualization features, such as CloudPC, DevBox, Azure Virtual Desktop. We are investigating to determine the precise conditions under which this issue can trigger.
Availability of this update via Windows Update and Windows Update for Business was paused for a couple of days, but is being resumed today for most devices. This update offering is now paused only for devices affected by the issue. As a result, this update might not be offered to Hyper-V virtual machines running on hosts that utilize certain processor types.
Users of Windows Home edition are less likely to experience this issue, as virtualization is less common in home environments.
Resolution: This issue was resolved in updates released July 9, 2024 (KB5040442) 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 11, version 23H2; Windows 11, version 22H2
- Server: None
April 2024
Edge updates might cause Microsoft Copilot app to show up in Installed apps
| Status | Originating update | History |
|---|---|---|
| Resolved | N/A | Resolved: 2024-06-13, 14:21 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 was intended to prepare some Windows devices for future Windows Copilot enablement and was 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.
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.
Resolution: This issue is now resolved with Edge browser updates released on April 26, 2024, and June 13, 2024. Edge version 124.0.2478.67 was released on April 26 and removed the package ‘Microsoft chat provider for Copilot in Windows’ from all servers affected by this issue. Edge version 126.0.2592.56 was released on June 13, 2024, and removed the same package from all Windows client versions 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.
Affected platforms:
Client: Windows 11, version 23H2, Windows 11, version 22H2, Windows 11, version 21H2, Windows 10, version 22H2
Server: Windows Server 2022
VPN connections might fail after installing the April 2024 security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5037771 | OS Build 22621.3447 KB5036893 2024-04-09 | Resolved: 2024-05-14, 10:00 PT Opened: 2024-04-30, 20:15 PT |
Windows devices might face VPN connection failures after installing the April 2024 security update (KB5036893) or the April 2024 non-security preview update.
Resolution: This issue was resolved by Windows updates released May 14, 2024 (KB5037771), 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 11, version 23H2; Windows 11, version 22H2, Windows 11, version 21H2, Windows 10, version 22H2, Windows 10, version 21H2.
Server: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008.
February 2024
The February 2024 security update might fail to install
| Status | Originating update | History |
|---|---|---|
| Resolved KB5035853 | OS Build 22621.3155 KB5034765 2024-02-13 | Resolved: 2024-03-12, 10:00 PT Opened: 2024-02-26, 12:58 PT |
Windows 11 devices attempting to install the February 2024 security update, released February 13, 2024 (KB5034765), and the non-security preview update, released February 29, 2024 (KB5034848), might face issues during the update process. The installation might fail when the update's download reaches 96% of completion, and the device might roll back to the previous update installed.
Resulting from this error, the following message might be displayed:
- “Something didn’t go as planned. No need to worry – undoing changes. Please keep your computer on”.
This issue might be reflected in the Windows Event Viewer with error code ‘0x800F0922’.
Resolution: This issue was resolved in updates released March 12, 2024 (KB5035853) and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one.
If you are using an update released before March 12, 2024, and have this issue, you can resolve it by applying the workaround listed below.
Workaround:
This issue can be prevented by deleting the hidden folder C:\$WinREAgent. A restart might be required. After following these steps, installing the February 2024 security update should succeed.
Below are two possible ways to delete the C:\$WinREAgent folder.
1) Manually delete the folder: To delete a hidden folder in Windows 11, you need to first make the folder visible and then delete it.
- Open File Explorer from the Taskbar, or by pressing Windows key + E.
- Click on the three-dotted icon and select Options.
- Go to the View tab and select the Show hidden files, folders, and drives option. Click the OK button to save the change.
- Now, you should be able to see the hidden folder C:\$WinREAgent in File Explorer. Right-click the hidden folder C:\$WinREAgent and select Delete.
2) Run a script to delete the folder:
- Open the start menu and type command prompt.
- From the results displayed at the right side of the start menu, select ‘Run as administrator’.
- On the command prompt, type the command rd /s /q "C:\$WinREAgent" and press enter.
- If no message is displayed, it means the command has succeeded and the folder has been deleted. You can proceed to close the command prompt window.
- Note that a message is only displayed if an error was encountered. In this case, we recommend deleting the folder manually.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2
- Server: None
December 2023
Microsoft received reports about issues connecting to Wi-Fi networks
| Status | Originating update | History |
|---|---|---|
| Resolved KB5034123 | OS Build 22621.2792 KB5032288 2023-12-04 | Resolved: 2024-01-09, 10:00 PT Opened: 2023-12-18, 20:49 PT |
Microsoft has received reports of an issue in which some Wi-Fi adapters might not connect to some networks after installing KB5032288. We have confirmed this issue was caused by KB5032288 and KB5033375. As reported, you are more likely to be affected by this issue if you are attempting to connect to an enterprise, education, or public Wi-Fi network using 802.1x authentication. This issue is not likely to occur on home networks.
Resolution: This issue was resolved in updates released January 9, 2024 (KB5034123) and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one. If you install an update released January 9, 2024 (KB5034123) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before January 9, 2024, and have this issue, you can resolve it by installing and configuring the special Group Policy listed below. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> <Group Policy name listed below>.
For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.
Group Policy downloads with Group Policy name:
- Download for Windows 11, versions 23H2 and 22H2 - Windows 11 22H2 KB5032288 231029_032011 Known Issue Rollback
Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2
- Server: None
Printer names and icons might be changed and HP Smart app automatically installs
| Status | Originating update | History |
|---|---|---|
| Resolved | N/A | Resolved: 2023-12-22, 15:53 PT Opened: 2023-12-04, 18:46 PT |
Some issues related to printer configurations are being observed on Windows devices. Microsoft is investigating this issue and coordinating with partners on a solution.
Symptoms can include the following:
- Some Windows devices are installing the HP Smart app.
- Printers may show LaserJet M101-M106 model information regardless of their manufacturer. Printer icons might also be changed.
- Double clicking on a printer displays the on-screen error "No tasks are available for this page".
Note: Our investigations indicate that 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.
Resolution: You can resolve this issue by downloading and executing one of the files listed in the article KB5034510 Printer Metadata Remediation Tool – December 2023. 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. To learn more about critical and recommended troubleshooters, see Keep your device running smoothly with recommended troubleshooting.
If you need support to resolve this issue, go to https://support.microsoft.com/contactus, and select Windows.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2; 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 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
November 2023
Desktop icons might move unexpectedly between monitors
| Status | Originating update | History |
|---|---|---|
| Resolved | OS Build 22621.2361 KB5030310 2023-09-26 | Resolved: 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.
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 |
|---|---|---|
| Resolved KB5034204 | N/A | Resolved: 2024-01-23, 14:00 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.
Resolution: This issue was resolved by Windows updates released January 23, 2024 (KB5034204), 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 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
July 2023
Some apps might fail to playback, record, or capture video
| Status | Originating update | History |
|---|---|---|
| Resolved KB5034204 | OS Build 22621.1928 KB5027303 2023-06-27 | Resolved: 2024-01-23, 14:00 PT Opened: 2023-07-25, 14:47 PT |
After installing KB5027303 or later updates, some apps might fail to playback, record, or capture video when using the WVC1 codec (VC-1). Certain cameras or webcams might also fail to work if they use the WVC1 codec by default.
Resolution: This issue was resolved in updates released January 23, 2024 (KB5034204) and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one.
If you install an update released January 23, 2024 (KB5034204) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before January 23, 2024, and have this issue, you can resolve it by installing and configuring the special Group Policy listed below. The special Group Policy can be found in Computer Configuration > Administrative Templates > <Group Policy name listed below>.
For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.
Group Policy downloads with Group Policy name:
- Download for Windows 11, version 22H2 - Windows 11 22H2 KB5027303 230528_03453 Known Issue Rollback
- Download for Windows 11, version 21H2 - Windows 11 (original release) KB5028245 230630_032045 Known Issue Rollback
Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 11, version 21H2
- Server: None
February 2023
Devices with locale set to Croatia might not utilize the expected currency
| Status | Originating update | History |
|---|---|---|
| Resolved KB5031455 | N/A | Resolved: 2023-10-26, 14:00 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.
Resolution: This issue was resolved in updates released October 26, 2023 (KB5031455) and later.
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
November 2021
Compatibility issues with Intel Smart Sound Technology drivers and Windows 11
| Status | Originating update | History |
|---|---|---|
| Resolved External | N/A | Last updated: 2024-04-12, 15:36 PT Opened: 2021-11-15, 16:40 PT |
Intel and Microsoft have found incompatibility issues with certain versions of drivers for Intel Smart Sound Technology (Intel SST) on Intel 11th Gen Core processors and Windows 11. Windows 11 devices with the affected Intel SST driver might receive an error with a blue screen. The affected driver is named Intel® Smart Sound Technology (Intel® SST) Audio Controller under System Devices in Device Manager and is found with the file name 'IntcAudioBus.sys'. If this file is version 10.29.0.5152 or 10.30.0.5152, this issue can occur.
Only devices with both an Intel 11th Gen Core processors and an Intel SST driver version of 10.29.0.5152 or 10.30.0.5152 are affected by this issue.
To safeguard your upgrade experience, we have applied a compatibility hold on Windows 10 devices which have Intel SST driver versions 10.29.0.5152 or 10.30.0.5152. This will prevent those devices from being offered any version of Windows 11. If your organization is using Update Compliance, the safeguard IDs are:
- Windows 11, version 21H2: 36899911
- Windows 11, version 22H2: 41291788
- Windows 11, version 23H2: 49561482
Resolution: Devices which are encountering this issue will need to install newer versions of the Intel® SST Audio Controller drivers prior to updating to Windows 11. The issue is resolved by updating the Intel® Smart Sound Technology drivers to version 10.30.00.5714 and later, or 10.29.00.5714 and later. Please note that later versions of this driver might refer to only the last part of the version number. For the purpose of addressing this issue, 10.30.x versions are not newer than 10.29.x versions.
For most users, updated drivers can be installed via Windows update by checking for Windows updates on your device. This is the preferred method of installing these and other drivers. If your device still encounters this safeguard hold 48 hours after updating your drivers, it's possible drivers for this Audio Controller haven't been developed for your specific device hardware configuration. In this case, you will need to contact your device manufacturer (OEM) for more information on the necessary drivers. Microsoft works to make the latest compatible drivers available under Windows Update whenever developers have released them.
IT admins in organizations where devices are managed can refer to the following resources to deploy drivers using one of these tools:
- Windows Update for Business customers: Deploy drivers and firmware updates - Windows Update for Business deployment service
- Intune: Learn about Windows Driver updates policy for Windows 10 Windows 11 devices in Intune
- Autopatch: Manage driver and firmware updates - Windows Deployment
Once you have updated to a compatible version of the Intel® Smart Sound Technology drivers, you should be able to upgrade to Windows 11. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the upgrade to Windows 11 is offered. We recommend that you do not attempt to manually upgrade using the 'Update now' button or the Media Creation Tool until you have performed the necessary driver updates.
Affected platforms:
- Client: Windows 11, version 23H2, Windows 11, version 22H2; Windows 11, version 21H2
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.