This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I am using Windows 10 Pro Build 19013.vb_release.191025-1609. Now I cannot use external hard drives.
When plugging external hard drive I can hear the sound of something is connected. But, the drive never displayed in This PC.
Checking Disk Management, the disk is not even there.
Checking Device Manager, one device is malfunction: USB Attached SCSI (UAS) Mass Storage Device.
The device status is:
"
This device cannot start. (Code 10)
{Not Enough Quota}
Not enough virtual memory or paging file quota is available to complete the specified operation.
"
I don't understand this error.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
EDIT: This appears to have now been fixed in the following build
It looks like this issue is acknowledged in the 'Known Issues' section of the latest Insider build.
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.
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
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.
This essentially kills support for UAS and negatively impacts the performance of the drive. If the external drive is an SSD, you also lose support for important functionality. I'd rather sit on a working Insider build until this is fixed. See
https://winaero.com/blog/check-if-your-usb-3-0-device-supports-usb-attached-scsi-uas-protocol/
Yikes, thanks for the heads up. I was thinking of trying that, glad I didn't.
This essentially kills support for UAS and negatively impacts the performance of the drive. If the external drive is an SSD, you also lose support for important functionality. I'd rather sit on a working Insider build until this is fixed. See
https://winaero.com/blog/check-if-your-usb-3-0-device-supports-usb-attached-scsi-uas-protocol/
