Resolved issues in Windows 10, version 22H2
Find information on recently resolved issues for Windows 10, 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 |
|---|---|---|---|
| Users might be unable to update or uninstall packaged apps on Windows 10 This issue impacts users who have received WinAppSDK 1.6.2 package on their Windows 10 devices. | N/A | Resolved KB5046714 | 2024-11-21 10:00 PT |
| Apps that set UIAccess=true might fail to start for non-admin users This issue is due to child processes of these apps running with Integrity level low instead of Integrity level medium | OS Build 19045.4957 KB5043131 2024-09-24 | Resolved KB5046613 | 2024-11-12 10:00 PT |
| Azure Virtual Desktop users might experience black screen during login This issue affects enterprise users with multi-session environments due to issues with AppX Deployment Service | OS Build 19045.4717 KB5040525 2024-07-23 | Resolved KB5045594 | 2024-10-22 10:00 PT |
| AVD users might experience extended black screen during logon and SSO failures This issue affects enterprise users using FSLogix user profile containers on multi-session environments. | OS Build 19045.4717 KB5040525 2024-07-23 | Resolved KB5045594 | 2024-10-22 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 19045.4651 KB5040427 2024-07-09 | Resolved KB5041580 | 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 |
| 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 KB5037768 | 2024-05-14 10:00 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 | Resolved KB5040525 | 2024-07-23 10: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 19045.3758 KB5032278 2023-11-30 | Resolved | 2024-06-28 16:15 PT |
| Apps show "Open With" dialog when right-clicking on Taskbar or Start menu icons You might experience this when right-clicking an app icon shown in your Taskbar or Start menu to execute a task. | OS Build 19045.4355 KB5036979 2024-04-23 | Resolved KB5039299 | 2024-06-25 14: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 19045.4291 KB5036892 2024-04-09 | Resolved KB5037768 | 2024-05-14 10:00 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 | Resolved | 2024-04-30 14:07 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 KB5034203 | 2024-01-23 10:00 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-03-26 14: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 19045.30000 KB5028244 2023-07-25 | Resolved | 2024-02-28 11:09 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 |
Issue details
November 2024
Users might be unable to update or uninstall packaged apps on Windows 10
| Status | Originating update | History |
|---|---|---|
| Resolved KB5046714 | N/A | Resolved: 2024-11-21, 10:00 PT Opened: 2024-11-20, 19:54 PT |
Starting November 12, 2024, Windows 10 users might experience issues while trying to update or uninstall packaged apps. Affected Windows 10 devices have received the WinAppSDK 1.6.2 package (published on November 12, 2024). When users download an app that relies on WinAppSDK, the necessary components of the SDK are automatically downloaded and installed along with the app.
Resulting from this issue, you might observe that Microsoft Store displays the error message, ‘Something happened on our end’ in the ‘Downloads’ panel.
If you are an IT administrator trying to manage packaged apps through PowerShell using ‘Get-AppxPackage’ command you might observe the error ‘Deployment failed with HRESULT: 0x80073CFA’, ‘Please contact your software vendor. (Exception from HRESULT: 0x80073CFA’) in PowerShell.
You will also notice that apps like Microsoft Teams and other 3rd party apps are impacted if you choose to uninstall and re-install the apps as part of the update process.
Please note, this issue is not caused by a Windows security or preview monthly update.
Resolution: This issue was resolved by Windows updates released November 21, 2024 (KB5046714), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
Affected platforms:
- Client: Windows 10, version 22H2
- Server: None
AVD users might experience extended black screen during logon and SSO failures
| Status | Originating update | History |
|---|---|---|
| Resolved KB5045594 | OS Build 19045.4717 KB5040525 2024-07-23 | Resolved: 2024-10-22, 10:00 PT Opened: 2024-11-01, 14:11 PT |
A small subset of Azure Virtual Desktop customers using multi-session hosts (AVD) who have installed Windows Updates released between KB5040525 on July 23, 2024, and KB5044273 released October 8, 2024, may experience the following issues:
- An extended 10-to-30-minute-long hang at a black screen following user logon.
- Office applications including Outlook and Teams experience single sign-on (SSO) failures, preventing users from connecting or synchronizing data.
This issue is caused by a deadlock in the interactions between the Azure Active Directory(AAD) broker and the underlying AppX deployment service(AppxSvc) and Background tasks infrastructure service.You are more likely to experience this issue if you are using FSLogix user profile containers on multi-session environments. FSLogix is a Microsoft tool that helps manage and speed up user profiles on computers, especially in virtual environments like remote desktops.
Windows 10 Education edition users and home users of Windows using Home or Pro editions are unlikely to face this issue as Azure Virtual Desktop is more commonly used in enterprise environments.
Resolution:
This issue is resolved by installing the Windows updates released October 22, 2024 (KB5045594) or later updates and by applying one of the options mentioned in the Resolution section in KB5048864. Note that you need to perform both actions to resolve the issue.
Affected platforms:
- Client: Windows 10, version 22H2
- Server: None
October 2024
Apps that set UIAccess=true might fail to start for non-admin users
| Status | Originating update | History |
|---|---|---|
| Resolved KB5046613 | OS Build 19045.4957 KB5043131 2024-09-24 | Resolved: 2024-11-12, 10:00 PT Opened: 2024-10-30, 12:45 PT |
After installing the September 2024 preview update (KB5043131), released September 24, 2024 or later, you might observe that apps such as Quick Assist, Microsoft Teams, Windows Narrator, etc might fail to start if you are a non-admin user. You might experience this issue on any app that sets UIAccess=true while trying to run the app as a non-admin user. The uiAccess=true attribute in an application's manifest file is used to request that the application be granted higher privileges. Apps using this attribute launch from a secure path, such as :
- %ProgramFiles% (including subdirectories)
- %ProgramFiles(x86)% (including subdirectories for 64-bit versions of Windows)
- %systemroot%\system32
- %systemroot%\syswow64 (for 64-bit versions of Windows)
If you have the Procmon monitoring tool installed in your device, you will observe that the application runs with the wrong integrity level, Integrity:Low instead of the expected Integrity:Medium. You are less likely to encounter this issue if you are running the application as an administrator.
Resolution:
This issue was resolved by Windows updates released November 12, 2024 (KB5046613), 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 November 12, 2024 (KB5046613), and 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 November 12, 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 10, version 22H2 – Windows 10 20H2, 21H1, 21H2 and 22H2 KB5041582 241027_11353 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: The below steps apply to enterprise devices that are domain joined.
- Wait for the KIR group policy changes to replicate in Active Directory and the SYSVOL
- Follow one of the steps below before applying the KIR:
- Wait for group policy to refresh in the background then restart your device (or)
- Run ‘gpupdate /force’ from a command prompt then restart your device
Affected platforms:
- Client: Windows 10, version 22H2
- Server: None
Azure Virtual Desktop users might experience black screen during login
| Status | Originating update | History |
|---|---|---|
| Resolved KB5045594 | OS Build 19045.4717 KB5040525 2024-07-23 | Resolved: 2024-10-22, 10:00 PT Opened: 2024-10-14, 11:48 PT |
After installing the July 2024 non-security preview update (KB5040525), released July 23, 2024 or subsequent updates, you might experience a black screen when you login to Azure Virtual Desktop (AVD). You might also notice that you are unable to log out of your account and the black screen persists even after disconnecting and reconnecting to AVD. Resulting from this issue, the application event log in Event viewer will show an application error with Event ID:1000 indicating a fault with the application ‘svchost.exe_AppXSvc’.
Please note that AppX Deployment Service (AppxSvc) being in an invalid state could also cause other symptoms like the Start Menu to close unexpectedly due to registration issues.
Windows 10 Education edition users and home users of Windows using Home or Pro editions are unlikely to face this issue as Azure Virtual Desktop is more commonly used in enterprise environments.
Resolution:
This issue is resolved by installing the Windows updates released October 22, 2024 (KB5045594) or later updates and by applying one of the options mentioned in the Resolution section in KB5048864. Note that you need to perform both actions to resolve the issue.
Affected platforms:
- Client: Windows 10, version 22H2
- Server: None
Click here to manage email notifications for Windows known issues.
July 2024
Devices might boot into BitLocker recovery with the July 2024 security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5041580 | OS Build 19045.4651 KB5040427 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 (KB5040427), 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 (KB5041580), 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 (KB5041580) 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
June 2024
Apps show "Open With" dialog when right-clicking on Taskbar or Start menu icons
| Status | Originating update | History |
|---|---|---|
| Resolved KB5039299 | OS Build 19045.4355 KB5036979 2024-04-23 | Resolved: 2024-06-25, 14:00 PT Opened: 2024-06-17, 09:45 PT |
Following installation of the Windows update released April 23, 2024 (KB5036979)and updates released after that, certain apps might display an "Open With" dialog box asking, "How do you want to open this file?". You might experience this issue when you place your mouse on an app icon shown in your Taskbar or Start menu and right-click on the app to execute a task in that app. Resulting from this, you might see the “Open With” dialog box instead of the execution of the selected task.
This issue was reported by Teams, new Outlook for Windows, and Snip & Sketch users. This issue can also affect other applications attempting to right-click on its icon to find a context menu with a list of tasks.
Workaround: Although the "Open With" dialog prevents the use of the tasks available from the right-click context menu, it's likely that those same operations can be performed by making the application interface visible, and navigating the application interface and menus.
Resolution: This issue was resolved in updates released June 25, 2024 (KB5039299) 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; Windows 10, version 21H2
- Server: None
April 2024
Enterprise customers might be unable to use Microsoft Connected Cache
| Status | Originating update | History |
|---|---|---|
| Resolved KB5040525 | OS Build 19045.3996 KB5034203 2024-01-23 | Resolved: 2024-07-23, 10:00 PT Opened: 2024-04-05, 11:09 PT |
After installing the February 2024 Windows security update (KB5034203), released February 13, 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.
Resolution: This issue was resolved by Windows updates released July 23, 2024 (KB5040525), 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 21H2, Windows 10, version 22H2
- Server: None
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 KB5037768 | OS Build 19045.4291 KB5036892 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 (KB5036892) or the April 2024 non-security preview update.
Resolution: This issue was resolved by Windows updates released May 14, 2024 (KB5037768), 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.
January 2024
The January 2024 Windows RE update might fail to install
| Status | Originating update | History |
|---|---|---|
| Resolved | N/A KB5034441 2024-01-09 | Resolved: 2024-04-30, 14:07 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".
Resolution: Automatic resolution of this issue won't be available in a future Windows update. Manual steps are necessary to complete the installation of this update on devices which are experiencing this error.
The WinRE partition requires 250 megabytes of free space. Devices which do not have sufficient free space will need to increase the size of the partition via manual action. For guidance on making this change, review the following resources:
- A code script can be used to extend the partition size. A sample script has been provided in the documentation for adding an update package to WinRE. See 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.
Completion of these manual steps will allow the installation of this update to succeed.
Affected platforms:
- Client: Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2
- Server: Windows Server 2022
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
December 2023
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 19045.3758 KB5032278 2023-11-30 | Resolved: 2024-06-28, 16:15 PT Opened: 2023-11-30, 17:09 PT |
Windows devices using more than one 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: We are gradually rolling out a new Copilot experience for devices with Windows updates released June 25, 2024 () or later. This new experience will resolve this issue for Windows 10, version 22H2. This update () was released on June 25, 2024, and you can expect to receive the new Copilot experience between now and the coming months.
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 |
|---|---|---|
| Resolved KB5034203 | N/A | Resolved: 2024-01-23, 10: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 (KB5034203), 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 | OS Build 19045.30000 KB5028244 2023-07-25 | Resolved: 2024-02-28, 11:09 PT Opened: 2023-07-25, 14:47 PT |
After further investigation, we concluded that this issue was not applicable to Windows 10, version 22H2. It affected only Windows 11, versions 22H2 and 21H2. The content below was published prior to this finding and has been edited on February 27, 2024. This issue can be disregarded by Windows 10 users.
To learn about the impact of this issue for Windows 11, select from the links below:
After installing KB5028244 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.
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 KB5037768 | N/A | Resolved: 2024-05-14, 10: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 May 14, 2024 (KB5037768) and later. We recommend you install the latest security update for your device as 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, 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.