Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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 |
|---|---|---|---|
| KB5058405 might fail to install with recovery error 0xc0000098 in ACPI.sys Windows 11, 22H2 and 23H2 might fail to start with error 0xc0000098 in ACPI.sys while installing KB5058405 | OS Build 22621.5335 KB5058405 2025-05-13 | Resolved KB5062170 | 2025-05-31 14:30 PT |
| August 2024 security update might impact Linux boot in dual-boot setup devices This issue might impact devices with dual-boot setup for Windows and Linux when SBAT setting is applied | OS Build 22621.4037 KB5041585 2024-08-13 | Resolved KB5058405 | 2025-05-13 10:00 PT |
| Windows 11, version 24H2 might not download via Windows Server Updates Services Devices with April 2025 security update fail to download, showing error 0x80240069 | OS Build 22621.5189 KB5055528 2025-04-08 | Resolved KB5058405 | 2025-05-13 10:00 PT |
| USB printers might print random text with the January 2025 preview update This issue is observed with USB dual-mode printers that support both USB Print and IPP Over USB protocols. | OS Build 22621.4830 KB5050092 2025-01-29 | Resolved KB5053657 | 2025-03-25 10:00 PT |
| 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 |
Issue details
May 2025
KB5058405 might fail to install with recovery error 0xc0000098 in ACPI.sys
| Status | Originating update | History |
|---|---|---|
| Resolved KB5062170 | OS Build 22621.5335 KB5058405 2025-05-13 | Resolved: 2025-05-31, 14:30 PT Opened: 2025-05-28, 12:08 PT |
While installing the May Windows security update (KB5058405) on the Windows versions listed below, some devices might encounter the following recovery error:
Your PC/Device needs to be repaired The operating system couldn't be loaded because a required file is missing or contains errors. File: ACPI.sys Error code: 0xc0000098
This issue has been observed on a small number of physical devices, but primarily on devices running in virtual environments, including:
- Azure Virtual Machines
- Azure Virtual Desktop
- On-premises virtual machines hosted on Citrix or Hyper-V
Home users of Windows Home or Pro editions are unlikely to face this issue, as virtual machines are mostly used in IT environments.
The ACPI.sys file (Advanced Configuration and Power Interface) is a critical Windows system driver that enables Windows to manage hardware resources and power states. Note: There are also reports of this same error occurring with a different file name.
Resolution:
This issue is resolved in the out-of-band (OOB) update KB5062170, which is only available via the Microsoft Update Catalog. If you experienced this issue, or if you have not yet deployed the May 2025 Windows security update on the Windows versions listed below and your IT environment includes devices running in a virtual desktop infrastructure, we recommend you apply the out-of-band update instead.
Note: This out-of-band update contains all of the improvements and fixes included in the May 2025 Windows non-security preview update (KB5058502), in addition to this issue’s resolution. Since this is a cumulative update, you do not need to apply any previous update before installing KB5062170, as it supersedes all previous updates for affected versions. This update does not contain any additional security updates from those available in the May 2025 Windows security update. Installation of this OOB will require a device restart.
If you experienced this issue and are unable to start Windows, please try the following steps to recover your device. After you've recovered your device, install the out-of-band update (KB5062170) via the Microsoft Update Catalog.
- On Recovery-enabled devices:
- Access the Windows Recovery Environment.
- Restart Windows.
- On non-Recovery enabled devices:
- Mount the virtual hard disk (VHD) from a remote device.
- Mount the VHD on another virtual machine (VM) or device as a data disk and then return it back to the affected VM.
- Restart Windows in normal mode. This will revert Windows to the last successfully installed Windows update.
For Azure customers, we recommend using the self-help repair steps outlined in this article to carry out these steps: Repair a Windows VM using Azure Virtual Machine repair commands.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2
- Server: None
April 2025
Windows 11, version 24H2 might not download via Windows Server Updates Services
| Status | Originating update | History |
|---|---|---|
| Resolved KB5058405 | OS Build 22621.5189 KB5055528 2025-04-08 | Resolved: 2025-05-13, 10:00 PT Opened: 2025-04-29, 15:40 PT |
Devices which have installed the April Windows monthly security update, released April 8, 2025, (KB5055528), the April 11, 2025, Windows out-of-band update (KB5058919), or the April 22, 2025, Windows preview update (KB5055629), might be unable to update to Windows 11, version 24H2 via Windows Server Update Services (WSUS). WSUS allows Servers with the WSUS role to defer, selectively approve, and schedule updates for specific devices or groups across an organization.
As part of this issue, the download of Windows 11, version 24H2 does not initiate or complete. Windows updates log can show error code 0x80240069, and further logs might include text similar to "Service wuauserv has unexpectedly stopped".
Resolution: This issue was resolved by Windows updates released May 13, 2025 (KB5058405), 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 May 13, 2025 KB5058405, 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 May 13, 2025, and have this issue, your IT administrator can resolve it by installing and configuring the special Group Policy listed below.
Group Policy downloads with Group Policy name:
- Download for Windows 11, version 23H2 and Windows 11, version 22H2 – Windows 11 22H2 KB5055528 250426_03001 Known Issue Rollback.msi (also applicable to Windows 11, version 23H2)
The special Group Policy can be found in Computer Configuration > Administrative Templates > <Group Policy name>. For information on deploying and configuring these special Group Policies, please see How to use Group Policy to deploy a Known Issue Rollback.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2
- Server: None
March 2025
USB printers might print random text with the January 2025 preview update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5053657 | OS Build 22621.4830 KB5050092 2025-01-29 | Resolved: 2025-03-25, 10:00 PT Opened: 2025-03-11, 17:04 PT |
After installing the January 2025 Windows preview update (KB5050092), released January 29, 2025, or later updates, you might observe issues with USB connected dual-mode printers that support both USB Print and IPP Over USB protocols. You might observe that the printer unexpectedly prints random text and data, including network commands and unusual characters. Resulting from this issue, the printed text might often start with the header "POST /ipp/print HTTP/1.1", followed by other IPP (Internet Printing Protocol) related headers. This issue tends to occur more often when the printer is either powered on or reconnected to the device after being disconnected.
The issue is observed when the printer driver is installed on the Windows device, and the print spooler sends IPP protocol messages to the printer, causing it to print unexpected text.
Resolution:
This issue was resolved by Windows updates released March 25, 2025 (KB5053657), 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 have an enterprise-managed device and have installed the update released March 25, 2025 (KB5053657) 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 March 25, 2025, 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, version 23H2 and 22H2 - Windows 11 22H2 KB5050092 250131_150523 Known Issue Rollback
- Download for Windows 10, version 22H2 - Windows 10 22H2, 21H1, 21H2 and 22H2 KB5050081 250131_082569 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 printing issue.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2
- Server: None
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
August 2024
August 2024 security update might impact Linux boot in dual-boot setup devices
| Status | Originating update | History |
|---|---|---|
| Resolved KB5058405 | OS Build 22621.4037 KB5041585 2024-08-13 | Resolved: 2025-05-13, 10:00 PT Opened: 2024-08-21, 18:33 PT |
After installing the August 2024 Windows security update, (KB5041585) or the August 2024 preview update, you might face issues with booting Linux if you have enabled the dual-boot setup for Windows and Linux in your device. Resulting from this issue, your device might fail to boot Linux and show the error message “Verifying shim SBAT data failed: Security Policy Violation. Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation.”
The August 2024 Windows security and preview updates apply a Secure Boot Advanced Targeting (SBAT) setting to devices that run Windows to block old, vulnerable boot managers. This SBAT update will not be applied to devices where dual booting is detected. On some devices, the dual-boot detection did not detect some customized methods of dual-booting and applied the SBAT value when it should not have been applied.
IMPORTANT: This known issue only occurs with the installation of the August 2024 security and preview updates. The September 2024 security update and later updates do not contain the settings that caused this issue.
Resolution: This issue was resolved by Windows updates released May 13, 2025 (KB5058405), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
Note: On Windows-only systems, after installing the September 2024 or later updates, you can set the registry key documented in CVE-2022-2601 and CVE-2023-40547 to ensure the SBAT security update is applied. On systems that dual-boot Linux and Windows, there are no additional steps necessary after installing the September 2024 or later updates.
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
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
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.