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.
The file in my package was extracted from Windows 10 1909 updated Dec 2019, so was newer than yours.
This package was a tempoary workaround ofcause. Still waiting for MS fixing, and can not using any utility such as sfc, file will be restored.
That is strange, because even with today's update to build 18363.628 the uaspstor.sys file is still dated 10/6/2019 just a slightly different time from the previous one, yet the content is identical to the file in your zip.
Perhaps it was copied without preserving the date and time ? Unless the packages for different countries have different dates ?
I don't think the date of the driver is depending on the time you do the update, but when the file was originally created.
Directory of C:\Windows\System32\drivers
10/06/2019 06:56 PM 79,376 uaspstor.sys
1 File(s) 79,376 bytes
0 Dir(s) 420,104,019,968 bytes free
I didn't made any changes to this file. This file was extract from MSDN ISO image file, "cn_windows_10_business_editions_version_1909_updated_dec_2019_x64_dvd_262ac8af.iso", you can verfied it yourself.
And you can also take look at the digital signature of uaspstor.sys:
It was signed on 2019-12-07 08:59:27, so it was newer than yours absolutely.
The file in my package was extracted from Windows 10 1909 updated Dec 2019, so was newer than yours.
This package was a tempoary workaround ofcause. Still waiting for MS fixing, and can not using any utility such as sfc, file will be restored.
That is strange, because even with today's update to build 18363.628 the uaspstor.sys file is still dated 10/6/2019 just a slightly different time from the previous one, yet the content is identical to the file in your zip.
Perhaps it was copied without preserving the date and time ? Unless the packages for different countries have different dates ?
I don't think the date of the driver is depending on the time you do the update, but when the file was originally created.
Directory of C:\Windows\System32\drivers
10/06/2019 06:56 PM 79,376 uaspstor.sys
1 File(s) 79,376 bytes
0 Dir(s) 420,104,019,968 bytes free
The file in my package was extracted from Windows 10 1909 updated Dec 2019, so was newer than yours.
This package was a tempoary workaround ofcause. Still waiting for MS fixing, and can not using any utility such as sfc, file will be restored.
iFish,
The uaspstor.sys in your zip file is dated 12/4/2019 5:09PM, the MS good one (Ver 10.0.18362.387) that I find in my systems is dated 10/6/2019 5:31PM.
The files look the same and work fine, but why is the date different ?
Also be aware that just replacing the file in C:\Windows\system32\Drivers is only a temporary fix.
The driver must be installed with the correct signature or it will not match the manifest for the different build.
If you run sfc /scannow it will think the file is corrupted and replace it back with the bad one from the insider build, see screen shot below.
We need the proper installation package signed by MS to avoid the uaspstor.sys from been reverted back to the bad one.
