A faulty Samsung Galaxy Connect app update is preventing Windows 11 users from accessing their C: drive on certain Samsung devices, with Microsoft and Samsung working on a fix.
A critical bug affecting Windows 11 users on Samsung devices has emerged following a recent system update, with the Samsung Galaxy Connect app identified as the culprit behind widespread C: drive access failures.

The Scope of the Problem
The issue manifests as an "Access denied" error when users attempt to access their C: drive, preventing them from launching applications, accessing files, or performing administrative tasks. Microsoft's investigation confirms that affected users cannot open essential software including Outlook, Office applications, web browsers, system utilities, and Quick Assist.
Beyond application launch failures, the bug also blocks users from:
- Accessing files stored on the C: drive
- Performing administrative functions
- Removing recent Windows updates
- Accessing certain system logs
- Elevating user access privileges
Affected Hardware and Software
Microsoft has identified specific Samsung device models experiencing the issue:
- NP750XGJ, NP750XGL, NP754XGJ, NP754XFG, NP754XGK (Galaxy Book 4 laptops)
- DM500SGA, DM500TDA, DM500TGA, DM501SGA (Samsung Desktop models)
The problem appears to be triggered by the February 2026 security updates (KB5077181) combined with the Samsung Galaxy Connect and Galaxy Share Folder apps.
Technical Investigation Findings
Microsoft and Samsung's joint investigation has pinpointed the Samsung Galaxy Connect app as the source of the malfunction. The investigation revealed that the issue stems from broken Access Control Lists in Samsung's factory image for Windows, which become problematic when the affected apps receive updates.
Current Mitigation Efforts
In response to the widespread impact, Samsung has taken several immediate actions:
- Temporarily removed the Galaxy Connect app from the Microsoft Store
- Rolled back to a previous version of the app to prevent further installations
- Working with Microsoft to develop and validate solutions for affected devices
However, Microsoft acknowledges that "recovery for devices already impacted remains limited," leaving users with few options for immediate resolution.
Available Workarounds
While official solutions are still in development, some users have reported potential workarounds through Reddit's r/sysadmin community. These methods involve extensive changes to drive permissions and altering drive ownership, though Microsoft has not tested or verified these approaches.
Important Warning: These workarounds require significant modifications to system permissions and are not recommended for long-term use, as they could create additional security vulnerabilities or system instability.
Recommended Actions for Users
For users with affected Samsung devices, Microsoft recommends:
- Immediate app removal: Uninstall the Samsung Galaxy Connect app from your device
- Rollback to stable version: If possible, revert to the currently recommended version of the app
- Monitor for updates: Watch for official communications from Microsoft and Samsung regarding permanent fixes
- Avoid risky workarounds: Unless you're technically experienced, avoid unverified permission modifications
Industry Impact and Response
The bug highlights the complex interdependencies between hardware manufacturers, software developers, and operating system providers. This incident demonstrates how a single application's update can cascade into system-wide failures affecting core functionality.
Both companies are working urgently to develop a comprehensive solution, though no timeline has been provided for when affected users can expect a fix. The incident serves as a reminder of the risks associated with pre-installed manufacturer applications and the importance of thorough testing before software updates are released.
Users experiencing the issue are advised to monitor official channels from both Microsoft and Samsung for updates on the resolution progress and to avoid making system modifications unless absolutely necessary.

Comments
Please log in or register to join the discussion