Microsoft pulls Samsung Galaxy Connect from the Store after C: drive lockouts
Samsung's Galaxy Connect app, not a Windows update, locked some Galaxy Book4 and Samsung desktop users out of C: on Windows 11. Affected models and next steps.
In March 2026 Microsoft confirmed that some Samsung Galaxy Book4 laptops and Samsung desktops on Windows 11 were losing access to their own system drive, with the error "C:\ is not accessible – Access denied." The timing pointed at Windows updates, but Microsoft and Samsung traced it to Samsung's Galaxy Connect app, and Microsoft temporarily pulled the app from the Microsoft Store. This is a useful case for anyone who ships Windows software that touches file-system permissions.
What happened
Users of certain Samsung PCs on Windows 11 24H2 and 25H2 began reporting that the C: drive had become inaccessible after installing the February 2026 cumulative update (KB5077181) or later updates. Microsoft opened a release health entry on 13 March 2026 and updated it on 14 March. After a joint investigation, Microsoft said the issue "is not caused by current or previous Windows monthly updates." It pointed to Samsung Galaxy Connect, the app that handles phone-to-PC features such as screen mirroring and file transfer.
Microsoft temporarily removed the affected Galaxy Connect version from the Microsoft Store, and Samsung republished an earlier stable version to stop new devices from being affected. Microsoft marked the issue as mitigated but said recovery options for PCs already affected were limited, and it directed users to Samsung support while the two companies worked on a fix.
Who is affected
- Galaxy Book4 models NP750XGJ, NP750XGL, NP754XGJ, NP754XFG and NP754XGK.
- Samsung desktop models DM500SGA, DM500TDA, DM500TGA and DM501SGA.
- Running Windows 11 24H2 or 25H2 with the affected Galaxy Connect version installed.
Symptoms included being unable to open files or launch apps (Outlook, Office, browsers, system tools, Quick Assist), and permission errors when trying to elevate, uninstall updates or collect logs.
What it means for developers and engineering teams
Samsung hasn't published a technical root cause. The symptoms, though, show an application changing access control on the system volume, through ACLs on C:\ or the way processes are allowed to access it. That is about the most damaging thing a desktop app can do, because it also breaks the tools you would use to fix it: elevation, the uninstaller and log collection all failed.
Lessons for anyone shipping Windows software with installers, sync agents or services running as SYSTEM:
- Never change ACLs on volume roots or system folders. Limit permission changes to your own directories under
%ProgramData%or%LOCALAPPDATA%. - Test on the OEM images and models you ship to, across the current and previous Windows feature updates.
- Roll out gradually with telemetry that can detect a spike in failures and stop the rollout, the same practice you'd use for a server deploy.
- Correlation isn't causation. The issue appeared after a Windows update, which sent early triage the wrong way. Include installed app versions in bug reports.
For IT teams the incident shows the value of keeping OEM utilities under the same change control as everything else. Vendor companion apps often install through the Microsoft Store or their own updaters, outside WSUS or Intune update rings, so they can change on a managed device without anyone approving it. Inventorying those apps and deciding which ones a business device actually needs reduces this kind of surprise.
What to do now
- If you manage Samsung PCs, check for Galaxy Connect, for example with
Get-AppxPackage *Galaxy*in PowerShell, and make sure only Samsung's re-released stable version is installed. - Hold back Galaxy Connect updates on the affected models until Samsung confirms a fix.
- For affected machines, contact Samsung support before attempting manual ACL repairs. Restore from backup if recovery isn't possible.
- Before any repair attempt, make sure BitLocker recovery keys are available, since offline repair may need them.
- If you develop Windows apps, search your installer and service code for calls that change security descriptors (
SetNamedSecurityInfo,icacls) and confirm they only target your own paths.