You connect an external HDD, SSD, or USB drive through a USB-C hub.

Windows detects it.

The drive may even appear normally in File Explorer.

But the moment you double-click it, Windows responds:

Location is not available.
The parameter is incorrect.

That message is frustrating because it sounds specific while telling you very little about the actual problem.

It does not automatically mean the USB-C hub is defective, and it does not prove the drive itself has failed.

The safest approach is to treat this as a storage-access problem first and a USB-C hub problem second.

Before trying to repair anything, determine what Windows can still see.

Stop: Protect the Data Before You Repair the Drive

If the drive contains important photos, work files, backups, or anything that cannot easily be replaced, do not begin by formatting it.

Also avoid immediately running every disk-repair command you find online.

Some Windows storage commands make changes to the file system.

That is useful when the volume is healthy enough to repair—but it is not the first thing you want to do if:

• the drive is repeatedly disconnecting;
• Windows reports RAW;
• capacity suddenly looks wrong;
• the HDD is clicking or restarting;
• the drive is disappearing during transfers;
• the same drive fails on multiple computers.

Use this simple rule:

If the data matters, diagnose before you modify.

If the drive is still readable intermittently, prioritize copying critical files before long troubleshooting sessions.

Read the Drive State Before Reading the Error Message

Instead of repeatedly opening the drive in File Explorer, open:

Start → Disk Management

Locate the external disk by its physical capacity.

For example, a 1TB drive should still appear roughly as a 1TB physical disk.

Now look at what Windows actually reports.

This is more useful than the wording “The Parameter Is Incorrect.”

The Windows dialog tells you the access request failed.

Disk Management tells you what state the storage device is actually in.

If Windows now reports the volume as RAW or 0 bytes—especially after an unsafe disconnect—use our dedicated guide to an external drive showing RAW or 0 bytes after a USB-C hub disconnect before attempting formatting or repair.

Green, Yellow, or Red? Put the Drive in the Right Risk Zone

Before changing anything, classify the drive.

GREEN — The Drive Looks Normal in Disk Management

Typical signs:

Correct capacity
NTFS or exFAT still recognized
Drive remains continuously connected
No unusual HDD noises

This is the safest situation for normal Windows troubleshooting.

Proceed to the direct-connection comparison below.

YELLOW — Windows Sees the Disk but Something About the Volume Is Wrong

Examples:

No drive letter
RAW file system
Volume will not mount
Drive becomes read-only
File Explorer errors despite correct capacity

Do not format immediately.

If the SSD is accessible but suddenly refuses writes rather than refusing to open completely, see our separate guide to an external SSD becoming read-only through a USB-C hub.

RED — The Physical Drive Is Not Behaving Reliably

Examples:

0 bytes

No Media

wrong capacity

repeated disconnects

HDD clicks, spins down, or restarts

drive disappears while Windows is checking it

Do not make CHKDSK your first experiment here.

First stabilize or bypass the connection.

If an external HDD is physically restarting or making repeated abnormal sounds, use our external hard drive clicking or spinning down through a USB-C hub guide before continuing.

Now Ask the Most Important Question: Does the Error Follow the Drive or the Hub?

Run one A/B comparison.

Connection A

External Drive → USB-C Hub → Windows PC

Try opening the drive.

Record:

The Parameter Is Incorrect

or

Drive opens normally

Then safely disconnect it.

Connection B

Connect the same drive as directly to the computer as your available ports allow.

Use the same storage cable where possible.

Try opening it again.

Now you have one of three outcomes.

Result 1: The Error Appears Both Directly and Through the Hub

Stop focusing on the USB-C hub.

The problem is more likely somewhere in:

the drive → enclosure → file system → Windows storage configuration

Check Disk Management again and move to the Windows repair section below.

Result 2: The Drive Opens Directly but Fails Through the Hub

This is the strongest evidence that the intermediate connection matters.

Investigate:

• the hub USB port;
• hub-to-laptop connection;
• available USB power;
• storage cable;
• additional devices sharing the hub;
• laptop power state;
• whether the drive disconnects under load.

If the external SSD does not appear consistently at all through the hub, rather than merely giving a parameter error, our external SSD not detected through a USB-C hub guide covers that earlier stage of the problem.

Result 3: The Drive Works Sometimes and Fails Sometimes

Do not start file-system repair while the physical connection is unstable.

A repair process needs a connection that remains active.

If touching the cable, starting a large transfer, adding another USB device, or connecting/disconnecting the charger causes the drive to disappear, fix that instability first.

If Windows Recognizes the File System, Check Before You Repair

Suppose Disk Management still shows:

NTFS

or

exFAT

and the drive remains stable.

Windows includes CHKDSK for inspecting a volume's file system and file-system metadata.

Microsoft's official CHKDSK documentation explains an important distinction:

Running CHKDSK without repair parameters reports the volume status.

Running it with parameters such as /f instructs Windows to fix errors on the volume.

That difference matters.

Open Command Prompt as Administrator.

If the external drive is E:, start with:

chkdsk E:

This is an inspection step.

Do not automatically jump to:

chkdsk E: /f

or

chkdsk E: /r

on an unstable or irreplaceable drive.

When a repair command becomes more reasonable

Consider repair only after:

the connection is stable;

Windows identifies the file system;

the drive is not showing obvious hardware-failure symptoms;

and, ideally,

important accessible files have already been backed up.

If you proceed with chkdsk E: /f, understand that /f modifies the volume in order to repair file-system errors.

Do not disconnect the drive or hub while the operation is running.

What If Disk Management Shows No Drive Letter?

A detected volume without a drive letter may not appear normally in File Explorer.

Microsoft documents drive-letter assignment through Disk Management in its official Change a Drive Letter guide.

