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 23H2. 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 |
|---|---|---|---|
| Incorrect notifications that "Microsoft Defender Antivirus is turned off" Microsoft Defender Antivirus remains active and functioning correctly despite notifications following the latest update. | N/A | Resolved | 2026-09-30 16:42 PT |
| Remote Desktop Services might stop responding after Sept. 2026 security update Some Windows devices with Remote Desktop enabled might experience Remote Desktop Services (RDS) instability. | OS Build 22621.7582 KB5122880 2026-09-08 | Resolved KB5129242 | 2026-09-14 10:00 PT |
| Host folder shares might be unavailable in Hyper-V-based Linux VMs Plan9 host folder shares might not appear in the guest environment after installing the September 2026 security update. | OS Build 22621.7582 KB5122880 2026-09-08 | Resolved KB5129242 | 2026-09-14 10:00 PT |
| GIF functionality in the Windows Emoji Panel might become unavailable This issue occurs because the previous GIF provider (Tenor) retired its service on June 30, 2026. | N/A | Resolved KB5120240 | 2026-08-11 10:00 PT |
| Windows Server Update Services sync operations might have issues or time out Remediation efforts are underway. Synchronization times are expected to return to normal as recovery progresses. | N/A | Resolved | 2026-07-20 13:22 PT |
| Deleting a file from the Recycle Bin displays an internal filename in the dialog This issue only occurs within the confirmation dialog after installing the June Windows security update. | OS Build 22621.7219 KB5093998 2026-06-09 | Resolved KB5099414 | 2026-07-14 10:00 PT |
| Parental consent may not show for some browser versions with web filtering on Children may not be able to use some browsers when web filtering is on, and Activity reporting is off in Family Safety | N/A | Resolved | 2026-02-10 18:11 PT |
| Some devices might fail to shut down or hibernate This issue affects some Secure Launch-capable PCs with Virtual Secure Mode enabled after installing Jan '26 updates. | OS Build 22621.6491 KB5073455 2026-01-13 | Resolved KB5075941 | 2026-02-10 10:00 PT |
| Connection and authentication failures in Azure Virtual Desktop and Windows 365 January 2026 Windows update causes Windows App credential prompt failures on Azure Virtual Desktop and Windows 365 | OS Build 22621.6491 KB5073455 2026-01-13 | Resolved KB5078132 | 2026-01-24 14:00 PT |
| Apps might become unresponsive when saving files to cloud-backed storage Affected apps include Outlook, which can become unresponsive when accessing PST files stored on Microsoft OneDrive. | OS Build 22621.6491 KB5073455 2026-01-13 | Resolved KB5078132 | 2026-01-23 14:00 PT |
| Smartcard authentication issues might occur with the October 2025 Windows update This issue is related to a security change introduced for strengthening Windows Cryptographic Services. | OS Build 22621.6060 KB5066793 2025-10-14 | Resolved | 2025-10-22 17:31 PT |
Issue details
September 2026
Remote Desktop Services might stop responding after Sept. 2026 security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5129242 | OS Build 22621.7582 KB5122880 2026-09-08 | Resolved: 2026-09-14, 10:00 PT Opened: 2026-09-11, 11:19 PT |
After installing the September 2026 Windows security update (KB5122880), some organizations might experience issues with Remote Desktop Services (RDS).
In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at "Please wait for the Remote Desktop Configuration". Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator.
Note: This issue does not affect Windows 365 or Azure Virtual Desktop.
Resolution: This issue is resolved by the out-of-band (OOB) update released on September 14, 2026 (KB5129242), and in updates released after this date.
IT administrators who deployed a temporary mitigation through Group Policy do not need to take any action before installing this OOB update.
This OOB update is cumulative and includes all improvements and security protections contained in previous Windows updates. As a best practice, we recommend installing the latest update available for your devices, as it contains important improvements and issue resolutions, including this one.
Affected platforms:
- Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016
- Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Host folder shares might be unavailable in Hyper-V-based Linux VMs
| Status | Originating update | History |
|---|---|---|
| Resolved KB5129242 | OS Build 22621.7582 KB5122880 2026-09-08 | Resolved: 2026-09-14, 10:00 PT Opened: 2026-09-11, 02:22 PT |
Updated (9/14): The resolution section was updated. IT administrators that deployed a temporary mitigation through Group Policy must re-enable the Group Policy and install the out-of-band update to resolve the issue.
After installing the September 2026 security update KB5122880, applications that use HCS-managed virtual machines might experience issues when sharing host folder with Linux VMs using Plan9. Affected virtual machines start normally, but folders shared from the Windows host using Plan9 do not appear or cannot be accessed in the guest environment.
Applications or sandbox environments that depend on these shared folders might display an error indicating that no Plan9 drive shares were mounted. Claude Cowork and the Windows Subsystem for Linux (WSL) are two of the applications affected by this issue. Standard Hyper-V virtual machines that do not use the Plan9 feature are not affected by this issue.
Resolution: This issue is resolved by the out-of-band (OOB) update released on September 14, 2026 (KB5129242), and in updates released after this date.
IT administrators who deployed a temporary mitigation through Group Policy must re-enable the Group Policy, install this OOB update, and restart to resolve this issue.
This OOB update is cumulative and includes all improvements and security protections contained in previous Windows updates. As a best practice, we recommend installing the latest update available for your devices, as it contains important improvements and issue resolutions, including this one.
Affected platforms:
- Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10, version 21H2
- Server: None
Click here to manage email notifications for Windows known issues.
August 2026
Incorrect notifications that "Microsoft Defender Antivirus is turned off"
| Status | Originating update | History |
|---|---|---|
| Resolved | N/A | Resolved: 2026-09-30, 16:42 PT Opened: 2026-08-28, 15:34 PT |
After installing Microsoft Defender Antivirus update (version 4.18.26070.9), released on August 5, 2026, notifications might appear stating that "Microsoft Defender Antivirus is turned off," even though the antivirus is functioning correctly and all settings show it as active. These notifications can appear when Windows starts and intermittently afterward. They persist even if notification settings are turned off.
This issue can be observed in any version of Windows or Windows Server with Microsoft Defender Antivirus running with the latest Defender updates.
Resolution: This issue was resolved in Microsoft Defender Antivirus update (version 4.18.26080.4), released on September 17, 2026.
Affected platforms:
- Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016
- Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
July 2026
Windows Server Update Services sync operations might have issues or time out
| Status | Originating update | History |
|---|---|---|
| Resolved | N/A | Resolved: 2026-07-20, 13:22 PT Opened: 2026-07-17, 18:18 PT |
Microsoft has identified a service degradation affecting Windows Server Update Services (WSUS). Organizations might experience increased synchronization times or sync operation timeouts on WSUS servers. This issue began in recent days, with heightened impact observed starting July 13, 2026, and service-side mitigation on Saturday July 18, 2026. After this day, synchronization times and sync operations are expected to be restored to normal.
This issue is related to a buildup of publishing metadata which is present on existing WSUS server installations as well as from the service side.
Resolution: There are two parts to the resolution of this issue.
- Organizations with existing WSUS server installations that are experiencing long sync times can benefit from manual steps in order to clean up unneeded metadata. This metadata is present in existing WSUS installations but can be safely removed. Detailed guidance has been provided at the following KB article: https://support.microsoft.com/help/5121986.
- On July 18, 2026, Microsoft deployed a service-side mitigation which returns synchronization times and sync operations back to normal for new WSUS installations and rebuilds. After this date, newly installed or rebuilt WSUS servers should not encounter this issue.
Affected platforms:
- Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; 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
- Server: Windows Server 2025; Windows Server 2022; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
June 2026
GIF functionality in the Windows Emoji Panel might become unavailable
| Status | Originating update | History |
|---|---|---|
| Resolved KB5120240 | N/A | Resolved: 2026-08-11, 10:00 PT Opened: 2026-06-29, 20:45 PT |
Starting on June 30, 2026, you might not see GIF options in the Windows Emoji Panel on some devices and instead see a message stating “GIF service is not available.” This issue occurs because the previous GIF provider (Tenor) retired its service on that date.
Resolution: This issue was resolved by Windows updates released August 11, 2026 KB5120240, and later. These updates include a new GIF provider (GIPHY). To restore the GIF functionality in the Windows Emoji Panel, install the latest available Windows update.
Affected platforms:
- Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2
- Server: Windows Server 2025
Deleting a file from the Recycle Bin displays an internal filename in the dialog
| Status | Originating update | History |
|---|---|---|
| Resolved KB5099414 | OS Build 22621.7219 KB5093998 2026-06-09 | Resolved: 2026-07-14, 10:00 PT Opened: 2026-06-18, 12:03 PT |
When permanently deleting a single item from the Recycle Bin, the confirmation dialog displays the internal Recycle Bin filename (for example, $Rxxxxx.ext) instead of the original filename. The Recycle Bin itself correctly displays the original filename, and restoring the item also restores it using the original filename.
This issue occurs after installing the Windows security update released on June 9, 2026 (KB5093998).
Resolution: This issue was resolved by Windows updates released July 14, 2026 (KB5099414), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one. If your organization has installed an update released on July 14, 2026, or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue.
Affected platforms:
- Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10 Enterprise LTSC 2019; Windows 10, version 1607
- Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
January 2026
Some devices might fail to shut down or hibernate
| Status | Originating update | History |
|---|---|---|
| Resolved KB5075941 | OS Build 22621.6491 KB5073455 2026-01-13 | Resolved: 2026-02-10, 10:00 PT Opened: 2026-01-15, 18:33 PT |
After installing the January 13, 2026, Windows security update (KB5073455) for Windows 11, version 23H2, some PCs with Secure Launch are unable to shut down or enter hibernation. Instead, the device restarts. Secure Launch uses virtualization-based security to protect the system from firmware-level threats during startup. KB5073455 is only offered for Enterprise and IoT editions of Windows 11, versions 23H2.
In addition, some Secure Launch-capable PCs with Virtual Secure Mode (VSM) enabled can experience this issue after installing Windows updates released on or after January 13, 2026 (KB5073455). This issue does not affect devices with AMD or ARM64 processors and is limited to the affected platforms listed below.
Resolution:
This issue was fully resolved by Windows updates released February 10, 2026 (KB5075941), and updates released after that date. This update resolves the issue both for devices with Secure Launch and for devices with VSM enabled. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
An initial solution that resolved some devices with Secure Launch was originally released via the Microsoft Update Catalog in an out-of-band (OOB) update, released January 17, 2026 (KB5077797), and then later via Windows Update in the out-of-band update released on January 24, 2026 (KB5078132).
Affected platforms:
- Client: Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019
- Server: Windows Server 2022; Windows Server 2019
Connection and authentication failures in Azure Virtual Desktop and Windows 365
| Status | Originating update | History |
|---|---|---|
| Resolved KB5078132 | OS Build 22621.6491 KB5073455 2026-01-13 | Resolved: 2026-01-24, 14:00 PT Opened: 2026-01-14, 00:52 PT |
Updated 2026-01-24: This message was updated to reflect the availability of a new Windows out-of-band update that addresses this issue and is available via the Windows Update release channel.
After installing the January 2026 Windows security update (KB5073455), credential prompt failures might occur in some remote connection applications. This includes remote desktop connections using the Windows App on Windows client devices, on Azure Virtual Desktop and Windows 365. The Windows App is affected by this issue on specific Windows builds and can experience sign-in failures.
Other remote connections and related applications may be similarly impacted.
Resolution:
Updated 1/24:
A new out-of-band (OOB) update was released on January 24, 2026. It can be found as KB5078132. If you have turned on Get the latest updates as soon as they're available in Windows Update settings (Settings > Windows Update), you will automatically receive this update. If the toggle is off on your device, you can install the update manually by going to Settings > Windows Update and selecting Download & install. Note that this update will show up in Windows Update only if you have installed one of the updates released in January that caused this issue.
We recommend using Windows Update to install this update. This OOB update is cumulative and includes all protections and improvements from the January 2026 Windows security update released January 13, 2026 and from the OOB update released January 17, 2026. If you have not yet deployed the January 2026 Windows security update and your IT environment includes the affected applications and features, we recommend applying this OOB update instead.
As always, we recommend you install the latest update for your device as it contains important improvements and issue resolutions including this one.
Updated 1/17:
This issue was originally addressed in an out-of-band (OOB) update released January 17, 2026, in the Microsoft Update Catalog. It can be found as KB5077797. For additional guidance, see How to download updates from the Microsoft Update Catalog.
If the OOB is not installed, one of the following connection options can be used as a temporary workaround:
- Use the Remote Desktop client for Windows to connect to Azure Virtual Desktop here (/previous-versions/remote-desktop-client/whats-new-windows?tabs=windows-msrdc-msi)
- Connect using the Windows App Web Client at windows.cloud.microsoft
Affected platforms:
- Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10, version 21H2, Windows 10 Enterprise LTSC 2019
- Server: Windows Server 2025; Windows Server 2022; Windows Server 2019
Apps might become unresponsive when saving files to cloud-backed storage
| Status | Originating update | History |
|---|---|---|
| Resolved KB5078132 | OS Build 22621.6491 KB5073455 2026-01-13 | Resolved: 2026-01-23, 14:00 PT Opened: 2026-01-20, 22:10 PT |
After installing Windows updates released on or after January 13, 2026 (KB5073455), some applications might become unresponsive or experience unexpected errors when opening files from or saving files to cloud-backed storage, such as OneDrive or Dropbox.
For example, in some configurations of Outlook that store PST files on OneDrive, Outlook might become unresponsive and fail to reopen unless its process is terminated in Task Manager, or the system is restarted. In addition, sent emails might not appear in the Sent Items folder, and previously downloaded emails might be downloaded again. The affected Outlook configurations primarily involve classic Outlook, which is commonly tied to enterprise licensing and is not included with most home installations of Windows. To check your Outlook configuration, see Feature comparison between new Outlook and classic Outlook.
Resolution:
This issue is resolved in the out-of-band (OOB) update released on January 24, 2026, (KB5078132), and updates released after this date.
If you have turned on Get the latest updates as soon as they're available in Windows Update settings (Settings > Windows Update), you will automatically receive this update. If the toggle is off on your device, you can install the update manually by going to Settings > Windows Update and selecting Download & Install. Note that this update will show up in Windows Update only if you have installed one of the updates released in January that caused this issue.
We recommend installing the latest update for your device, as it contains important improvements and issue resolutions, including this one.
For devices that have not yet installed the OOB update, there is an optional workaround for Outlook-specific scenarios. Moving the Outlook PST files out of OneDrive should resolve this issue. For guidance, please see documentation at How to remove an Outlook .pst data file from OneDrive. In addition, email accounts can still be accessed via webmail, if supported by your email provider.
Affected platforms:
- Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019
- Server: Windows Server 2025; Windows Server, version 23H2; Windows Server 2022; Windows Server 2019
October 2025
Smartcard authentication issues might occur with the October 2025 Windows update
| Status | Originating update | History |
|---|---|---|
| Resolved | OS Build 22621.6060 KB5066793 2025-10-14 | Resolved: 2025-10-22, 17:31 PT Opened: 2025-10-17, 20:06 PT |
Smart card authentication and other certificate operations might intentionally fail after installing Windows Updates released on or after October 14, 2025 (KB5066793) that contain protections for the security vulnerability, CVE-2024-30098. As part of this cryptography improvement, RSA-based smart card certificates are required to use KSP (Key Storage Provider) instead of CSP (Cryptographic Service Provider).
Common symptoms for certificates that use CSP include:
- Smart cards not being recognized as CSP providers (Cryptographic Service Provider) in 32-bit applications
- Inability to sign documents
- Failures in applications relying on certificate-based authentication
- Users might observe error messages such as "invalid provider type specified" and "CryptAcquireCertificatePrivateKey error."
You can detect if your smart card will be affected by this security enforcement if, prior to installing the October 2025 Windows security update (KB5066793), the System log contains Smart Card Service or Microsoft-Windows-Smartcard-Server Event ID: 624 with the message text: "Audit: This system is using CAPI for RSA cryptography operations. Please refer to the following link for more detail: https://go.microsoft.com/fwlink/?linkid=2300823."
Resolution:
For a permanent resolution, developers should update their authenticating app to perform Key Storage Retrieval using Key Storage API documented at Key Storage and Retrieval. Developers should complete this change before Windows updates released in April 2026, at which time the DisableCapiOverrideForRSA workaround listed below is planned to be removed.
Workaround:
If you encounter this issue, you can temporarily resolve it by setting the DisableCapiOverrideForRSA registry key value to 0. This is documented in CVE-2024-30098. Detailed steps to modify the registry key are listed below. Note: This option will be removed in Windows updates, planned for release in April 2026.
Steps to Modify the Registry
⚠️ Important: Editing the registry incorrectly can cause system issues. Always back up the registry before making changes.
1. Open Registry Editor.
- Press Win + R, type regedit, and press Enter.
- If prompted by User Account Control, click Yes.
2. Navigate to the subkey.
- Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Calais
3. Edit the key and set the value.
- Inside Calais, check if key DisableCapiOverrideForRSA exists
- Double-click DisableCapiOverrideForRSA.
- In Value date, enter: 0
Note: The DisableCapiOverrideForRSA registry setting is NOT added by the default OS install or the installation of Windows Updates and must be manually added on each device.
4. Close and restart.
- Close Registry Editor.
- Restart the computer for changes to take effect.
Affected platforms:
- Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2
- Server: Windows Server 2025; Windows Server 23H2; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2
June 2025
Parental consent may not show for some browser versions with web filtering on
| Status | Originating update | History |
|---|---|---|
| Resolved | N/A | Resolved: 2026-02-10, 18:11 PT Opened: 2025-06-24, 16:25 PT |
Certain laws require Microsoft to protect children from harmful and illegal content on the internet. Microsoft is committed to creating tools for parents and guardians to help them in guiding their children’s digital experiences and protect them from harmful and illegal online content.
One of the available tools is web filtering, which lets a parent or guardian filter websites. Currently, Microsoft Edge is the only supported browser that provides this functionality within Microsoft Family Safety, allowing Edge to be used by default on the child’s device after web filtering is enabled. Once web filtering is enabled, a parent or guardian needs to approve other unsupported browsers (any browser other than Edge) before they can be used. This helps parents understand that different settings apply to other browsers when it comes to blocking inappropriate websites and filtering search results for their children.
The blocking behavior continues to work for unsupported browsers, however, when unsupported browsers update to a new version, the latest version of the browser cannot be blocked until we add it to the block list. Microsoft is currently adding the latest versions of unsupported browsers, to the block list. As a result, some browsers may temporarily appear unblocked during this update process. We're actively working to ensure all latest versions of browsers are blocked, reinforcing our commitment to parents and guardians.
As Microsoft continues to update the block list, we’ve received reports of a new issue affecting Google Chrome and some browsers. When children try to open these browsers, they shut down unexpectedly. However, the standard workflow is to prompt a parental approval message stating, “You’ll need to ask to use this app”. Once the approval is consented, the browser operates as intended. This issue is only observed when the Activity reporting feature is turned off.
Workaround: The browser shutdown issue can be temporarily mitigated by turning on Activity reporting under Windows settings in Family Safety. Parents will then be able to receive approval requests as expected.
Resolution:
- Temporary access to unsupported browsers: This issue has been resolved through a service‑side fix. The rollout began early February 2026 and should reach all affected devices over the coming weeks. If your device presented this symptom, please let it connect to the internet to receive the resolution. No other action is required. For more information on how to use this feature, see Set up Microsoft Family Safety.
- Missing parental consent prompt: Fixed in the July non-security preview update (KB5062663), released July 22, 2025. The fix is gradually rolling out and will be automatically enabled on devices with KB5062663 installed or later updates.
Affected platforms:
- Client: Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, 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.