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 10, version 1809 and Windows Server 2019. 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 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 17763.9245 KB5122876 2026-09-08 | Resolved KB5129238 | 2026-09-14 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 17763.8880 KB5094123 2026-06-09 | Resolved KB5099538 | 2026-07-14 10:00 PT |
| Domain controllers may restart repeatedly after installing April security update Affected DCs will experience LSASS crashes. A mitigation is available through Microsoft Support. | OS Build 17763.8644 KB5082123 2026-04-14 | Resolved KB5091573 | 2026-04-19 14:00 PT |
| Windows Server 2022 and Server 2019 unexpectedly upgraded to Windows Server 2025 This issue has been mitigated. It was observed when updates were managed through some third-party applications. | N/A | Resolved KB5082123 | 2026-04-14 10:00 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 17763.8276 KB5073723 2026-01-13 | Resolved KB5075904 | 2026-02-10 10: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 17763.8276 KB5073723 2026-01-13 | Resolved KB5078131 | 2026-01-23 14: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 17763.8276 KB5073723 2026-01-13 | Resolved KB5077795 | 2026-01-17 14:00 PT |
| Message Queuing (MSMQ) might fail with the December 2025 Windows security update This issue causes MSMQ operations to fail unless users are granted full administrative privileges on the system. | OS Build 17763.8146 KB5071544 2025-12-09 | Resolved KB5074975 | 2025-12-18 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 17763.7919 KB5066586 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 KB5129238 | OS Build 17763.9245 KB5122876 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 (KB5122876), 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 (KB5129238), 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
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
Deleting a file from the Recycle Bin displays an internal filename in the dialog
| Status | Originating update | History |
|---|---|---|
| Resolved KB5099538 | OS Build 17763.8880 KB5094123 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 (KB5094123).
Resolution: This issue was resolved by Windows updates released July 14, 2026 (KB5099538), 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
April 2026
Domain controllers may restart repeatedly after installing April security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5091573 | OS Build 17763.8644 KB5082123 2026-04-14 | Resolved: 2026-04-19, 14:00 PT Opened: 2026-04-16, 18:50 PT |
After installing the April 2026 Windows security update (KB5082123) and rebooting, domain controllers (DCs) in environments with multiple domains in the forest that use Privileged Access Management (PAM), might experience LSASS crashes during startup. As a result, affected DCs may restart repeatedly, preventing authentication and directory services from functioning, and potentially rendering the domain unavailable.
Note: This issue affects Windows Server only. It does not impact consumer PCs or personal devices. The scenario is unlikely to be observed on individual-use devices that are not managed by an IT department.
Resolution: This issue is resolved by the out-of-band (OOB) update, released April 19, 2026, in the Microsoft Update Catalog. It can be found as KB5091573. For additional guidance, see How to download updates from the Microsoft Update Catalog.
Affected versions:
- Client: None
- Server: Windows Server 2025; Windows Server 2022; Windows Server, version 23H2; Windows Server 2019; Windows Server 2016
January 2026
Some devices might fail to shut down or hibernate
| Status | Originating update | History |
|---|---|---|
| Resolved KB5075904 | OS Build 17763.8276 KB5073723 2026-01-13 | Resolved: 2026-02-10, 10:00 PT Opened: 2026-01-15, 18:33 PT |
After installing Windows updates released on or after January 13, 2026 (KB5073723), some Secure Launch-capable PCs with Virtual Secure Mode (VSM) enabled are unable to shut down or enter hibernation. Instead, the device restarts. This issue does not affect devices with AMD or ARM64 processors and is limited to the affected platforms listed below.
Resolution: This issue was resolved by Windows updates released February 10, 2026 (KB5075904), and updates released after that date. 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 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019
- Server: Windows Server 2022; Windows Server 2019
Apps might become unresponsive when saving files to cloud-backed storage
| Status | Originating update | History |
|---|---|---|
| Resolved KB5078131 | OS Build 17763.8276 KB5073723 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 (KB5073723), 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 KB5078131, released on January 24, 2026, and available via the Microsoft Update Catalog, as well as in updates released after this date. We recommend installing the latest update for your device, as it contains important improvements and issue resolutions, including this one.
Note: To download updates from the Microsoft Update Catalog, follow the steps described on this article.
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
Connection and authentication failures in Azure Virtual Desktop and Windows 365
| Status | Originating update | History |
|---|---|---|
| Resolved KB5077795 | OS Build 17763.8276 KB5073723 2026-01-13 | Resolved: 2026-01-17, 14:00 PT Opened: 2026-01-14, 00:52 PT |
After installing the January 2026 Windows security update (KB5073723), 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: To address this issue, an out-of-band (OOB) update was released January 17, 2026, in the Microsoft Update Catalog. It can be found as KB5077795.
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. For additional guidance, see How to download updates from the Microsoft Update Catalog. As always, we recommend you install the latest update for your device as it contains important improvements and issue resolutions including this one.
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
December 2025
Message Queuing (MSMQ) might fail with the December 2025 Windows security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5074975 | OS Build 17763.8146 KB5071544 2025-12-09 | Resolved: 2025-12-18, 14:00 PT Opened: 2025-12-12, 17:13 PT |
After installing the December 2025 Windows security update (KB5071544), users might face issues with the Message Queuing (MSMQ) functionality. This issue also impacts clustered MSMQ environments under load. Due to this issue, users might encounter the following symptoms:
- MSMQ queues becoming inactive
- IIS sites failing with “Insufficient resources to perform operation” errors
- Applications unable to write to queues
- Errors such as "The message file 'C:\Windows\System32\msmq\storage*.mq' cannot be created” when creating message files
- Misleading logs like “There is insufficient disk space or memory", despite sufficient disk space and memory being available
This issue is caused by the recent changes introduced to the MSMQ security model and NTFS permissions on C:\Windows\System32\MSMQ\storage folder. MSMQ users now require write access to this folder, which is normally restricted to administrators. As a result, attempts to send messages via MSMQ APIs might fail with resource errors.
Individuals using Windows Home or Pro editions on personal devices are very unlikely to experience this issue. This issue primarily affects enterprise or managed IT environments.
Resolution: This issue was resolved by the Windows out-of-band update, released December 18, 2025 (KB5074975), which is available via the Microsoft Update Catalog, and updates released after that date. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
Note: To download updates from the Microsoft Update Catalog, follow the steps described on this article.
Affected versions:
- Client: Windows 10, version 22H2, Windows 10, version 21H2, Windows 10, version 1809, Windows 10, version 1607
- Server: Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012
October 2025
Smartcard authentication issues might occur with the October 2025 Windows update
| Status | Originating update | History |
|---|---|---|
| Resolved | OS Build 17763.7919 KB5066586 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 (KB5066586) 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 (KB5066586), 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
November 2024
Windows Server 2022 and Server 2019 unexpectedly upgraded to Windows Server 2025
| Status | Originating update | History |
|---|---|---|
| Resolved KB5082123 | N/A | Resolved: 2026-04-14, 10:00 PT Opened: 2024-11-09, 12:16 PT |
Windows Server 2025 is intended to be offered as an Optional upgrade in Windows Update settings for devices running Windows Server 2019 and Windows Server 2022. Two scenarios were observed in certain environments:
- Some devices upgraded automatically to Windows Server 2025 (KB5044284). This was observed in environments that use third-party products to manage the update of clients and servers. Please verify whether third-party update software in your environment is configured not to deploy feature updates. This scenario has been mitigated.
- An upgrade to Windows Server 2025 was offered via a message in a banner displayed on the device’s Windows Update page, under Settings. This message is intended for organizations that want to execute an in-place upgrade. This scenario has already been resolved.
The Windows Server 2025 feature update was released as an Optional update under the Upgrade Classification: “DeploymentAction=OptionalInstallation”. Feature update metadata must be interpreted as Optional and not Recommended by patch management tools.
We advise organizations to use Microsoft-recommended methods to deploy Windows Server feature updates.
Resolution: This issue is resolved and Microsoft has re-enabled the upgrade offer via the Windows Update settings panel. For more information on Feature Update from the Windows Server Setting Dialog, see Perform an in-place upgrade of Windows Server at Microsoft Learn.
Affected platforms:
- Client: None
- Server: Windows Server 2025; Windows Server 2022; Windows Server 2019
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.