Your external SSD connects successfully through a USB-C hub.

The drive appears in File Explorer. Files open normally. Transfers work.

But when you inspect the storage device in Windows, you discover that it is not using USB Attached SCSI Protocol (UASP). Instead, Windows appears to be using the traditional USB Mass Storage path.

Or perhaps the same SSD uses UASP when connected directly to the laptop but falls back after you add a USB-C hub.

That does not automatically mean the SSD or hub is defective.

The first thing to understand is:

UASP and USB link speed are different properties of the storage connection.

UASP describes how storage commands are transported.

5Gbps or 10Gbps describes the USB data-link speed.

To diagnose a fallback correctly, identify both before running another benchmark.

Give the SSD a Protocol Identity

Before changing cables or drivers, record three things:

Now you can distinguish several very different situations.

UASP + 10Gbps

The expected storage transport and high-speed USB path are both active.

USB Mass Storage + 5Gbps

The device may still have a SuperSpeed USB connection, but UASP is not active.

USB Mass Storage + 480Mbps

The connection may also have fallen back to a USB 2.0-class path.

These should not be diagnosed as the same problem.

What UASP Actually Changes

UASP stands for USB Attached SCSI Protocol.

USB-IF maintains the official USB Attached SCSI Protocol specification as a USB mass-storage transport specification.

Windows also distinguishes its storage-driver paths.

Microsoft's USB device class driver documentation lists:

Uaspstor.sys for supported SuperSpeed USB mass-storage devices using UAS,

and:

Usbstor.sys for conventional USB mass-storage devices.

The important takeaway is:

UASP is a storage transport protocol—not another name for USB 3.0, USB-C, 5Gbps, or 10Gbps.

A USB-C connector alone tells you nothing about whether UASP is active.

Check What Windows Is Actually Using

Do not infer UASP from transfer speed alone.

Open Device Manager and inspect the external storage device and its related storage-controller entry. The exact location can vary with the enclosure and Windows configuration.

Open Properties → Driver → Driver Details.

You are looking for the storage-driver path.

Uaspstor.sys

Windows is using the UASP path.

Usbstor.sys

Windows is using the traditional USB Mass Storage path.

This is more useful than saying:

“My SSD copied at 500 MB/s, so UASP must be enabled.”

Sequential transfer speed alone does not reliably identify the transport protocol.

Add the Actual USB Link Speed

Next determine what USB speed the SSD negotiated.

A 10Gbps enclosure can still operate at:

5Gbps

or:

480Mbps

if another component in the path limits the connection.

Use the LENTION guide for checking the actual USB link speed on Windows and macOS rather than relying only on the speed printed on the SSD enclosure.

Now combine the two results:

Transport Mode + USB Link

That combination tells you where to look next.

Read the Four Most Important Combinations

1. UASP Active + Expected SuperSpeed Link

Example:

Uaspstor.sys

10Gbps link

If the SSD is still slow, stop troubleshooting UASP.

Look instead at:

• sustained SSD write speed;
• SLC cache;
• thermal throttling;
• destination drive;
• file workload;
• shared hub bandwidth.

If large copies begin extremely fast and later collapse, the more relevant issue is covered in the guide to large file copy speeds that start fast and then drop.

UASP can be working perfectly while another storage bottleneck limits throughput.

2. USB Mass Storage + SuperSpeed Link

This is the most UASP-specific result.

Suppose Windows uses:

Usbstor.sys

while the USB connection is still running at a SuperSpeed rate.

Now inspect the storage enclosure itself.

The path is:

Windows

→ USB Host

→ USB-C Hub

→ USB Bridge Controller

→ SSD

The USB-to-NVMe or USB-to-SATA bridge inside the enclosure must expose the appropriate storage protocol. Windows cannot simply force UASP onto hardware that does not present it correctly.

This is why two enclosures containing the same SSD can behave differently.

Test the Enclosure Before Blaming the Hub

If your SSD uses traditional USB Mass Storage even when connected directly to the laptop, the hub is unlikely to be what removed UASP.

Check whether the enclosure explicitly supports:

UASP / UAS

rather than assuming support from labels such as:

