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: Most helpful
  1. Anonymous
    2020-02-01T04:02:42+00:00

    The (Code 10) error with enclosure iDsonix, (Not enough quota), has been fixed by MS in insider build 19555.1001.

    The uaspstor.sys in build 19555 is dated 1/27/2020 and fixed this particular bug.

    There were other problems with different enclosures that need to be checked out.

    Have you had a chance to try this build and verify it works for you or are you going by what it says in the release notes? 

    unpvg, 

    I had 2 different problems that were occurring with any previous 20H1 Build:

    1. iDsonix enclosure with any Sata HDD was getting "This device cannot start (Code 10) not enough quota, this was a solid bug.
    2. A 2TB Sata WD HDD in a Sabrent enclosure was disconnecting during Image backup after 10-15 minutes and never completed the backup.

    With Build 19555.1001 both my problems are fixed. See uaspstor.sys size and date here.

    I have other enclosures Zheino with mSata SSDs and a different model of Sabrent with a 2.5" Adata SSD and those work fine too, but they did not fail before either.

    There are many different brands of enclosures for USB attached SCSI, I can only speak for the ones I have.

    Good luck !

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-02-01T03:24:01+00:00

    The (Code 10) error with enclosure iDsonix, (Not enough quota), has been fixed by MS in insider build 19555.1001.

    The uaspstor.sys in build 19555 is dated 1/27/2020 and fixed this particular bug.

    There were other problems with different enclosures that need to be checked out.

    Have you had a chance to try this build and verify it works for you or are you going by what it says in the release notes?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-01-30T21:03:03+00:00

    The (Code 10) error with enclosure iDsonix, (Not enough quota), has been fixed by MS in insider build 19555.1001.

    The uaspstor.sys in build 19555 is dated 1/27/2020 and fixed this particular bug.

    There were other problems with different enclosures that need to be checked out.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-01-29T15:57:21+00:00

    The latest official MS ISO is 18363.418.

    This came from the MS ISO 18363.418, not sure why your file has a later date, since the files are identical when I compare them, just the date is different.

    The actual digital signature was on Sept 23, 2019 for 18362.387 file version.

    The ISO I used was download from MSDN.

    That may explain the different date. 

    The one from the 18363.592 ISO is now dated 1/9/2020, but the file is still version  10.0.18362.387 and the file content is identical to the old one from September 2019.

    Was this answer helpful?

    0 comments No comments