Microsoft Removes Samsung Galaxy Connect App After C: Drive Access Denial Affects Windows 11 Devices
What Happened — Microsoft pulled the Samsung Galaxy Connect app from the Microsoft Store after users of certain Samsung Galaxy Book 4 and desktop models reported “C:\ is not accessible – Access denied” errors that blocked file access and the launch of core Office and browser applications. The issue was traced to the app’s interaction with Windows 11, and a temporary removal was enacted while Samsung prepares a stable version.
Why It Matters for TPRM —
- A third‑party app can render critical OS functionality unusable, creating an operational‑continuity risk for any organization that deploys the affected hardware.
- The incident highlights the need for continuous monitoring of vendor‑supplied software that integrates with corporate endpoints.
- Delays in remediation can expose organizations to data‑loss or productivity impacts, especially in regulated sectors that rely on uninterrupted access to Windows C: drives.
Who Is Affected — Technology, finance, healthcare, government, and other enterprises that provision Samsung Galaxy Book 4 or Samsung desktop models running Windows 11.
Recommended Actions —
- Inventory all Windows 11 endpoints for the Samsung Galaxy Connect app; uninstall if present.
- Apply Microsoft’s out‑of‑band update for RRAS (released concurrently) to keep the OS patched.
- Coordinate with Samsung support for guidance on the stable app version and remediation timeline.
- Review third‑party app vetting processes and enforce least‑privilege policies on endpoint software.
Technical Notes — The Samsung Galaxy Connect app provides screen‑mirroring, file‑sharing, and data‑transfer capabilities between Galaxy devices and Windows PCs. On affected models (NP750XGJ, NP750XGL, NP754XGJ, NP754XFG, NP754XGK, DM500SGA, DM500TDA, DM500TGA, DM501SGA) the app caused permission failures that blocked access to the C: drive, prevented elevation of privileges, and hindered uninstalling updates or collecting logs. No CVE was disclosed; the root cause appears to be a software bug rather than a vulnerability exploit. Source: BleepingComputer