If your volume is healthy and Windows simply has not assigned a letter:

1. Open Disk Management.
2. Find the correct external volume by capacity.
3. Right-click it.
4. Choose Change Drive Letter and Paths.
5. Select Add if no letter is assigned.
6. Choose an available letter.
7. Apply the change.

Be absolutely certain you have selected the external volume.

Do not modify your Windows system partitions.

Also note that this fix applies to a healthy mountable volume with a missing drive letter.

It will not repair a drive that is RAW, physically unstable, or incorrectly reporting its capacity.

What If the Drive Shows RAW?

RAW changes the problem.

Windows is seeing the storage device, but it is not recognizing the volume as a normal supported file system.

Do not respond to RAW by immediately clicking:

Format

if you need the existing data.

Formatting creates a new file system; it is not the same thing as repairing access to the existing one.

Instead:

stop writing to the drive → verify the physical connection → test another computer/direct connection → decide whether data recovery is needed

before reformatting.

The key question becomes:

Is this a file-system problem on a healthy drive, or is an unstable connection continuing to damage access?

That is why the direct-vs-hub comparison should happen before destructive steps.

If It Works Directly but Fails Through the Hub, Rebuild the Hub Test

Now simplify the setup.

Start with:

Laptop → USB-C Hub → External Drive

Disconnect:

• HDMI monitor;
• webcam;
• phone charging;
• capture card;
• second storage drive;
• card reader;
• printer;
• unnecessary USB accessories.

Try opening the drive again.

If it now works

Reconnect the devices one by one.

The first device that causes storage instability is a useful clue.

The issue may involve:

available power, host bandwidth, or the hub resetting under combined load.

If the drive still fails by itself

Try another USB data port on the hub.

Do not connect the external drive to a USB-C port marked only:

PD

Power Delivery

Charging

or similar wording unless the product specifically says that port supports data.

Stable Power Matters More With External Storage

An external HDD or SSD is not the same type of load as a keyboard.

Storage can draw more power and can change its demand during:

• startup;
• mounting;
• large transfers;
• sustained writes;
• SSD controller activity.

If the drive works directly but becomes unstable when several peripherals share one hub, adding stable external power to the hub can be useful.

For a workstation that needs a hard drive alongside other USB accessories, a USB-C hub with three 5Gbps USB 3.0 ports and up to 100W PD pass-through can keep data peripherals on dedicated USB ports while the PD input supplies additional power to the connected setup.

The current configuration specifically supports external hard disks through its USB 3.0 ports and uses PD input to provide additional power to hard drives and other accessories.

That does not mean a powered hub repairs corrupted storage.

Use it only when your A/B test has already shown:

the drive is healthy directly, while the original hub/power configuration is unstable.

Don't Forget the Enclosure Between Windows and the SSD

An external SSD may actually be several components:

M.2 SSD → enclosure controller → USB cable → USB-C hub → computer

If the same M.2 SSD repeatedly disappears, becomes inaccessible, or throws errors through one enclosure, the enclosure itself is another variable worth isolating.

For compatible M.2 drives, a 10Gbps USB-C M.2 enclosure supporting NVMe and NGFF/SATA SSDs can be used as a comparison enclosure to determine whether the original USB bridge, cable, or enclosure is involved.

Its current specification supports common 2230, 2242, 2260, and 2280 M.2 sizes and UASP on compatible systems.

This is an isolation test, not a data-repair tool.

If the same SSD remains unreadable in another known-good enclosure and on another computer, focus on the SSD and its data rather than continuing to replace hubs.

The Error Is Gone—Can You Trust the Drive Again?

Do not stop the moment File Explorer opens.

Before returning the drive to important work:

Open several existing files

Confirm they are actually readable.

Copy a noncritical test file from the drive

Confirm sustained reading works.

If the drive is writable, create a small test file

Eject the drive safely, reconnect it, and verify the file.

Transfer a larger noncritical file

Watch for:

• disconnect sounds;
• speed dropping to zero;
• drive disappearance;
• File Explorer freezing;
• HDD spin-down;
• repeated Windows errors.

If the problem returns under sustained transfer, the storage path is not yet reliable.

A drive that works for ten seconds is not the same as a stable external-storage setup.

Use This Final Decision Map

“The Parameter Is Incorrect” + correct capacity + recognized file system

→ Inspect the volume and connection.
→ Run non-repair CHKDSK first if appropriate.
→ Back up data before repair.

“The Parameter Is Incorrect” + RAW

→ Do not format if the data matters.
→ Test direct connection.
→ Treat as a file-system/recovery problem.

Error only through USB-C hub

→ Simplify the hub.
→ Check data port and power.
→ Add peripherals back individually.

Drive disappears while testing

→ Fix connection stability before file-system repair.

0 bytes / No Media / wrong capacity

→ Investigate enclosure, controller, cable, and drive hardware.

Works with another enclosure

→ Original enclosure/bridge becomes suspicious.

Fails directly, through the hub, and on another computer

→ Stop treating the USB-C hub as the primary cause.

Final Takeaway

When Windows says “The Parameter Is Incorrect” while opening an external drive through a USB-C hub, the error message should not be your diagnosis.

Your real evidence is:

What does Disk Management show?

Does the drive remain continuously connected?

Does it work directly?

Does Windows still recognize the file system?

Does the error follow the drive or only the hub connection?

Protect important data before attempting repair.

Then separate the two layers:

Storage layer: drive, file system, partition, enclosure.

Connection layer: USB-C hub, USB data port, cable, power, peripheral load.

If the problem follows the drive, troubleshoot the storage.

If the problem follows the hub path, troubleshoot the connection.

And if the drive is unstable in both places, data safety matters more than forcing Windows to open it one more time.