Cannot use USB External Hard Drive

Anonymous
2019-11-02T13:33:20+00:00

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.

Windows for home | Windows 10 | Devices and drivers

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.

0 comments No comments
Answer accepted by question author
Anonymous
2019-11-22T00:42:35+00:00

EDIT: This appears to have now been fixed in the following build

https://blogs.windows.com/windowsexperience/2020/01/30/announcing-windows-10-insider-preview-build-19555/

It looks like this issue is acknowledged in the 'Known Issues' section of the latest Insider build. 

https://blogs.windows.com/windowsexperience/2019/11/19/announcing-windows-10-insider-preview-build-19028/

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.

Was this answer helpful?

9 people found this answer helpful.
0 comments No comments

61 additional answers

Sort by: Oldest
  1. Anonymous
    2019-12-11T08:05:21+00:00

    This issue havn't been fixed for over one month.

    With latest version of windows 10 (version 2004, build 19041.1) this issue still not fixed yet.

    As I mentioned above, I was also in the same boat when I contacted "feedback hub".  They showed me that I was also running the latest Windows version (same as you), but a Beta version.  I did as was suggested (doing a clean install of Windows according to https://www.microsoft.com/en-us/software-download/windows10ISO) and with the exception of the 3 LACIE rugged FW USB3 SCSI Disk drives all my disks that were showing up with "yellow triangles" and wouldn't mount are now working perfectly on my new Surface Pro 7 just as they did on my "problematic Surface Pro 4".

    Give it a try.

    Sabina

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-12-11T08:15:08+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-01-26T04:04:58+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-01-26T17:08:45+00:00

    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?

    Was this answer helpful?

    0 comments No comments