Code 10 error in Device Manager in Win10 64-bit (both Home and Pro), with Adata USB3.0 drive - BUG?

[VirtualLarry]

Pulled out a brand-new Adata 16GB USB3.0 UV128 Yellow flash drive, opened the package, plugged it into my DeskMini's front USB3.0 port. Heard one chime from Windows, but not two. Doesn't show up in Explorer.exe or Disk Management console. Device Manager shows a USB Mass Storage Device, with a "Code 10 - Cannot Start - missing Device" error. Something about USBSTOR. On that same machine, an Emtec Click USB2.0 drive in the same port is recognized correctly, no problem.

So I fired up another machine, this one a Haswell H81 board, with front USB2.0 connected, and plugged it into the USB2.0 ports. Same deal. One chime, not two, and Code 10 in Device Manager.

I've tried with two brand-new Adata drives. Same deal.

So, it's not the hardware, it might be an incompatibility with the OS, something with a recent Win10 update, maybe? Either that, or I just got an entire bad batch of flash drives. These drives worked wonderfully for me in the past, I don't understand how the new batch could all be bad.

Any ideas?

The drives ARE recognized in the BIOS, on the DeskMini. Just not in Windows.

https://answers.microsoft.com/en-us...10-error/7152cb63-9258-e011-8dfc-68b599b31bf5

https://support.microsoft.com/en-us...rt-code-10-error-in-device-manager-in-windows

https://support.microsoft.com/en-us/help/2970908/how-to-use-microsoft-easy-fix-solutions

https://www.newegg.com/Product/Prod...1761&cm_re=Adata_UV128-_-20-211-761-_-Product

Hmm, several recent reviews, of multiple OOTB DOAs. Not a good sign. One fellow mentioned firmware errors, that he was able to fix with some sort of firmware tool from Adata.

Cons: FIRMWARE ON THESE IS COMPLETE GARBAGE. We bought 3, 2 had DOA firmware right out of the box. After using the ADATA update utility they came back to life for about 2 uses [300MB of writes] then died again. The one that wasnt DOA was so painfully slow that its embarrasing that its labeled as a USB3.0 device. USB 1.1 is closer to actual performance.

Other Thoughts: These drives serve more purpose being in a trash bin than holding any data of any kind as it will eventually corrupt itself.

I got to a USB flash drive online recovery page:
http://www.adata.com/en/ss/usbdiy/

Only, you have to enter the serial number, and the field that they give you to enter it, won't fit all the digits! WTF ADATA!?

I'm no longer going to recommend these drives, they have turned to GARBAGE. Two DOAs, in a row? Bad firmware? Bad tech-support page to back them up? Adata, clean up your ACT!

Now, I feel bad, that I ordered a pair of Adata SX8000 M.2 SSDs. If this is how they treat their flash drive customers, do they treat their SSD customers any better?

I noticed that they no longer offer Acronis downloads on their web site anymore, they only offer the free version of Macrium Reflect.

Edit: It gets MORE INTERESTING.

All three of the "bad" drives (plugged into multiple PCs, all running Win10 64-bit), WORKED FINE, plugged into a DeskMini, running Win7 64-bit SP1, with the Servicing Stack update (April 2016), July 2016 rollup, and the Cumulative Update Rollup v4.

So, looks like a defective driver in Win10 RS1? Affects some USB3.0 drives, but not USB2.0 drives?

Those people that say that Win10 "doesn't have bugs"... are lying.

 

[UsandThem]

I generally only use SanDisk Ultra or Samsung flash drives because I've had similar experiences using other drives in the past.

 

[VirtualLarry]

Bump for update - THE DRIVES WORK FINE IN WIN7 64-bit.

 

[XavierMace]

You get what you pay for.

 

[VirtualLarry]

You get what you pay for.

Referring to Windows 10's bugs?

 

[XavierMace]

No referring to your crappy thumb drives. I've had zero issue with the dozen plus San Disk drives I've got with a variety of Win10 computers.

 

[VirtualLarry]

No referring to your crappy thumb drives. I've had zero issue with the dozen plus San Disk drives I've got with a variety of Win10 computers.

Well, I'll see that comment, and raise you one.

When I was testing out a Dell Cherry Trail laptop, that was said in a review to be able to run Xubuntu, I put it on a (brand new) stubby Sandisk USB3.0 drive, the ones that are barely bigger than the USB port. Well, it wouldn't boot off of that drive. Gave me all kinds of weird errors.

So I put it on one of my "old reliable" Adata UV128 drives (one of my older-batch ones), and it booted just fine and smooth.

So, now I don't trust Sandisk drives, I think that they're junk.

Edit: When it failed to boot the first time, I used Rufus to do a write/read-test of the entire drive, before copying the ISO to it. It passed the testing, it wasn't "defective". Just incompatible.

Edit: Oh yeah, remember that "feature" of Sandisk drives, where they came from the factory configured with part of the storage space partitioned and formatted as a CD-ROM, and you had to download and run a special program from them, that required your e-mail to download, just to get all of the space on your thumb drive that you paid for? I do. That was one other reason I avoided Sandisk drives for a long time. Way too much hassle involved with them.

Until these recent Win10 updates, those Adata drives were always fine and reliable for me, and speedy too, even in a USB2.0 port.

Edit: I'm not denying that these drives might have a firmware problem, that might make them incompatible with Windows 10, but work just fine with Windows 7. This isn't the first instance of people using USB storage peripherals, that stopped working once they moved to Win10.

The wierd part is, the BIOS will see the drives fine, and prior-batch drives that were written with various OS boot disks (Linux and Windows), the Win10 system will see fine. Just not the fresh new drives.

 

[XavierMace]

I've got 3 systems right now actively booting and running off those stubby SanDisk drives, so I'd love to know what errors you were getting.

 

[VirtualLarry]

When I plugged into into my Windows box to run Rufus to put on the Linux ISO, I started getting weird keypresses in my programs and web browsers. Maybe it was an NSA bug?

 

[rchunter]

I have 2 of those tiny little sandisk drives running in my servers. They seem OK for the 2+ years i've had them.
The nsa isn't after me though...

 

[VirtualLarry]

This review is from:

ADATA 16GB UV128 USB 3.0 Flash Drive (AUV128-16G-RBE)

Pros: price

Cons: Could not get these to be recognized in windows 10

Other Thoughts: I purchased a 3 pack of these on Black Friday to have some spares, I opened them up this past weekend and could not get my windows 10 PC to see them, all three, even in disk management, or even thru command prompt (diskpart) and list. My macbook air can see them, my windows 7 PC can see them. I even took them to work and tired in another windows 10 pc and they could not be seen. For some reason they are not visible in windows 10. These are going back.

The Adata SSD's I have bought are very reliable and I've had no issue with them. I will never buy their USB flash drives again tho.

Apparently, I'm not the only one having issues with these drives and Win10.