• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Microsoft confirms Windows 11 bug crippling PCs and making drive C inaccessible

MrGuvernment

Fully [H]
2FA
Joined
Aug 3, 2004
Messages
23,951
Surprise! Another crap-tastic update from Microsoft that breaks basic functionality of the OS... in a major way...

At least it is specific systems, that they know of, so far...

https://www.neowin.net/news/microso...rippling-pcs-and-making-drive-c-inaccessible/

Microsoft has just confirmed a Windows 11 bug where the system won't let you access the system drive.​

Microsoft has updated the official Windows 11 documentation with details about a newly discovered bug that may ruin your day if you have a certain PC and try to access the system drive C. According to Microsoft, installing the February 2026 Patch Tuesday update (KB5077181) could lead to the error "C:\is not accessible - Access denied."
While drive C is not something you want to open every day, the problem goes a bit deeper than just opening File Explorer. Microsoft says that because of the bug, some apps cannot start, and those include popular stuff like Outlook, browsers, system utilities, and more. The issue effectively cripples your computer, as common actions like accessing files, executing common tasks, elevating privileges and doing other daily things.
Although the bug sounds absolutely terrifying, the good news is that not every Windows 11 system is affected. Microsoft says that the bug is "predominantly observed" on Samsung laptops, particularly on the Samsung Galaxy Book4 and other models in countries like Brazil, Portugal, Korea, and India. It is possible that the Samsung Share application could be the reason, but Microsoft is not ready to share exact details. Microsoft is investigating the problem, so expect to hear from them soon.

Here is what Microsoft says in the official documentation:
Microsoft has received reports of an issue in which some Samsung device models lose access to the C: drive after installing the February 2026 security update (KB5077181) and subsequent updates. Users might encounter the error, “C:\ is not accessible – Access denied”, which prevents access to files and blocks the launch of some applications including Outlook, Office apps, web browsers, system utilities and Quick Assist.
Affected devices encounter the issue when users execute common actions, such as accessing files, launching applications, or performing administrative tasks, and do not require any specific user action beyond routine operations. In some cases, users are also unable to elevate privileges, uninstall updates, or collect logs due to permission failures.
This issue has been reported across multiple regions, including Brazil, Portugal, Korea, and India, and is predominantly observed on Samsung Galaxy Book 4 and other Samsung consumer devices. Latest investigations indicate that the issue may be related to the Samsung Share application, though the root cause has not yet been fully validated.
As for the affected systems, only Windows 11 versions 24H2 and 25H2 were hit. If you are on Windows 10 or Windows 11 23H2 and older, the problem should not affect your Samsung device. Frustrated users on Reddit claim that changing ownership of the Drive C and its folders/files fixes the problem, but it is a risky thing that should be done only in emergencies. For most users, if rolling back the update did not yield any results, the best course of action is to wait for Microsoft to fix the issue.
 
Changing permissions is dangerous to those not in possession of technical skills needed to fix things.
Just another reason why to start with a fresh install on any OEM system!
 
What a relief that I don't live in Brazil, Portugal, Korea, or India, and don't have a Samsung laptop.

Don't OEMs test new releases any longer?
But the issue came from a Microsoft Update, I guess until we know, if ever, what specifically was the conflict that cause this, was it some outdated Samsung driver or software they use, or was it 100% another crappy MS update that broke something
 
Back
Top