Resolved issues in Windows 11, version 25H2

Find information on recently resolved issues for Windows 11, version 25H2. 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 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

Issue details

March 2026

Microsoft account sign ins might fail for Microsoft Teams Free and other apps

Following installation of Windows updates released March 10, 2026 (KB5079473) sign in with Microsoft accounts might fail for some Microsoft applications, including Microsoft Teams Free or OneDrive. As a result of this issue, sign in attempts will display an error message with text similar to "You'll need the Internet for this. It doesn't look like you're connected to the Internet". This appears even if the device is connected to the internet.

Please note that this issue occurs only with sign in operations involving Microsoft accounts, which are commonly used for Microsoft Teams Free. Businesses using Entra ID (previously known as Azure Active Directory) for app authentication will not be affected by this issue.

Other applications affected include Microsoft Edge, Excel, Word, and Microsoft 365 Copilot. Whenever a feature in these applications requires Microsoft account sign in, the same message can be encountered.

Resolution: This issue was resolved by Windows updates released March 21, 2026 (KB5085516), and later updates. We recommend you install the latest updates for your device as they contain important improvements and issue resolutions, including this one. 

If you install an update released March 21, 2026 (KB5085516) or later, you do not need to use a workaround for this issue. If you are using an update released before this date, and have this issue, restarting the device while keeping it connected to the internet should prevent the issue from occurring.

Please note this issue occurs when the device enters a specific network connectivity state, and may resolve on its own. However, if the device is restarted without an active internet connection, it might return to a connectivity state where the issue can occur again. In such a case, it will be necessary to restart again while keeping internet connectivity, in order to repair the connectivity state.

Affected platforms:

• ​Client: Windows 11, version 25H2; Windows 11, version 24H2
• ​Server: None

Microsoft received reports of loss of access to the C: drive and app failures

Microsoft has received reports of an issue in which some Samsung device models lose access to the C: drive after installing the February 2026 security update (KB5077181) and subsequent updates. Users might encounter the error, “C:\ is not accessible – Access denied”, which prevents access to files and blocks the launch of some applications including Outlook, Office apps, web browsers, system utilities and Quick Assist. 

Microsoft and Samsung investigated these reports and concluded that the symptoms were caused by an issue in the Samsung Galaxy Connect app. While the reports coincided with recent March Patch Tuesday timing, investigation confirmed the issue is not caused by current or previous Windows monthly updates. The issue has been observed on Samsung Galaxy Book 4 and Samsung Desktop models running Windows 11, versions 24H2 and 25H2, including NP750XGJ, NP750XGL, NP754XGJ, NP754XFG, NP754XGK, DM500SGA, DM500TDA, DM500TGA, and DM501SGA.

Affected devices encounter the issue when users execute common actions, such as accessing files, launching applications, or performing administrative tasks, and do not require any specific user action beyond routine operations. In some cases, users are also unable to elevate privileges, uninstall updates, or collect logs due to permission failures.

Resolution: This issue can be resolved on affected devices by following the guidance documented in the Microsoft KB article “Recovery steps: Samsung Galaxy Connect or Samsung Continuity Service might cause loss of access to the C: drive.”

Microsoft and Samsung collaborated to validate these steps, which restore standard Windows permissions.

For device-specific assistance, please contact Samsung’s support channels.

Note: Mitigations to prevent additional devices from encountering this issue were implemented starting March 14, 2026 (Pacific Time). As part of these mitigations, the affected Samsung Galaxy Connect application was temporarily removed from the Microsoft Store, and Samsung republished a stable previous version of the application to prevent recurrence.

Affected platforms:

• ​Client: Windows 11, version 25H2; Windows 11, version 24H2
• ​Server: None

January 2026

Connection and authentication failures in Azure Virtual Desktop and Windows 365

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 (KB5074109), 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 KB5078127. 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 KB5077744. 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

After installing Windows updates released on or after January 13, 2026 (KB5074109), 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, (KB5078127), 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

Task Manager process might continue to run in background after app is closed

After installing Windows Updates released on or after October 28, 2025 (KB5067036), you might encounter an issue where closing Task Manager using the Close (X) button does not fully terminate the process. When you reopen Task Manager, the previous instance continues running in the background even though no window is visible. This results in multiple lingering instances of taskmgr.exe, consuming system resources and potentially degrading device performance. Additional instances appear as “Task Manager” in the Processes tab and as “Taskmgr.exe” in the Details tab. Although the impact is less if Task Manager is opened and closed a few times, many instances accumulated over time can cause noticeable slowdowns in other applications.

Resolution:

This issue is resolved in the November Windows security update (KB5068861) and later updates. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.  

If you have installed Windows updates released before November 11, 2025, you can use the following workaround.

Workaround: You can mitigate the issue by following one of the steps below:

1. ​When closing Task Manager, instead of closing it with the 'X' button, use End Task on the Task Manager process itself. This can be done by going to the Processes tab, selecting the Task Manager process, and clicking End Task.
2. ​To close multiple instances of Task Manager, you can use the command line prompt:
   1. ​Click Start (Windows icon) or press the Windows key.
   2. ​Type cmd or Command Prompt in the search box.
   3. ​Click Command Prompt from the results.
   4. ​To run as Administrator: Right-click Command Prompt and select Run as administrator.
   5. ​Run the command taskkill.exe /im taskmgr.exe /f and press enter.
   6. ​This will close all instances of Task Manager

