DiskPart Has Encountered an Error: The Parameter Is Incorrect When Formatting

DDaniel8 · 2026-05-07T08:11:26+00:00

Hi everyone, I got the error “Windows could not format a partition on disk 0,” so I opened CMD from the installer and tried using DiskPart manually. I used...

DDaniel8

Emily Thank you. It works!

Allen

Had this exact issue last month. Before you do anything else, run detail disk after selecting the disk and check if there's any weird partition types or hidden sectors. Sometimes the partition table gets corrupted and clean doesn't actually clean everything.

Also, what does attributes disk show? If there's read-only attributes set, that'll cause this error too.

Allen

Allen
Actually, let me correct myself.
attributes disk clear readonly is what you want to try first. Had a client's drive with the same symptom and that fixed it.

Lucky

Allen
To add some context on why this happens:
The "parameter is incorrect" error in DiskPart is actually a generic wrapper for multiple underlying issues. At the filesystem driver level, when DiskPart calls into the volume manager to perform a format operation, it passes a set of parameters including cluster size, filesystem type, and quick format flag. If any of these parameters conflict with the physical drive's geometry or if the partition table entries don't align properly with the actual sector boundaries, the IO manager returns STATUS_INVALID_PARAMETER, which gets translated to the user-friendly message you're seeing.

The reason attributes disk clear readonly works in some cases is that certain USB controllers will report a drive as read-only when they detect potential corruption, and DiskPart's format routine doesn't check for this condition before attempting the write operations.

Lisa

Lucky

That's not entirely accurate. STATUS_INVALID_PARAMETER is just one possible NTSTATUS that maps to this error. It could also be STATUS_INVALID_DEVICE_REQUEST or even STATUS_DEVICE_NOT_READY in some edge cases. The Win32 error code 87 (ERROR_INVALID_PARAMETER) is what you're describing, but DiskPart doesn't always surface the underlying NTSTATUS directly.

Also, the read-only attribute thing is a red herring in most cases. The actual cause is usually that the partition was created with an incorrect starting offset or the partition type ID doesn't match what the format routine expects. clean should reset the partition table, but if the disk has a protective MBR from a previous GPT configuration, you need convert mbr or convert gpt explicitly.

Lucky

Lisa

Fair point on the NTSTATUS variations. I was simplifying for a general audience. But I'd argue the protective MBR scenario is less common with USB drives unless someone was messing with disk imaging tools. The read-only attribute issue is documented in MS forums going back years, so I wouldn't call it a red herring.

Tyler

Lucky

Ah yes, the classic "Windows decided your USB drive is now a paperweight" error. Love to see it.

OP, quick question - did you safely eject this drive... ever? Or are you one of those "I just pull it out when I'm done" people? Because 9 times out of 10, this error is Windows' way of saying "congratulations, you played yourself."

Anyway, try this:

diskpart

list disk

select disk X

clean

convert mbr

create partition primary

format fs=ntfs quick

If that doesn't work, your drive might actually be dying. SanDisk drives have a habit of going into read-only mode when they detect too many bad sectors. It's a "feature" to prevent data loss, but really it just means you need a new drive.

Lucky

Tyler

the convert mbr step is a good call. I've seen drives get stuck in a weird state where they're not properly GPT or MBR and DiskPart gets confused.

OP, also try running chkdsk /f /r X: from an elevated command prompt before you give up on the drive. Sometimes there's just a bad sector at the beginning of the partition that's causing the format to fail.

Lora

Following this thread. I have the same issue with a Kingston 64GB drive. Tried the attributes disk clear readonly suggestion from #6 and it worked! The format completed successfully.

Quick question though: what causes the read-only attribute to get set in the first place? I don't remember doing anything unusual with this drive.

Lisa

Lora

It can be triggered by several things: unsafe removal, power fluctuations during write operations, or the drive's internal controller detecting potential flash cell degradation. Some USB drives have firmware that automatically sets the read-only flag as a protective measure when they detect anomalies. It's not something you did "wrong" necessarily.

For future reference, always use "Safely Remove Hardware" or the eject option in Explorer. The write cache on USB drives isn't always flushed immediately, and pulling the drive out mid-write can corrupt the filesystem metadata.

Tyler

Lora

congrats, you just learned the hard way what "write caching" means.

But seriously, glad it worked. For anyone else finding this thread via Google at 2 AM while panicking about a dead drive: the sequence that usually fixes this is:

attributes disk clear readonly

clean

convert mbr (or gpt if you need >2TB)

create partition primary

format fs=ntfs quick

If none of that works, your drive is probably toast.

Lora

Lisa
Thanks for the explanation! Bookmarked this thread for future reference.

One more question: is there a way to check if a drive has the read-only attribute set BEFORE running into this error? Would be nice to catch it early.

Lora

Tyler

Thanks for the summary!

DDaniel8

Thanks everyone! The attributes disk clear readonly command worked for me too. Drive is formatting now.

Lucky

DDaniel8

Good to hear it worked. For anyone interested in the technical details. the reason this error message is so unhelpful is that DiskPart wraps multiple Win32 and NTSTATUS errors into a single user-facing message. The actual error is logged in the System Event Log under source "disk" or "ntfs" with more specific information. You can check it with Event Viewer > Windows Logs > System and filter for Event ID 7, 11, or 51.

Lisa

Lora

In DiskPart, after select disk X, run attributes disk or detail disk. The "Current Read-only State: Yes" line will tell you. You can also check in Device Manager under Disk Drives > Properties > Policies tab, but that's more about write caching than the actual read-only attribute.

Tyler

Lora

pro tip: if your USB drive suddenly becomes read-only and you didn't do anything, that's usually the drive telling you it's about to die. Back up your data immediately and don't trust it with anything important.SanDisk specifically has had issues with this - their Cruzer line has a known problem where the controller locks the drive when it detects too many write errors. It's a "safety feature" that basically bricks the drive. Fun times.