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.
Really, I've been waiting for months for a fix...and Microsoft wants me to update my Windows 7 systems that work fine and load these drives without any issues . I'll take my chances without their poorly tested updates any day. In fact. my windows XP systems are the most reliable systems I maintain to date.
Asc6666,
The bug I have seen with USB attached SCSI driver uaspstor.sys is only occurring with the builds of windows 10 insider previews.
I don't have any issues with the current public release of windows 10 v 1903 or 1909.
All my USB attached SCSI devices work fine on USB 3.0 or 3.1 with the uaspstor.sys 18362.387 dated 10/6/2019.
I don't understand why MS is taking so long to propagate the same good driver to the new insider preview builds.
Also keep in mind that some of these enclosures use a different protocols when connected to a USB 2 port and when they are connected to a USB 3 port, some other enclosures use uaspstor.sys on either ports.
Here is a sample of an iDsonix enclosure (NS106X) that uses 2 different drivers on USB 2 with (usbstor.sys) and USB3 with uaspstor.sys.
With this particular device the bug is only occurring when connected to a USB 3 port, see below the error with build 19551.1005.
The same device works fine with current public build v 1909 build 18363.592 (uaspstor.sys 18362.387 dated 10/6/2019), any uaspstor.sys of insider builds fails with the error shown in the last picture below.
Device connected on USB 2.0 port:
Device connected on USB3.0 port.
Really, I've been waiting for months for a fix...and Microsoft wants me to update my Windows 7 systems that work fine and load these drives without any issues . I'll take my chances without their poorly tested updates any day. In fact. my windows XP systems are the most reliable systems I maintain to date.
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?
KentonGreen,
The bad file to replace uaspstor.sys is in C:\Windows\System32\Drivers.
If you have a system with the current public release v 1909 installed you can copy the good uaspstor.sys dated 10/06/2019 from C:\Windows\System32\Drivers to usb stick and put it in a temporary folder on the insider system that has the problem.
Then you will need to use a command prompt from a recovery environment to replace the bad one in C:\Windows\System32\Drivers.
mwong009,
Yours is just a workaround, I have some that work too with 20H1, but some fail with different errors.
All my enclosures were purchased from Amazon and work fine with current release code v1909 Build 18363.592.
MS has acknowledged the bug, but it takes forever to get it fixed (Device cannot start Code 10).
If I copy the uaspstor.sys dated 10/06/2019 from the current release build v 1909 and replace the bad one in any of the 20H1 insider builds everything works fine.
The only problem is that sfc /scannow will not like it because it does not match the manifest for the insider release and it will put back the bad driver if you run sfc /scannow.
MS needs to release the working driver with the proper signature, it is not difficult at all for MS since it is their own driver. They are just getting lazy.
The driver uaspstor.sys is in C:\Windows\System32\Drivers.
The one in the v 2004 and 20H1 builds is missing a bunch of updates to support correctly the USB attached SCSI devices, the one in the current public release v 1909 works perfectly.
