Windows 11 Bug Makes C Drive Inaccessible on Select Devices

Microsoft's February 2026 security update was supposed to fix things. Instead, it broke the most fundamental thing a computer does: letting you access your files.

On March 13, 2026, Microsoft officially acknowledged a bug in its February Patch Tuesday update (KB5077181) that renders the C: drive — the primary system drive on virtually every Windows PC — completely inaccessible on certain Samsung devices [1][2]. Users attempting to open File Explorer, launch applications, or do essentially anything productive are met with a terse message: "C:\ is not accessible – Access denied."

The bug doesn't just inconvenience users. It effectively bricks their machines. Outlook won't open. Browsers won't launch. System utilities refuse to run. Even the standard troubleshooting tools that might help diagnose the problem are themselves stored on the now-inaccessible drive [3].

For the millions of users who upgraded to Windows 11 in recent months — many of them reluctantly, pushed by Windows 10's end-of-support deadline — the incident is the latest data point in what has become an unmistakable pattern: Microsoft's update pipeline is broken, and the company knows it.

The Anatomy of a Drive Lockout

The technical details of the bug, while still under investigation, paint a troubling picture of how OEM software and Windows updates can collide catastrophically.

Microsoft's latest investigation points to the Samsung Share application — a file-sharing utility preinstalled on Samsung Galaxy Book laptops — as a likely culprit, though the company has not fully validated this theory [1][2]. The issue appears to involve corrupted or incorrectly applied Access Control Lists (ACLs) on the root of the system drive [4]. ACLs are the permission structures that determine which users and processes can read, write, or execute files on a given drive. When these permissions are stripped or misconfigured at the drive root level, the entire file system becomes a locked door.

The bug affects Windows 11 versions 24H2 and 25H2 — the two most current releases — and has been reported across multiple regions, including Brazil, Portugal, South Korea, and India [1][2][5]. It is "predominantly observed on Samsung Galaxy Book 4 and other Samsung consumer devices," according to Microsoft's known-issues documentation [3].

What makes the bug particularly insidious is that users cannot easily fix it themselves. Affected users are often unable to elevate privileges, uninstall the offending update, or even collect diagnostic logs, because all of those operations require access to the C: drive [2]. It is a Catch-22 of system permissions: the fix requires the very access that the bug has taken away.

The Dangerous Workaround

Frustrated users, many of them in Samsung's large Brazilian and South Korean markets, took to Reddit and community forums to crowdsource solutions. One widely circulated workaround — posted by a user claiming to be a Samsung technician in Brazil — involves booting into an administrator account and manually reassigning C: drive ownership to the "Everyone" security group [2][4].

Microsoft security experts have strongly cautioned against this approach. Granting the "Everyone" group ownership of the system drive effectively strips Windows of its built-in security protections for critical system directories, leaving the machine vulnerable to malware, unauthorized access, and further system instability [2]. It is the digital equivalent of removing the lock from your front door because you lost the key.

The recommended course of action, according to Microsoft, is to either uninstall KB5077181 (if the system allows it) or wait for a future update that addresses the root cause [1]. Microsoft and Samsung are jointly investigating the issue, but as of March 15, 2026, no official fix or workaround has been released.

KB5077181: One Update, Many Disasters

The C: drive lockout is far from the only problem caused by the February 2026 Patch Tuesday update. KB5077181 has generated a cascade of issues across a wide range of hardware configurations [6][7]:

• Boot loops: Some devices entered infinite restart cycles, restarting more than 15 times before reaching a broken login screen [6]
• Installation failures: Users reported a constellation of error codes — 0x800F0991, 0x800F0983, 0x800F0922, 0x80073712, and 0x80096004 — preventing the update from installing at all [6]
• Network failures: DHCP errors left some devices connected to Wi-Fi but unable to reach the internet [6]
• Bluetooth breakage: Bluetooth peripherals stopped functioning after the update [6]
• Audio and system freezes: Gaming laptops were particularly affected, with users reporting audio malfunctions and complete system lockups [6]

The breadth of these failures raises a fundamental question: how did an update this buggy pass through Microsoft's quality assurance pipeline?

Source: WindowsLatest / Microsoft Known Issues Documentation

Data as of Mar 15, 2026CSV

A Pattern, Not an Anomaly

The answer, according to a growing chorus of industry critics, is that the pipeline itself is the problem.

Windows 11 experienced more than 20 major update-related failures in 2025 alone [8]. The January 2025 Patch Tuesday broke USB audio devices and webcams. February's update crippled Adobe Premiere Pro on multi-monitor setups. March brought Blue Screens of Death and boot loops. By summer, game performance had degraded, the Windows Firewall was throwing false critical errors, and the "Reset This PC" recovery feature — the last-resort tool for a broken system — was itself broken [8].

The cadence has not improved in 2026. January's update (KB5074109) caused black screens and froze Outlook accounts, requiring not one but two emergency out-of-band patches within days [8][9]. February's KB5077181 then delivered the Samsung drive lockout and the litany of issues described above.