Affected Versions:

• ​Client: Windows 11, version 25H2; Windows 11, version 24H2
• ​Server: None

IIS websites might fail to load

After further investigation, we concluded that this issue was not applicable to Windows Server 2025. It affects only Windows 11, version 25H2 and 24H2.

This issue can be disregarded by Windows Server users.

To learn about the impact of this issue for Windows 11, select from the links below:

• ​Windows 11, version 25H2
• ​Windows 11, version 24H2

The issue mentioned below was published prior to this finding and November 14, 2025 edits:

Following installation of Windows updates releases on or after September 29, server-side applications that rely on HTTP.sys may experience issues with incoming connections. As a result, IIS websites might fail to load, displaying a message such as "Connection reset - error (ERR_CONNECTION_RESET)", or similar error. This includes websites hosted on http://localhost/, and other IIS connections.

Affected platforms:

• ​Client: Windows 11, version 25H2; Windows 11, version 24H2

Smartcard authentication issues might occur with the October 2025 Windows update

Smart card authentication and other certificate operations might intentionally fail after installing Windows Updates released on or after October 14, 2025 (KB5066835) 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 (KB5066835), 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

USB mouse and keyboard not working in the Windows Recovery Environment (WinRE)

After installing the Windows security update released on October 14, 2025 (KB5066835), USB devices, such as keyboards and mice, do not function in the Windows Recovery Environment (WinRE). This issue prevents navigation of any of the recovery options within WinRE. Note that the USB devices continue to work normally within the Windows operating system.

Resolution: This issue was resolved by the Windows out-of-band update, released October 20, 2025 (KB5070773), 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.

Workaround: If your device is impacted by this issue and is unable to boot to Windows to install the latest Windows update, you can work around this issue using one of the following methods:

• ​If your PC has a touchscreen, you can use the touchscreen's touch keyboard to navigate within WinRE.
• ​If your PC has a PS/2 port, you can use a PS/2 keyboard or mouse to navigate within WinRE.
• ​If you had previously created a USB recovery drive, you can boot your computer from the recovery drive. This will take you directly to WinRE with restored USB functionality.
• ​OEMs and enterprises can use the Preboot Execution Environment (PXE) in Configuration Manager, or can deploy push-button reset features using the Windows Assessment and Deployment Kit (Windows ADK) and Windows Preinstallation Environment (WinPE) add-on to recover affected devices.

Affected platforms:

• ​Client: Windows 11, version 25H2; Windows 11, version 24H2
• ​Server: Windows Server 2025

September 2025

Problems playing protected content in some BluRay/DVD/Digital TV applications

Some Digital TV and BluRay/DVD applications might experience problems playing protected content. Applications using Enhanced Video Renderer with HDCP enforcement or Digital Rights Management (DRM) for digital audio might experience copyright protection errors, frequent playback interruptions, freezing or black screens. This issue does not impact streaming services.

Resolution: Problems affecting certain applications that use Enhanced Video Renderer with HDCP enforcement have been addressed in the September 2025 Windows preview update (KB5065789), and later updates. Additional improvements were included in the October 2025 Windows preview update (KB5067036) and later updates to resolve problems for applications using DRM for digital audio. 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 25H2; Windows 11, version 24H2
• ​Server: None

August 2025

Updates installed via WUSA might fail if installed from a shared folder

Windows updates installed using the Windows Update Standalone Installer (WUSA) might fail with error ERROR_BAD_PATHNAME, when the update is installed using WUSA or double-clicking a .msu file from a network share that contains multiple .msu files. These issues might occur on devices that installed updates released May 28, 2025 () and later.

WUSA is a method of installing updates using the Windows Update Agent API which is typically only employed in enterprise environments. It is not common in personal or home settings. 

Please note that this issue does not occur when there is only one .msu file in the network share or when the .msu files are stored locally on the device. In addition, after installing an .msu file by double-clicking or using WUSA and restarting Windows, you might notice that the Update History page in Settings continues to indicate that a restart is required to complete the update. This is temporary and should be resolved on its own.

Resolution: This issue was resolved by Windows updates released March 24, 2026 (KB5079391), 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 install an update released March 24, 2026 (KB5079391) or later, you do not need to use a workaround for this issue. If you are using an update released before this date, and are experiencing this issue, you have the option to work around it by saving the .msu files locally on the device and install the update from this location. Also, if you've restarted Windows after installing an .msu file via WUSA, please wait 15 minutes or more before checking the Update History page in Settings. After this short delay, the Settings app should properly indicate if the update installed successfully.

Additionally, this issue was addressed using Known Issue Rollback (KIR) beginning September 2025, and was resolved automatically for most home users and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. IT admins can resolve this issue for managed devices which have installed the affected update and encountered this issue. It can be fixed by installing and configuring the Group policy 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. The special Group Policy can be found in Computer Configuration > Administrative Templates > [Group Policy name].

Group Policy downloads with Group Policy name:

• ​Download for Windows 11, version 24H2 and Windows Server, version 2025 - Windows 11 24H2 and Windows Server 2025 KB5062660 250806_17201 Known Issue Rollback.msi

Affected platforms:

• ​Client: Windows 11, version 25H2; Windows 11, version 24H2
• ​Server: Windows Server 2025

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.