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 also had the problem (which I posted earlier on and also on another similar thread
but I found that some ext usb controllers do work (because of the firmware?). It really depends on the manufacturer, maybe its a old firmware that conflicts with MS.
My trick was to buy every single brand of ext drive enclosure from Amazon, test each and every one of them, and send back those that didnt work.
i have tested a couple of ext ssd drive enclosures and I know for sure this specific model work flawlessly: https://www.amazon.co.uk/AmazonBasics-SATA-Hard-Drive-Enclosure/dp/B01N5RLG2C, I bought 4 more of these, and all work just fine, the other brands all show the yellow warning error.
Thank you THANK YOU fg2001, you've hit the nail on the head. We represent a silent-but-large number of people with a significant problem, we've learned to adapt but it leaves a bad taste and weakens Microsoft's customer base. Is the fix really that hard, MS?
@Fg2001: where can a reader of this thread find that 'good' copy of uaspstor.sys?
I have two devices running windows 10 insider build. All of them have different compatible problems with my external hdds.
However, my workaround still usable (as I posted on November 22, 2019 in this thread), so currently it was not a big problem to me.
This bug has been going on for months and MS still has not fixed it.
All it takes is to put back the good uaspstor.sys from build 18362.387 and everything works fine, but MS is not listening to the feedbacks.
It really sucks that it takes so long to fix something they just screwed up with the insider preview builds.
This still fails with build 19551.1005 on Jan 25 2020.
If I copy the file from the current 1909 release it works fine. The problem is there is no way to install the old good driver because it is not signed for the latest insider release, if you replace the file manually it will be restored when running sfc /scannow.
So there is not a clean way to put back the old driver.
I have two devices running windows 10 insider build. All of them have different compatible problems with my external hdds.
However, my workaround still usable (as I posted on November 22, 2019 in this thread), so currently it was not a big problem to me.