"A big part of the problem is focus, or the lack of it," wrote WindowsLatest in a detailed accounting of the year's failures. "While core parts of Windows 11 kept breaking update after update, Microsoft was busy pushing Copilot into every nook and corner of Windows" [8].

That criticism found an unlikely echo inside Microsoft itself. In January 2026, Windows division head Pavan Davuluri publicly acknowledged the "pain points" users had been reporting and announced that 2026 would be a "repair year" for the operating system [9][10]. Microsoft adopted an internal strategy called "swarming" — an incident-response model where cross-disciplinary teams of kernel developers, test engineers, driver partners, and QA staff are temporarily concentrated on the highest-impact failures [10][11].

"This year, you will see us focus on addressing pain points we hear consistently from customers: improving system performance, reliability, and the overall experience of Windows," Davuluri stated [10].

The Worst Possible Timing

The update quality crisis arrives at a moment when Microsoft can least afford it. Windows 11's market share has surged to 72.78% as of February 2026, up from just 50.73% in December 2025 — a 22-percentage-point jump in two months that StatCounter described as one of the sharpest increases in a decade [12][13].

Source: StatCounter Global Stats

Data as of Mar 2, 2026CSV

The surge is not a vote of confidence in Windows 11. It is a migration deadline. Windows 10 reached end of support on October 14, 2025, meaning devices still running it no longer receive security patches [14]. For businesses in regulated industries — healthcare, finance, legal — continuing on unsupported software can violate compliance requirements and void cyber-insurance coverage [14]. According to the analyst firm Omdia, 18% of Microsoft partners reported that their customers planned to continue running Windows 10 after end-of-support without a defined migration path, while 29% expected upgrades to take six months or longer [14].

The result is a massive, compressed wave of migrations — many of them happening on Samsung, Lenovo, HP, and Dell consumer and business laptops that ship with manufacturer-specific drivers, utilities, and preinstalled software. Each of these OEM configurations represents a potential surface for conflicts with Windows updates, and the Samsung Share bug is a textbook illustration of how those conflicts can escalate from annoyance to system failure.

The OEM Bloatware Problem

The C: drive lockout has reignited a long-running debate about OEM preinstalled software — commonly referred to as "bloatware" — and the risks it introduces into the Windows update pipeline.

Samsung Galaxy Book laptops, like most consumer Windows PCs, ship with a suite of manufacturer-specific applications: Samsung Settings, Samsung Update, Samsung Notes, and Samsung Share, among others. These applications operate with elevated system permissions and interact with Windows at a level that standard third-party software does not. When a Windows security update modifies system-level permissions — as KB5077181 appears to have done — these deeply embedded OEM applications can behave unpredictably [2][5].

The interaction between Samsung Share and Windows' ACL structures is a case study in the risks of this model. Samsung Share likely modifies or monitors file system permissions as part of its file-sharing functionality. When the February update altered the underlying permission architecture, the two systems may have conflicted in a way that neither Microsoft nor Samsung tested for [2][3].

This is not a novel failure mode. In 2025, Intel Smart Sound Technology (SST) drivers — included on many OEM laptops — caused widespread audio failures after Windows updates replaced part of the driver stack with incompatible versions [15]. OEM update utilities have also been known to silently reinstall drivers that users had deliberately removed or blocked [15].

The fundamental tension is structural: Microsoft controls the operating system and its update pipeline, but OEMs control the hardware and the preinstalled software stack. Neither party fully tests against the other's changes, and the user is left holding the consequences.

What Affected Users Should Do

For users currently locked out of their C: drive, the options remain limited:

1. Attempt to uninstall KB5077181 by booting into Windows Recovery Environment (WinRE) or Safe Mode and using the "Uninstall latest quality update" option
2. Wait for the official fix — Microsoft has indicated it will release a resolution in a future update, though no timeline has been provided [1]
3. Avoid the Reddit workaround of assigning C: drive ownership to "Everyone," which creates serious security vulnerabilities [2]
4. Contact Samsung support for device-specific guidance, particularly regarding the Samsung Share application

For users who have not yet installed the February update, pausing Windows Update temporarily may be prudent until Microsoft confirms a fix.

The Bigger Picture

The C: drive lockout is, in isolation, a serious but bounded problem — it affects specific Samsung devices running specific Windows 11 versions after a specific update. But it does not exist in isolation. It is one link in a chain of update failures stretching back more than a year, hitting users at the precise moment when hundreds of millions of them are being pushed onto an operating system that has repeatedly proven it cannot update itself without breaking something.

Microsoft has promised that 2026 will be the year it earns back user trust. Two months in, the repair work is far from finished — and for Samsung Galaxy Book owners staring at an "Access denied" error on their own C: drive, trust is precisely what is missing.

Source: GDELT Project

Data as of Mar 15, 2026CSV