Photo: neowin.com
Microsoft has officially acknowledged a significant issue affecting Windows 11, where a newly discovered bug can render the system drive C inaccessible for certain users. This flaw, detailed in updated Windows 11 documentation, can severely impede PC functionality following a recent security update.
Impact of the C: Drive Accessibility Issue
The core of the problem manifests as an error message stating, “C:\ is not accessible – Access denied” when users attempt to access their primary system drive. While merely opening File Explorer might not be a daily task for everyone, the implications of this bug extend far beyond simple file access. Microsoft reports that the issue prevents crucial applications, including popular email clients like Outlook, various web browsers, and essential system utilities, from launching. This effectively incapacitates affected computers, hindering routine operations such as managing files, executing programs, elevating administrative privileges, and performing other fundamental daily tasks.
Affected Systems and Potential Root Cause
Fortunately, this alarming bug does not impact all Windows 11 installations. Microsoft’s investigations indicate that the problem is “predominantly observed” on specific Samsung laptop models, notably the Samsung Galaxy Book4, and other consumer devices within regions such as Brazil, Portugal, Korea, and India. Initial findings suggest that the Samsung Share application could be linked to the issue, though Microsoft has yet to fully validate the exact root cause. The company is actively investigating to pinpoint the definitive origin of the problem.
The bug specifically targets Windows 11 versions 24H2 and 25H2. Users operating on Windows 10 or older Windows 11 iterations, such as 23H2, should not encounter this particular problem on their Samsung devices.
User Workarounds and Official Response
Users have reported on platforms like Reddit that manually changing the ownership of Drive C and its associated folders and files might resolve the issue. However, this is considered a high-risk procedure and is only advisable in critical situations by those with advanced technical knowledge. For most affected users, the recommended course of action, especially if rolling back the problematic update hasn’t helped, is to await an official fix from Microsoft.
Update March 16, 2026: Microsoft has since released an official workaround addressing these critical system access problems.
