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 known issues and the status of the Windows 11, version 25H2 rollout. 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.
Known issues
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| Microsoft account sign ins might fail for Microsoft Teams Free and other apps Only sign ins using Microsoft accounts are affected. Businesses using Microsoft Entra ID will not experience this issue. | OS Build 26100.8037 KB5079473 2026-03-10 | Resolved KB5085516 | 2026-03-24 12:35 PT |
| Updates installed via WUSA might fail if installed from a shared folder This issue might occur when installing an update from a network folder containing multiple .msu files. | N/A | Resolved KB5079391 | 2026-03-26 14:10 PT |
| Microsoft received reports of loss of access to the C: drive and app failures Reports mention the issue affects some Samsung devices in specific regions after installing KB5077181. | N/A | Resolved External | 2026-03-16 20:50 PT |
Issue details
March 2026
Microsoft account sign ins might fail for Microsoft Teams Free and other apps
| Status | Originating update | History |
|---|---|---|
| Resolved KB5085516 | OS Build 26100.8037 KB5079473 2026-03-10 | Resolved: 2026-03-21, 14:00 PT Opened: 2026-03-19, 19:03 PT |
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
| Status | Originating update | History |
|---|---|---|
| Resolved External | N/A | Last updated: 2026-03-16, 20:50 PT Opened: 2026-03-13, 12:13 PT |
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
August 2025
Updates installed via WUSA might fail if installed from a shared folder
| Status | Originating update | History |
|---|---|---|
| Resolved KB5079391 | N/A | Resolved: 2026-03-26, 14:00 PT Opened: 2025-08-15, 11:56 PT |
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.