A SATA SSD can become read-only for reasons ranging from a simple Windows setting to the drive’s own failure-protection mode. In the best-case scenario, a disk attribute, file-system error, or BitLocker state is blocking writes and can be corrected without losing data. In the worst case, the SSD firmware has detected excessive NAND wear, repeated write failures, or unstable power and has permanently switched the drive to read-only mode to preserve whatever data remains.
Do not begin by formatting the drive. First, copy any important files from it to another physical disk. A drive that is readable today may become inaccessible after a reboot, firmware reset, or failed repair attempt. This guide applies to internal 2.5-inch SATA SSDs, M.2 SATA SSDs, and SATA drives connected through USB adapters in Windows 11 and Windows 10 in 2026.
Most Common Causes
| Cause | Symptom | Likelihood |
|---|---|---|
| SSD firmware protection mode from NAND wear or failure | Writes fail on every PC; DiskPart cannot clear read-only status | High on older or heavily used drives |
| Windows disk or volume read-only attribute | Drive appears healthy, but new files cannot be created or deleted | Moderate |
| NTFS, exFAT, or partition-table corruption | “Write protected” or access errors after a crash or improper shutdown | Moderate |
| BitLocker encryption or permissions issue | Only certain folders or an unlocked encrypted volume reject changes | Moderate |
| Bad SATA cable, power connection, port, or USB-SATA bridge | Intermittent detection, freezes, I/O errors, or read-only behavior after reconnecting | Moderate |
| Registry WriteProtect policy or security software | Multiple removable or external drives are blocked from writing | Low |
Diagnose Step by Step
1. Confirm whether the problem affects the whole disk or one folder
Open File Explorer, select the SSD, and try to create a small text file in the drive’s root folder. Then try another folder. If only one game library folder rejects writes, the disk may be fine; folder permissions, controlled folder access, or a launcher process may be responsible. If Windows reports “The disk is write protected” everywhere, continue with disk-level checks.
For a Steam library, open Steam, select Steam > Settings > Storage, choose the affected drive, and check whether Steam reports the library folder as unavailable. Also close Steam completely from the system tray before testing manual file creation.
2. Back up readable data before attempting repairs
Copy save files, documents, screenshots, mod folders, and any irreplaceable data to another drive. Typical PC game save locations include C:\Users\YourName\Documents\My Games, C:\Users\YourName\Saved Games, and C:\Users\YourName\AppData\Local. To open AppData quickly, press Windows+R, type %localappdata%, and press Enter.
If copying produces cyclic redundancy check errors, freezes Explorer, or causes the SSD to disappear, prioritize data recovery rather than repair commands.
3. Check the disk attributes in DiskPart
Right-click Start and choose Terminal (Admin). Type the following commands one at a time:
diskpart list disk select disk X attributes disk list volume select volume X attributes volume
Replace each X with the correct disk or volume number. Verify capacity before selecting anything. Look for Current Read-only State : Yes and Read-only : Yes. The first can be imposed by hardware or firmware; the second is a software-set attribute that DiskPart may clear.
4. Review SMART health and Windows error logs
Use the SSD manufacturer’s utility if available, or a reputable SMART viewer, to inspect drive health, available spare blocks, media errors, unsafe shutdown count, and critical warnings. A “good” headline status does not guarantee a healthy drive, but critical warnings, rapidly increasing error counts, or unavailable SMART data are serious signs.
Also open Event Viewer by pressing Windows+R, typing eventvwr.msc, and pressing Enter. Go to Windows Logs > System, then use Filter Current Log. Check warnings and errors from sources including Disk, Ntfs, storahci, and iaStorA. Repeated Event ID 7, 51, 129, or 153 can point to storage communication trouble.
5. Rule out cable, port, and adapter faults
Shut down the PC fully, switch off the power supply if it has a rear switch, and reseat both SATA data and SATA power connectors. Try another known-good SATA data cable and a different motherboard SATA port. Avoid loose splitters when testing. For an external SATA SSD, test another USB cable, USB port, and USB-SATA enclosure or adapter.
If the SSD writes normally after changing the connection, do not assume the drive is permanently repaired. Watch Event Viewer for several days and keep backups current.
6. Check encryption, ownership, and security controls
Open Settings > Privacy & security > Device encryption or search for Manage BitLocker from Start. Confirm the drive is unlocked. For an NTFS folder, right-click it, select Properties > Security > Advanced, and verify your account has Modify permission. In Windows Security, check Virus & threat protection > Ransomware protection > Manage ransomware protection for Controlled folder access blocks.
Fixes by Cause
Windows disk or volume attribute
What causes it: A disk or volume can retain a software read-only flag after a policy change, disk-management operation, or failed utility.
How to check: In elevated DiskPart, inspect both attributes disk and attributes volume. A value of Read-only : Yes is the relevant software flag.
What to do: Select the correct disk, then run attributes disk clear readonly. Select the affected volume and run attributes volume clear readonly. Exit DiskPart with exit, reconnect the drive, and test creating a file. Do not use clean; it removes partition information.
How to undo: If you intentionally need write protection later, select the disk in DiskPart and run attributes disk set readonly.
File-system corruption
What causes it: Power loss, forced restarts, cable dropouts, or crashes can leave NTFS or exFAT metadata inconsistent. Windows may restrict writes to prevent additional damage.
How to check: Open Terminal (Admin) and run chkdsk E: /scan, replacing E: with the SSD letter. Review the result before making changes.
What to do: After backing up data, run chkdsk E: /f. If Windows says the volume is in use, accept scheduling the repair and restart. Use chkdsk E: /r only when data is already backed up and you suspect unreadable sectors; it takes longer and adds extensive reads.
How to undo: CHKDSK repairs cannot be cleanly reversed. This is why the backup comes first. You can cancel a scheduled boot-time check by running chkntfs /x E: before restarting.
BitLocker, permissions, or Controlled Folder Access
What causes it: An encrypted volume may be locked, an inherited permission may deny modification, or Windows ransomware protection may block an unfamiliar game launcher or mod tool.
How to check: Run manage-bde -status E: in Terminal to see BitLocker status. Check the folder’s Security tab and Windows Security protection history for blocked apps.
What to do: Unlock BitLocker with its recovery key if required. For a folder you own, use Properties > Security > Edit and grant your account Modify, not necessarily Full control. In Controlled folder access, choose Allow an app through Controlled folder access and add the exact launcher executable.
How to undo: Remove the allowed app from the same ransomware-protection page. Restore prior permissions by removing the added permission entry or re-enabling inheritance in Security > Advanced.
SATA connection or controller instability
What causes it: A marginal cable, weak connector, unstable USB bridge, or controller reset can interrupt writes. Some SSDs react defensively after repeated communication failures.
How to check: Look for repeated Disk, storahci, or iaStorA events and test the SSD using a different cable, port, and power lead.
What to do: Replace the data cable, use a direct motherboard SATA port, and reconnect SATA power firmly. Install the motherboard chipset and storage-controller driver supplied by the PC or motherboard manufacturer. For USB use, replace the adapter rather than repeatedly reconnecting a questionable one.
How to undo: Reconnect the previous hardware only if testing proves it reliable. In Device Manager, use Storage controllers > Properties > Driver > Roll Back Driver if a newly installed driver causes new issues.
SSD firmware failure-protection mode
What causes it: When the controller detects worn NAND, exhausted spare area, uncorrectable write errors, or internal metadata risk, it may lock the SSD into read-only mode. This is designed to preserve data, not to inconvenience you.
How to check: DiskPart may show Current Read-only State : Yes even after clearing the normal attribute. The condition follows the SSD to another system, SMART data may show warnings, and manufacturer diagnostics may report failure or degraded health.
What to do: Copy all readable files immediately. Check for a manufacturer firmware update only if the utility specifically identifies a supported update and your backup is complete. Do not repeatedly format, secure erase, or power-cycle a failing drive. Start a warranty claim if applicable and replace the SSD.
How to undo: A genuine firmware-enforced read-only state usually cannot be safely undone. Replacing the drive is the appropriate reversal of the problem.
When to Replace or Reinstall
Replace the SSD when it remains read-only on another PC with another cable, DiskPart cannot clear the current read-only state, SMART reports critical warnings, or Windows logs repeated I/O and controller-reset errors. Also replace it if it disappears during large file copies or fails manufacturer diagnostics. A read-only SSD may remain readable for a while, but it is not trustworthy for game installs, save files, or an operating system.
Reinstall Windows only after confirming the hardware is stable. If the SSD is healthy and only the Windows installation has corrupted permissions, policies, or file-system damage, first try an in-place repair installation from Windows Setup while choosing to keep personal files and apps. For a clean reinstall, disconnect other storage drives temporarily, install Windows to the correct SSD, then reconnect secondary drives after setup. Never reinstall onto a drive that is already exhibiting firmware-level read-only behavior.
FAQ
Can a SATA SSD become read-only because it is full?
Usually no. A full SSD normally reports insufficient free space, not write protection. However, leaving very little free space can worsen performance and make recovery operations difficult. Free space by deleting data only if the drive still accepts writes; do not rely on this as a cure for a read-only state.
Will formatting remove read-only mode?
Formatting can fix a damaged file system if Windows can still write to the drive. It will not fix an SSD controller that has locked itself read-only, a faulty cable, or a Windows policy affecting the disk. Formatting also erases data, so it should never be the first diagnostic step.
Why can I read games from the SSD but not update them?
Game files already stored on the SSD can be read while launchers fail to download patches, create shader caches, update manifests, or write save data. Check free space, library-folder permissions, Controlled Folder Access, and whether the drive rejects a simple text file created in File Explorer.
Can I keep using a read-only SSD for storage?
Only temporarily, and only after copying important data elsewhere. A firmware-locked SSD can become fully inaccessible without warning. Treat its readable state as an opportunity to recover files, not as a dependable archive solution.