USB 3.1

USB 3.2

10Gbps

or:

NVMe

These describe different capabilities.

If you want to isolate the enclosure or bridge controller as a variable, testing the SSD in a 10Gbps USB-C M.2 SSD enclosure with explicit UASP support provides a useful comparison.

The LENTION C9Elite explicitly lists UASP support, USB transmission up to 10Gbps, the RTL9210B bridge controller, compatibility with NVMe and NGFF/SATA M.2 SSDs, and support for 2230/2242/2260/2280 sizes.

For example:

Original enclosure → Usbstor.sys

but:

Same compatible SSD in C9Elite → Uaspstor.sys

would strongly suggest that the original enclosure, bridge controller, or its firmware was part of the protocol difference.

That is a diagnostic comparison—not a guarantee that changing the enclosure will make every SSD faster.

3. UASP Direct → USB Mass Storage Through Hub

This result points somewhere else.

Suppose:

Direct Connection

Uaspstor.sys

Through USB-C Hub

Usbstor.sys

Now you have already proved that:

• Windows supports the UASP device;
• the enclosure can expose UASP;
• the SSD works through that enclosure;
• the direct host path supports it.

Something changes only after the hub is added.

Check:

hub data port

→ hub host connection

→ cable

→ negotiated USB link

→ device enumeration

Do not start by replacing the SSD.

Verify the Hub Is Providing a Real SuperSpeed Data Path

A USB-C hub does not inherently disable UASP.

A compatible SuperSpeed hub can sit between the computer and SSD while the storage device continues to use UASP.

The clean comparison is:

SSD Direct → UASP/BOT + Link Speed

versus:

SSD Through Hub → UASP/BOT + Link Speed

For a workflow built around multiple high-speed USB-C storage devices, a USB-C hub with four USB 3.2 Gen 2 10Gbps data ports provides a straightforward high-speed data topology to test.

The LENTION CE31s specifies:

• 4 × USB-C USB 3.2 Gen 2 data ports;
• up to 10Gbps per data connection;
• up to 100W PD pass-through;
• a separate PD input for host charging and additional peripheral power.

Its four downstream USB-C ports are explicitly data-only rather than video or charging outputs.

This is useful for a setup such as:

USB-C SSD

Second USB-C storage device

Other USB-C peripherals

without repeatedly converting those devices through USB-A adapters.

But one distinction matters:

Four 10Gbps downstream ports do not create four independent 10Gbps upstream links.

Simultaneously active devices still share the hub's upstream connection.

So if UASP remains active but two SSDs slow each other down during simultaneous transfers, you have moved from a protocol problem to a shared-bandwidth problem.

4. USB Mass Storage + 480Mbps

This is a broader fallback.

If the SSD should support USB 3.x but is now operating around:

480Mbps

investigate the physical USB path first.

Possible causes include:

• USB 2.0 port;
• USB 2.0-only cable;
• lower-speed adapter;
• incorrect hub port;
• failed SuperSpeed negotiation.

Microsoft identifies Uaspstor.sys as the Windows class driver for supported SuperSpeed UAS mass-storage devices, so losing the expected SuperSpeed path can coincide with losing the UASP storage path as well.

If this is your result, use the dedicated guide for an external SSD falling back to USB 2.0 speed through a USB 3.x hub.

Fix the connection mode before optimizing storage performance.

5Gbps Does Not Mean UASP Failed

Suppose your SSD supports 10Gbps but is connected through a 5Gbps USB data port.

Windows can still use:

Uaspstor.sys

The SSD simply has a lower USB bandwidth ceiling.

So:

UASP + 5Gbps

is fundamentally different from:

USB Mass Storage + 480Mbps

Think of it this way:

USB Link Speed = road capacity

UASP / BOT = how storage commands travel on that road

A 5Gbps road can still carry UASP.

UASP Active Does Not Guarantee Maximum SSD Speed

The reverse assumption is also wrong.

Seeing:

USB Attached SCSI

does not mean the SSD will automatically deliver its advertised maximum speed.

Performance can still be limited by:

• USB link speed;
• NAND performance;
• SSD cache;
• temperature;
• enclosure controller;
• file system;
• small-file workload;
• destination storage;
• other devices sharing the hub.

For example:

UASP + 5Gbps

can be perfectly healthy while still being slower than:

UASP + 10Gbps

because the transport protocol is the same but the available USB bandwidth differs.

Do Not Benchmark UASP With Only One Large File

UASP's usefulness is not limited to sequential copies.

Real storage workloads can include:

multiple file requests

random access

application data

many small files

concurrent reads and writes

So a single 20GB video copy is not the best way to decide whether UASP exists.

Confirm the transport through Windows device/driver information first.

Then benchmark the workload you actually care about.

The correct sequence is:

Identify Protocol

→ Verify USB Link

→ Measure Workload

not:

Benchmark → Guess Protocol

Firmware Can Matter Too

USB-to-NVMe and USB-to-SATA bridge controllers have firmware.

Firmware can influence:

• device compatibility;
• sleep behavior;
• disconnect behavior;
• enumeration;
• storage-command handling.

If your enclosure manufacturer provides an official firmware update that specifically addresses compatibility, follow its instructions.

Avoid flashing random bridge-controller firmware from unofficial sources.

A failed firmware update can create a much more serious storage problem than the UASP fallback you started with.

When Should You Change Hardware?

Use the identity results rather than buying hardware at random.

Enclosure Never Uses UASP

If:

Direct = Usbstor.sys

and:

Hub = Usbstor.sys

focus first on the enclosure/bridge.

Testing the SSD in a UASP-enabled 10Gbps M.2 enclosure can help isolate whether the original bridge is the limiting layer.

UASP Works Directly but Not Through the Hub

If:

Direct = Uaspstor.sys

but:

Hub = Usbstor.sys

focus on:

hub port

cable

host connection

link negotiation

and:

hub enumeration

A 10Gbps USB-C hub with clearly specified SuperSpeed USB-C data ports provides a different high-speed hub path to validate.

UASP Is Already Active but Performance Is Low

Do not keep troubleshooting UASP.

Move to:

link speed

cache

thermal behavior

sustained write speed

shared bandwidth

and:

file workload.

Use This UASP Result Map

This is the most important table in the article because it separates:

Storage Protocol

from:

USB Link

from:

Real Throughput.

Quick Answers

What does UASP mean?

UASP is USB Attached SCSI Protocol, a USB storage transport designed for SCSI-based storage communication.

How can I check whether UASP is active in Windows?

Inspect the storage device's driver path. Uaspstor.sys indicates the Windows UASP path, while Usbstor.sys indicates conventional USB Mass Storage.

Is USB Mass Storage the same as USB 2.0?

No. A storage device can use the older USB Mass Storage transport while still operating over a SuperSpeed USB link.

Can a 5Gbps USB-C hub support UASP?

Yes. UASP and USB link speed are separate. A compatible 5Gbps SuperSpeed connection can still use UASP.

Does UASP guarantee the SSD's maximum advertised speed?

No. SSD performance still depends on link speed, NAND, cache, temperature, enclosure, workload, and destination storage.

Why does UASP work directly but disappear through my hub?

That result suggests something changes in the added USB path. Check the hub data port, cable, negotiated link, host connection, and device enumeration.

Final Takeaway

When UASP is not active through a USB-C hub, do not start with another speed benchmark.

Identify the SSD's protocol identity first:

Uaspstor.sys or Usbstor.sys?

Then determine:

10Gbps, 5Gbps, or 480Mbps?

Finally compare:

Direct vs. Hub

The most important rule is:

UASP describes the storage transport protocol; 5Gbps or 10Gbps describes the USB link speed. They are not the same thing.

If:

Direct = UASP

but:

Hub = USB Mass Storage

investigate the added hub path.

If:

Direct = USB Mass Storage

and:

Hub = USB Mass Storage

investigate the enclosure, bridge controller, firmware, and host support.

And if:

UASP is already active

but the SSD remains slow, stop troubleshooting UASP and look for the actual storage bottleneck.

Once protocol, link speed, and throughput are separated, a vague “my SSD fell back to USB Mass Storage” problem becomes much easier to diagnose.