My WD external hard drive suddenly won’t open in Windows and shows “The parameter is incorrect.” It was working before, and I’m worried about losing files on it. What are the safest first steps to fix the WD external drive not accessible error without making things worse?
I’d be careful with this one. When I first got the “The parameter is incorrect.” message, I thought the external drive was dead. It had years of photos and work stuff on it, and Windows just refused to open it no matter how many times I replugged it. Turns out the data was probably still there, Windows just couldn’t read the file system properly.
So the main thing: don’t format it yet, even if Windows keeps pushing you that way. I’d also avoid running CHKDSK right away if there’s anything important on the drive. It can help in some cases, but I’d want a copy of the files first.
Start with the boring checks since they’re quick:
- Swap the USB cable.
- Try a different USB port, ideally one directly on the motherboard if it’s a desktop.
- Plug the drive into another computer.
- Check Disk Management and see if the drive still appears with the right capacity.
If Disk Management still shows the correct size, that’s a decent sign. It usually means the drive is still talking to Windows, even if the file system is messed up.
Before recovery, check the drive health. CrystalDiskInfo is good for that, and Disk Drill also has SMART monitoring if you’re already using it. If you see warnings like reallocated sectors, pending sectors, or other serious SMART errors, stop using the drive as much as you can. Extra reads can make a failing drive worse.
For getting the files back, I’d use Disk Drill. That’s what saved mine.
The part I liked most was Byte-to-byte Backup. Instead of repeatedly scanning the problem drive, it makes a full image of it first. Then you scan the image, not the original disk. That matters if the drive is unstable, because every read puts a little more stress on it.
Once you’ve made the image, or if the drive seems healthy enough to scan directly, run a Universal Scan. After it finishes, preview your photos, documents, videos, and whatever else you need. If the previews actually open, that’s usually a good sign. Recover the files to a different drive, never back onto the broken one.
Only after the important stuff is copied somewhere safe would I try repairing the drive.
A few options depending on what you’re seeing:
- If Windows still recognizes the file system, try CHKDSK with
chkdsk X: /r. - If the drive turned RAW, CHKDSK usually won’t do much. This video covers that kind of situation: TestDisk may be worth trying there since it can sometimes rebuild damaged partitions.
- If the drive seems fine but Windows is acting weird, run SFC and DISM to repair system files.
- There are also rare cases where the Windows decimal separator being changed causes this error. Switching it back to a period has fixed it for some people, though I wouldn’t put that high on the list.
If you’ve already recovered the files and nothing else works, then I’d do a quick format. If the drive behaves normally after that, it was probably file system corruption. If the same error comes back after formatting, I’d stop trusting the drive.
The one point where I wouldn’t keep messing with DIY fixes is if the drive clicks, drops offline randomly, vanishes from Disk Management, shows up inconsistently, or has serious SMART errors. At that stage, powering it on over and over can make recovery harder.
Most recovery labs will evaluate the drive first and quote you before doing the work. A lot of them also have a no data, no fee policy. From what I’ve seen, logical recovery is often around $300 to $600, while drives needing hardware repair or clean-room work can land closer to $700 to $2,000+, depending on the damage and capacity.
https://www.youtube.com/watch?v=_e4D_2bu8LE
1 Like
If the files matter more than the drive itself, do not try to “fix” the disk first. The safest first move is to stop anything that writes to it. That means no format, no initialize, no “scan and repair” pop-up, and I would not run chkdsk /r yet. That command can be useful later, but on a flaky external drive it can spend hours hammering the disk and changing the file system while it goes.
I agree with the cable/port/other-PC checks, but I’d add a boring Windows detail people miss: look in Disk Management without accepting any prompts. If the WD shows the right capacity but has no drive letter, you can try assigning a letter. If it shows RAW, unallocated, or asks to initialize, back out. That is not the moment to experiment. If it appears and disappears, makes clicking sounds, or takes forever to populate in Disk Management, unplug it and think recovery/clone first.
For a WD external specifically, don’t assume removing the bare drive from the enclosure will make recovery easier. Some WD USB enclosures handle translation or encryption in the bridge board, so moving the disk to SATA or another enclosure can make it look worse or unreadable. If the disk stays stable, make an image/clone and work from that. Disk Drill’s byte-to-byte image feature is reasonable for that kind of workflow, but the important bit is the method, not the brand: copy the problem drive first, recover files to a separate disk, then worry about repairing or reformatting the WD.
Plug the WD straight into a rear USB port with a known-good short cable, then leave it alone long enough to see whether Disk Management settles. A lot of portable WD drives get flaky when they are on a front-panel port, cheap hub, long cable, or underpowered laptop port. That can give you weird Windows errors that look like file system damage even when the first problem is just unstable USB power.
I agree with the warnings above about not formatting and not jumping straight to CHKDSK. The small caveat I’d make is that SMART readings over USB can be incomplete or misleading. If CrystalDiskInfo says “Caution” or “Bad,” believe it. If it says “Good,” don’t treat that as proof the drive is fine, especially if it disconnects, freezes Explorer, or takes ages to show folders.
If the drive stays connected and shows the right size, make your next move a copy-out or image, not a repair. Grab the irreplaceable folders first if the drive is readable at all. If it isn’t browseable, image it with a recovery tool and scan the image. Disk Drill is fine for that workflow, but the important rule is to recover to a different disk. After your files are safe, then you can try drive-letter changes, CHKDSK, partition repair, or a quick format. Until then, treat every “fix” button in Windows as something that might make the recovery messier.
A drive that shows up at the correct size is a different situation than a drive that keeps dropping out or clicking. In the first case, treat it like a file system or partition problem and copy/image first. In the second case, treat it like a failing device and stop poking at it.
I agree with the “don’t format, don’t run CHKDSK first” advice, but I’d extend that to WD’s own tools too. Don’t start an extended diagnostic or “repair” from WD Drive Utilities before the data is safe. A long surface test can be a lot of extra reading on a drive that may already be struggling. A quick health check is fine if the drive is stable, but if it hangs the computer or disappears, that test is not doing you any favors.
The first safe pass would be: short known-good cable, direct USB port, check Disk Management, confirm the capacity, then make a copy or image to another disk. If you can browse folders, grab the most important files manually before doing anything fancy. If Windows won’t browse it but the disk stays connected, then imaging it with something like Disk Drill’s byte-to-byte backup makes more sense than scanning the WD over and over. After that, experiment on the image or on a recovered copy, not on the only copy of your files. Only when the data is somewhere else would I try CHKDSK, partition repair, or formatting.