Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


When a USB drive is write-protected, first confirm that the computer can see the correct volume and read its existing files. Then separate a physical lock, a single locked file, operating-system permissions, a read-only disk attribute, an incompatible format, and a drive that has protected itself after errors. Do not erase or run a write-changing command until important data is copied elsewhere and the target disk is identified beyond doubt.
Key Takeaways
- Preserve readable files before trying to change the drive.
- Check whether one file, one folder, or the whole volume is read-only.
- Inspect a card adapter or enclosure for a physical lock.
- Confirm the filesystem and the operating system that last wrote to it.
- Treat repeated read-only behavior as a possible media-health warning.
If the device is absent from the system altogether, use the USB recognition guide. If the physical disk appears but no usable volume mounts, follow the external-drive visibility guide. This article starts only after a readable volume is present.
Begin with a small, disposable test file. Try to create a new folder at the top level of the USB drive, rename that folder, and then delete it. Do not use a valuable document for the test. Record the exact message and whether the same action works in a different folder on the drive.
The result creates a useful boundary:
| Observation | Likely layer to inspect next |
|---|---|
| One document cannot be edited, but a new folder works | File lock, ownership, application state, or document permissions |
| One folder rejects changes, but another folder works | Folder permissions or a managed/special-purpose directory |
| Nothing on the volume can be created, renamed, or deleted | Physical lock, volume attribute, filesystem state, policy, or media fault |
| Files can be copied off, but every write fails on two computers | Drive-side state, adapter lock, format, or failing media |
| The drive disappears or reconnects during a write | Port, cable, power, enclosure, or hardware fault rather than ordinary write protection |
Close applications that may still have the test file open, then retry once. An application can hold one file without making the entire drive read-only. On a managed computer, security software or an administrator policy may block removable-media writes; do not attempt to bypass that control.
Use the broader device and app troubleshooting guide if several storage devices or unrelated system functions changed at the same time.
Some SD cards, full-size SD adapters, USB card readers, and removable-media enclosures have a small lock slider. A microSD card normally relies on the adapter or reader for that signal. Inspect the device while it is disconnected, move only a clearly labeled switch, and reconnect it without forcing the mechanism.
If the switch feels loose or moves between positions, try a known-good compatible adapter or reader. A damaged slider can report “locked” even when it appears to be in the writable position. Do not tape, wedge, or dismantle a reader as a permanent fix; that can hide a mechanical fault and risk the card.
Plain USB flash drives usually do not have such a switch, but specialist secure or promotional drives sometimes do. Check the exact model documentation before assuming a small control is a write lock. A hardware-encrypted drive may also require its supported unlock process before writing; do not install an unknown “unlock” utility from a download site.
After reconnecting, repeat only the disposable folder test. If the drive becomes writable, copy or verify important data before trusting the adapter again. If the result changes when the device is touched or moved, stop repeated write attempts and replace the questionable adapter, cable, or enclosure.
First open Disk Management or File Explorer and confirm the drive letter, capacity, label, and existing folders. Disconnect other removable drives if that makes identification safer. The size and label should match the device in your hand; a drive letter alone is not enough evidence.
Windows DiskPart can display whether the selected disk has a read-only attribute. Microsoft documents that attributes disk shows disk attributes only after the intended disk has been selected.[1] Treat that as an inspection tool first. Do not copy a command sequence from a forum and clear attributes until you have matched the disk number, capacity, and contents.
If the attribute is not set, the block may be at another layer: a single file can be marked read-only, an account may lack permission to a folder, security policy may block removable storage, or the filesystem may have mounted read-only after an error. Test the same drive in another trusted computer before editing registry policy or reinstalling USB drivers.
If the attribute is set on a personal drive and you know why, follow Microsoft’s current documentation for the exact operation and then recheck the disposable folder. On a work or school computer, ask the administrator instead. A policy-enforced read-only state should not be defeated with registry changes, boot media, or third-party disk tools.
Run filesystem repair only after copying readable files and confirming the correct volume. Repair writes metadata, so it is not a harmless diagnostic on a failing device. If the drive disconnects, reports a different capacity, or produces repeated I/O errors, prioritize recovery and replacement rather than repeated repair passes.
A drive can be readable on one operating system but not writable because its filesystem is unsupported for writing there. Apple states that macOS can read an NTFS-formatted external drive but cannot write to it through Disk Utility’s supported formats. It also notes that a drive reserved for Time Machine may not accept ordinary files, and that permissions or disk errors can block writes.[2]
Check the reported format without erasing anything. On macOS, use Finder’s Get Info or Disk Utility; on Windows, use the drive properties or Disk Management. The format tells you which systems should write it, but it does not prove the media is healthy.
Choose the next action according to the data:
Reformatting destroys the existing filesystem and normally removes its files. It is a rebuild step, not a generic way to “remove write protection.” Never initialize or erase a disk simply because a prompt offers that option.
Flash media has a finite service life, and controllers may become unable to complete new writes when cells or metadata fail. The exact behavior varies by model, so a read-only state alone does not prove failure. The combination of repeated write protection, I/O errors, corrupted filenames, changing capacity, disconnects, or very slow reads is stronger evidence.
When those signs appear, stop stress-testing the drive. Copy the most important readable files first, starting with irreplaceable documents rather than large replaceable media. Verify a sample from the destination before doing anything that writes to the original.
Do not run multiple repair utilities, low-level format tools, or destructive surface tests on the only copy. If the data is valuable and reads are unstable, consider a professional recovery service. If the data is already backed up, retire the drive rather than returning it to an important workflow after one successful test.
For a new or warranty-covered drive, save the model, serial number, purchase record, screenshots of the exact error, and results from two trusted computers. Do not include private filenames in a public support post.
Use this order so that each step preserves evidence for the next:
Change one layer at a time. If you move the lock, alter permissions, clear an attribute, run repair, and reformat in one session, you will not know which condition mattered—and the final step may erase the evidence along with the data.
A physical adapter switch may have moved, the operating system may have mounted the filesystem read-only after an error, a policy may block removable-media writes, or the drive may be failing. Preserve readable files before trying to change the state.
Often, yes, if the cause is a lock switch, item permission, supported disk attribute, or host policy you are authorized to change. Formatting is destructive and should come only after backup and correct disk identification.
macOS can read NTFS volumes but does not provide normal NTFS writing through its supported Disk Utility formats. Use a supported workflow or back up and reformat for the systems you actually need.
Inspect first. DiskPart acts on the selected disk, so selecting the wrong disk can affect another device. Match the disk number, capacity, label, and contents, preserve data, and follow current Microsoft documentation.
Not always. A switch, permission, format, or managed policy can explain it. Repeated read-only behavior combined with I/O errors, disconnects, corruption, or changing capacity makes hardware failure more likely.
The file may be locked by an application, marked read-only, owned by another account, or stored in a restricted folder. If a disposable folder can be created elsewhere on the drive, troubleshoot the item rather than the whole disk.
Yes. Managed computers may deliberately prevent removable-media writes. Ask the administrator; do not use registry changes, boot tools, or another account to bypass a security control.
Replace it when write protection repeatedly returns, writes fail on trusted computers, the device disconnects, capacity changes, or filesystem errors recur. Verify your recovered files before retiring or returning the drive.
Distinguish one locked file from an entire USB volume that is read-only. Then check the hardware lock and the organization's write policy where applicable; neither a physical lock nor an administrative prohibition on writes can be released by changing VPN routing.
Sources checked 4 September 2026.
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.