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.
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/
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.
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.
