usb card reader problems

[imjeffreyw]

I have a NUC11PAHi7 that has an issue with card readers attached via usb.  If I plug in a reader with a camera SD card inserted it will function as expected until I remove the card from the reader, then the explorer window stays as if the card was still in. If I insert a second card nothing happens - it still shows the images from the initial card.  With the second card in the reader, unplugging the usb from the NUC and then plugging it back in closes the explorer window and reopens a new window with the contents of the second displayed.  So instead of just pulling the first SD card and then inserting a new card to view its content I have to also unplug/replug the reader for each SD card.  The built-in card reader work as expected, it is a problem with usb card readers.  BIOS is up to date, no problems show in Device manager.

[LeonWaksman]

Instead of disconnecting the SD card reader, right click on this drive in the Windows Explorer and then click ob "Eject". When you see the message that the card can be safely removed, only now replace the SD Card.

Leon

[imjeffreyw]

Leon, thanks for the reply,

I tried another usb reader and my problem went away!  Go figure...

jeffreyw

[Rew452]

Have you updated your USB firmware?

See  https://www.intel.com/content/www/us/en/products/sku/202783/intel-nuc-11-enthusiast-kit-nuc11phki7c/downloads.html

[imjeffreyw]

Thanks for the reply

I assumed that, because the reader worked well before this problem cropped up, that perhaps an upgrade broke it.  Turns out that the reader itself broke although I am at a loss as to how.  Two other readers work fine although the newest, a type c usb reader, wasn't working very well before. It, and another old usb 1.0 Kingston reader, are working perfectly now.  I will note that the Intel upgrade assistant installed a firmware upgrade while I was troubleshooting.  The reader that prompted my initial query (a Ugreen 4 in 1) is still broken.  I didn't find any driver downloads for the ugreen but I may look again.  It was using a generic MS mass storage device driver.

jeffreyw