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 have the same problem too.
Using an ORICO external SSD enclosure with a Samsung 960 EVO SSD attached.
Sometimes its Code 10, sometimes its 38.
Nothing wrong with the external SSD or enclosure, tested it on Ubuntu and another Windows 10 Release.
BUT....
sometimes it works, if I disable the driver with the yellow ! mark, but it falls back to usb2.0 speeds (50MB/s) from 480MB/s.
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.
WinPE or Sudo utility? I am not familiar with either utility.
Why need sudo?.... generally speaking, uaspstor.sys was system file and was under protect by Windows, you need TrustInstaller privilege to modify it. NSudo(you can download it from https://github.com/M2Team/NSudo/releases/tag/6.2) can let you have a cmd with trustinstaller privilege, so you can modify uaspstor.sys(rename it and use usbstror.sys to replace it) without break system integrity.
thanks.
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.
WinPE or Sudo utility? I am not familiar with either utility.
Why need sudo?.... generally speaking, uaspstor.sys was system file and was under protect by Windows, you need TrustInstaller privilege to modify it. NSudo(you can download it from https://github.com/M2Team/NSudo/releases/tag/6.2) can let you have a cmd with trustinstaller privilege, so you can modify uaspstor.sys(rename it and use usbstror.sys to replace it) without break system integrity.
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.
WinPE or Sudo utility? I am not familiar with either utility.
