Dear Windows 10 insiders,
I have an Orico external storage drive adapter (for HDD, SSD, etc). Since approximately the 7th of September my desktop powered by Windows 10 insider builds no longer mounts my external HDD. The drive is properly being recognized if I plug it into my Surface Pro so it cannot be the drive's fault. The drive indicator does light up when plugging in but shuts off quickly after.
Under device manager there is this yellow triangle with exclamation mark for the item "Per USB angeschlossenes SCSI (UAS)-Massenspeichergerät" (pardon my German). Then if I go into properties it says for the status:
Does anyone else experience the same or similar issue? I am afraid that Microsoft could ship a faulty Windows build to release (the issue has persisted for several builds already).
Please note that I also asked for help at tenforums.com.
EDIT: After talking with some friendly people I have managed to reduce the issue to USB 3.0 not working correctly. I wonder if there is any other person out there who cannot get an external HDD powered by USB 3.0 to work on latest insider builds? Maybe we happen to share the same or simliar chipset: Intel Z97? The work-around in my case is downgrading the USB 3.0 ports to USB 2.0 by disabling Intel xHCI in the BIOS.
I have an Orico external storage drive adapter (for HDD, SSD, etc). Since approximately the 7th of September my desktop powered by Windows 10 insider builds no longer mounts my external HDD. The drive is properly being recognized if I plug it into my Surface Pro so it cannot be the drive's fault. The drive indicator does light up when plugging in but shuts off quickly after.
Under device manager there is this yellow triangle with exclamation mark for the item "Per USB angeschlossenes SCSI (UAS)-Massenspeichergerät" (pardon my German). Then if I go into properties it says for the status:
Something about not having enough available virtual memory or page file space.Das Gerät kann nicht gestartet werden. (Code 10)
{Nicht genügend Quoten}
Für den angegebenen Vorgang sind nicht genügend Quoten für virtuellen Speicher oder die Auslagerungsdatei vorhanden.
Does anyone else experience the same or similar issue? I am afraid that Microsoft could ship a faulty Windows build to release (the issue has persisted for several builds already).
Please note that I also asked for help at tenforums.com.
EDIT: After talking with some friendly people I have managed to reduce the issue to USB 3.0 not working correctly. I wonder if there is any other person out there who cannot get an external HDD powered by USB 3.0 to work on latest insider builds? Maybe we happen to share the same or simliar chipset: Intel Z97? The work-around in my case is downgrading the USB 3.0 ports to USB 2.0 by disabling Intel xHCI in the BIOS.
Last edited: