Cannot use USB External Hard Drive

I knew that. But this better than totally not working anymore.

I can tolerate some lack of performance and functionality, but I can't tolerate being completely unusable.

When MS resolved this problem by giving an update or release a build, UAS support will be restored automatically (cause file uaspstor.sys will be updated).

Finally, Microsoft did not give any timepoint for fixing the problem, and this stupid issue alread bother me for almost one month, I cann't accept this anymore.

BTW, I had tried rollback to a working build to wait for MS fixing this issue. But rollback failed, god know why.

Yes, with every other computer the external drives can be read. (I have two external drives).

I have tried using Linux, they can be read. Using very old Windows 8 machine, they can be read.

I am now using Windows 10 Pro 1903 build 19013.1000.

Andre's post is not relevant, I think. But, if you must know, after plugging the hard drives, they are not listed in Disk Management console.

The error I see in Device Manager. It is under Storage Controllers. There are USB Attached SCSI (UAS) Mass Storage Device appear with yellow triangle with exclamation mark in it. Right click on it and choose Properties (or just double click it) shows Device Status:

"This device cannot start. (Code 10)

{Not Enough Quota}

Not enough virtual memory or paging file quota is available to complete the specified operation."

Then I check the Events tab. Here is the log chronologically (7 events):

"Device USB\VID_2537&PID_1068\MSFT300123456789ABCDE was migrated.

Last Device Instance Id: USB\VID_2537&PID_1068\MSFT300123456789ABCDE

Class Guid: {4d36e97b-e325-11ce-bfc1-08002be10318}

Location Path: 

Migration Rank: 0x0

Present: false"

"Device USB\VID_2537&PID_1068\MSFT300123456789ABCDE was configured.

Driver Name: uaspstor.inf

Class Guid: {4d36e97b-e325-11ce-bfc1-08002be10318}

Driver Date: 06/21/2006

Driver Version: 10.0.19013.1

Driver Provider: Microsoft

Driver Section: UASPort_Install_Control

Driver Rank: 0xFF2000

Matching Device Id: USB\Class_08&SubClass_06&Prot_62

Outranked Drivers: 

Device Updated: false

Parent Device: USB\ROOT_HUB30\4&23ace5cb&0&0

"

"Device USB\VID_2537&PID_1068\MSFT300123456789ABCDE had a problem starting.

Driver Name: uaspstor.inf

Class Guid: {4d36e97b-e325-11ce-bfc1-08002be10318}

Service: UASPStor

Lower Filters: 

Upper Filters: 

Problem: 0xA

Problem Status: 0xC0000017

"

"Device USB\VID_2537&PID_1068\MSFT300123456789ABCDE was deleted.

Class Guid: {4d36e97b-e325-11ce-bfc1-08002be10318}

"

"Device USB\VID_2537&PID_1068\MSFT300123456789ABCDE was not migrated due to partial or ambiguous match.

Last Device Instance Id: USB\VID_0951&PID_1666\60A44C3FAC1CBDB0C96B15E4

Class Guid: {36fc9e60-c465-11cf-8056-444553540000}

Location Path: PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(5)

Migration Rank: 0xF000FFFFC0000023

Present: false

Status: 0xC0000719

"

"Device USB\VID_2537&PID_1068\MSFT300123456789ABCDE was configured.

Driver Name: uaspstor.inf

Class Guid: {4d36e97b-e325-11ce-bfc1-08002be10318}

Driver Date: 06/21/2006

Driver Version: 10.0.19013.1

Driver Provider: Microsoft

Driver Section: UASPort_Install_Control

Driver Rank: 0xFF2000

Matching Device Id: USB\Class_08&SubClass_06&Prot_62

Outranked Drivers: 

Device Updated: false

Parent Device: USB\ROOT_HUB30\4&23ace5cb&0&0

"

"Device USB\VID_2537&PID_1068\MSFT300123456789ABCDE had a problem starting.

Driver Name: uaspstor.inf

Class Guid: {4d36e97b-e325-11ce-bfc1-08002be10318}

Service: UASPStor

Lower Filters: 

Upper Filters: 

Problem: 0xA

Problem Status: 0xC0000017

"

I am having the same exact issue.  My drive works on every other PC I own except for the one running Windows 10 Pro 1903 build 19030.1

It looks like this issue is acknowledged in the 'Known Issues' section of the latest Insider build. 

https://blogs.windows.com/windowsexperience/2019/11/19/announcing-windows-10-insider-preview-build-19028/

So at least we know Microsoft is aware of the problem and we'll hopefully see it fixed soon. The bad news is, of course, that it's not fixed yet. 

Can't believe Microsoft finally start investgation this issue after almost one month....

But I found a workaround: using WinPE or Sudo utility, rename C:\Windows\System32\Drivers\uaspstor.sys to uaspstor.sys.bak, copy USBSTOR.sys in place and rename to uaspstor.sys.

After reboot machine, my external HDD works again.

So, obviously, this issue was related to uaspstor.sys, aka UASP driver.

WinPE or Sudo utility?  I am not familiar with either utility.

Hi all,

My current workaround is to re-attach the drive until it is recognized by Windows.

This is strange, somehow Windows is rejecting my drive repeatedly saying sorry you don't have enough quota, and then boom, OKyou can come in. There is no pattern however. I initially thought Windows allow the drive to connect on every third trial, but no. Yesterday I have to do it almost eleven times.

And, this may be dangerous for the external drive, and the USB port(s).

I found out about this when I tried to record the error by reproducing it. My first attempt to reproduce the problem failed miserably, the drive is connected with no problem at all. Before that, I tried several times, including other USB ports. Then I decided to file a bug, and the drive was connected. :))

Well, of course I tried to record the bug again, and that time the problem was reproduced.