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.
![](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(89.60000000000001, 72%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESI%3C/text%3E%3C/svg%3E)
Hi Dapid,
I am Sumit, an Independent Advisor and a 2-Year Windows Insider MVP here to help.
As this is an a Insider build, you expect to see bugs. Please note that as development progresses of Vibranium branch more bugs would be noticed.
The immidiate fix is to rollback to 19009 by going into Settings>Update and Security>Recovery.
