[Help] diskpart clean vs clean all on a stubborn write-protected USB

Ray_993

am I about to nuke my OS drive?Picked up a weird read-only USB stick that Disk Management completely refuses to format. Tried opening CMD as Admin -> diskpart -> list disk. Now I'm staring at Disk 0 1TB NVMe boot drive and Disk 1 32GB USB. I am terrified of bricking my main system. What does clean actually do under the hood compared to clean all, and how does diskpart handle write protection?

Bobb

clean only zeroes out the partition table metadata (MBR/GPT headers and hidden sectors). The actual user data blocks stay untouched until overwritten. clean all writes zeroes sequentially across every single sector (O(n) time).
For write protection, running attributes disk clear readonly flips the software flag in the volume registry/partition header. However, if the NAND controller itself entered hardware write-lock due to bad-block exhaustion, no low-level CLI command will revive it.

AgentPrrrrro

Bobb Well actually, claiming clean only touches MBR/GPT is an oversimplification. On dynamic disks, it invalidates the Logical Disk Manager (LDM) database, and on GPT it wipes both the primary LBA 1 header and the backup header at the end of the physical volume.Also, running clean all on solid-state media does not issue an ATA Secure Erase or NVMe Sanitize command—it just wastes write cycles without triggering controller-level block reclamation.

Bobb

AgentPrrrrro Technically accurate on LDM and secondary LBA tables, but OP is dealing with a generic 32GB FAT32/exFAT thumb drive. No need to overcomplicate dynamic volume structures when the core risk is simply typing the wrong disk index.

AS_dk

Bobb Don't listen to the nerds OP. Real sysadmins always type select disk 0 -> clean all at 4:59 PM on a Friday to assert dominance over the production environment.

Ray_993

AS_dk Lmao please don't joke, my hands are literally sweating. So if I accidentally run clean on Disk 0, my Windows install is toast instantly?

RussleV8

Ray_993 Unplug every single external drive and card reader before you even launch CMD. Then run this exact sequence:
list disk
select disk X, replace X with your USB number, match by capacity,
attributes disk clear readonly clean
convert mbr,
create partition primary
format fs=exfat quick assign
If format throws an I/O device error or hangs indefinitely at 0%, the NAND is dead. Toss it in the bin.

Harlyn

RussleV8 +1 on unplugging everything first. Back in 2021, I was dead tired at 2 AM trying to make a bootable Linux stick. Typed select disk 0 instead of disk 2, hit clean, and instantly wiped my 4TB secondary HDD with 8 years of raw family photos. TestDisk saved my metadata eventually, but I lost 10 years of my life expectancy in 5 seconds.

Ray_993

Harlyn That is my literal nightmare. Why is there no Are you sure? (Y/N) prompt in diskpart before it obliterates a drive?

Isax

Ray_993 Because diskpart was designed for headless WinPE scripting and automated batch deployments, not interactive user handholding.If you want built-in safety boundaries, stop using the legacy CLI and move to PowerShell:Get-Disk | Where-Object BusType -eq 'USB' | Clear-Disk -RemoveData -Confirm:$trueIt checks hardware bus types and forces explicit confirmation tokens.

Harlyn

Ray_993 Back to your question in #8 about safety checks: Diskpart assumes Admin shell = user knows what they're doing. The foolproof habit is running detail disk immediately after select disk X and before touching clean. It prints the manufacturer model name (e.g. SanDisk Ultra USB Device vs Samsung SSD 980 PRO). If the name doesn't match your thumb drive, close CMD immediately.

AS_dk

Isax Bro really wrote a 3-line pipeline with 4 PascalCase cmdlets just to avoid unplugging a $6 Kingston thumb drive. Peak engineer efficiency.

Lupias

AS_dk Neither standard clean nor PowerShell Clear-Disk is secure if OP plans to sell or RMA the flash drive. Raw unallocated space can be reconstructed with carving tools in 10 minutes. At minimum, run clean all single-pass zero or an external 3-pass DoD 5220.22-M overwrite tool.

Bobb

Lupias DoD multi-pass wipes are magnetic platter relics from 1995. On NAND flash, Wear Leveling and the Flash Translation Layer (FTL) prevent predictable physical sector overwrites via sequential writes. A single zero pass, ATA Secure Erase, or destroying the BitLocker/AES encryption key makes data cryptographically unrecoverable. Nobody is using a scanning electron microscope on a cheap USB.

AS_dk

Bobb Unless OP works at Area 51, the only 3-pass standard they need is: 1. Microwave for 8 seconds, 2. Drill press straight through the flash die, 3. Throw the pieces into an active volcano.

Lupias

AS_dk Laugh all you want until your unencrypted browser session tokens end up on a secondary market forensic dump. Physical cross-cut shredding under 2mm particle size is the only ISO-compliant destruction method.

Ray_993

Harlyn The detail disk sanity check saved my sanity! Verified it was the SanDisk Cruzer, ran clean -> create part pri -> format, and the drive is working perfectly again. Thanks everyone for the explanations (and the paranoia)!