USB drive says "Read-Only" and won't format. Can DiskPart fix this?

zqxy

Okay, I am officially losing my mind.

I was in the middle of preparing a presentation for tomorrow morning, tried to save the updated PDF to my 64GB SanDisk USB flash drive, and BAM—"The disk is write-protected."

I didn't switch any physical tab because there isn't one. I tried deleting files, manually changing permissions, and even attempting a quick format in Windows File Explorer, but Windows just slaps me with "The disk is write-protected" or "Windows was unable to complete the format."

I've got files on here I desperately need to move off, but more importantly, I need to know if I can revive this drive so I don't have to panic-buy another one at 11 PM. I read somewhere that diskpart via Command Prompt can clear attributes or force a clean. Can DiskPart actually fix this, or am I just performing CPR on a plastic corpse? Please help, I’m running out of coffee and patience.

5k2z

DiskPart can fix it, but only if the read-only state was triggered by a software attribute flag rather than the drive’s internal controller locking down.

Run CMD as administrator and type:

diskpart

list disk

select disk X (replace X with your USB drive number)

attributes disk clear readonly

If the read-only attribute was set by Windows, a script, or a specific policy, this immediately clears it. However, if step 4 succeeds but the drive remains read-only after re-plugging, your NAND flash controller has likely triggered its hardware safety mode.

zqxy

5k2z Tried attributes disk clear readonly. CMD said "Disk attributes cleared successfully." I got super excited, unplugged it, plugged it back in... and it's STILL read-only when I try to copy files to it. Does this mean it's dead?

5k2z

zqxy Yep, congratulations, you have a read-only brick.

When flash memory hits its write-cycle limit or detects critical bad blocks, the onboard NAND controller deliberately locks the drive into read-only mode. It’s a hardware-level safety mechanism designed to let you read your data off the drive one last time before the memory cells degrade completely.

DiskPart commands operate at the OS software layer; they cannot override the low-level firmware instructions enforced by a failing flash controller. Copy your presentation off the drive RIGHT NOW while you still can, and buy a new one.

hgmm

5k2z Wait, hold on a second. Don't throw it in the trash just yet.

Before declaring software failure vs controller lock, you didn't run clean in DiskPart. attributes disk clear readonly only resets the volume flag in the OS environment.

Try this sequence:

select disk X

clean

create partition primary

format fs=ntfs quick (or fs=fat32)

If clean throws an I/O device error, then it's hardware failure. If clean succeeds, re-partitioning rebuilds the partition table and clears dirty bit flags stuck in the file system.

wnih

hgmm Typing format fs=ntfs quick in 2026 for a modern flash drive? Absolute madness. FAT32 caps out at 4GB per file, and NTFS causes excessive write cycles on flash media due to constant journaling. If you're going to give formatting advice, at least recommend exFAT for portable storage.

Also, running clean on a drive that might have a corrupted file system without checking chkdsk X: /f or checking raw S.M.A.R.T. data (if supported via vendor bridge) is asking to wipe unbacked-up data. Diagnose the underlying filesystem architecture before wiping partition tables.

zpwf

hgmm Writing down these exact commands step-by-step in my notes:

diskpart

list disk

select disk X

clean

create partition primary

format fs=exfat quick

Quick question though: if clean erases everything, I should definitely pull my PDF off the drive before doing this, right?

zqxy

hgmm Okay, I backed up my PDF to my desktop, took a deep breath, and ran clean.

It gave me this exact error:

DiskPart has encountered an error: The request could not be performed because of an I/O device error.

Is this the final boss? Am I cooked?

hgmm

zpwf Yes! Copy your PDF off FIRST. clean wipes the partition table, making data recovery much harder for beginners.

1nqq

zqxy "I/O device error" during a DiskPart write operation is literally the controller yelling "I can't write to these flash cells anymore, bro!"

Your SanDisk drive didn't just crash; it sacrificed itself to save your presentation. It went into read-only quarantine mode like a true hero so you wouldn't lose your work. Time to write a nice eulogy, toss it in the electronic waste bin, and go hit up Amazon or Best Buy.

wnih

zqxy Technically, there is one fringe exception before you bin it: bad USB ports or insufficient power delivery over the host bus can cause fake I/O device errors.

Try plugging the drive directly into a rear motherboard USB port (not an unpowered hub or front panel header), or test it on a completely different PC. If it still throws an I/O error on a fresh system, the NAND controller's write-protection bit is permanently set in firmware.

zqxy

wnih Tested on my roommate's desktop directly into the motherboard port back panel. Same exact I/O error when running DiskPart, and File Explorer still says read-only.

zpwf

zqxy Adding this to my cheat sheet:

attributes clear fails to stick -> Controller issue.

clean returns "I/O device error" -> Drive dead, NAND locked in safe mode.

Pull data immediately while read access still works.

Thanks everyone, this saved me hours of going down useless Registry editing rabbit holes!

1nqq

zqxy RIP drive. At least it gave you your PDF back before checking out.

Go grab that coffee now—you earned it, and your presentation is safe.