Share via

All-in-one card reader driver

Anonymous
2017-10-28T11:06:16+00:00

I use regularly use a Qpix card reader (all-in-one) to store/read/write short-term project data on an SD card, attached by an usb2 port on my desktop PC.  The OS for that PC is Win 7 home sp1 fully patched.

Periodically, when inserting/removing cards in succession (eg, when checking the amount of used/spare space on several cards), the 1st connection will be detected Ok and the card folder appears in explorer, but after 1st removal, the 2nd card insertion just gets the detection tones but does not appear in explorer and is effectively 'unconnected'.  Substitutions of card reader (brand new one), usb cables and even insertion of the actual SD card in a laptop with an integral card reader haven't isolated the cause to a piece of hardware.  The software is however implicated:  I've found that the only way to fix this is to re-boot the PC, and a card insertion is then detected correctly and displayed in explorer again.  But the pattern is repetitive - when the card is removed using the windows process, inserting a 2nd one is detected but not displayed in explorer.

This seems to suggest that the device driver is OK on start/boot, but a card disconnection changes something and it will no longer work display any new card connected until the PC is re-booted.

Since the device is operated via the usb ports, I have no idea how to check which driver is used, what the version number is or even if there's a more recent ver4sion available.

Does anyone else have this sort of experience?

What is or may be the cause, and how can I reliably fix it?

Davidk

Windows for home | Previous Windows versions | 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
  1. Anonymous
    2017-11-21T23:32:34+00:00

    Sorry I've been tardy replying . .  have been travelling, then working on this . . .

    In the course of all this, found a workaround that did not involve  a PC re-start - simply open another program that uses input from system drive storage (eg, Excel), and after exit and re-attaching the card reader - bingo it's seen again in explorer.  Pretty conclusive evidence that there was something amiss in the system software - suspected drivers, so began a driver update cycle - one driver a time, then test the card reader.  This took some time.

    It seems the culprit was a combination of windows and a driver update to the USB 3.0 extensible host controller (thru which the card reader attached to the PC).  I mentioned that this used to work, and then lately, did not. 

    Confusing the situation were contradictory reports about the currency of the installed device driver - windows 7 said it was Ok, and a driver updater said it needed updating.  After checking with the Intel site, there were 2 drivers for different chipsets listed - one old and one new - the new one dated June 2017.  Then had to check with the motherboard manufacturer for the chipset that was installed on the board.  Finally, an answer to that - chipset type stated, use the latest version driver.  Download and install, then test - and it seems to work (chip in the reader displayed in explorer) on repeated detach/attachment cycles without opening any other software.

    Early days yet, but looking good so far . . . .

    6 people found this answer helpful.
    0 comments No comments

5 additional answers

Sort by: Most helpful
  1. Anonymous
    2017-10-30T03:54:04+00:00

    To isolate your concern, we suggest that you connect the Qpix card reader (all-in-one) to another computer. Perform same process and test the functionality of the card reader. In that case, we can identify if this is a hardware related issue. 

    Give us an update with the outcome.

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2017-10-29T03:48:48+00:00

    Hi David,

    This can be due to a recent change in the configuration of your device. To assist you with your concern, we recommend that you use Device Manager to disable and re-enable all the USB controllers. This lets the controllers recover the USB port from its unresponsive condition. The USB controllers represent the USB ports in Device Manager.

    To disable and re-enable the USB controllers, follow these steps:

    1. In the Search box, type Device Manager and press Enter.
    2. Expand Universal Serial Bus controllers.            

    Note You might have to scroll down the list to find this item. 3. Right-click the first USB controller under Universal Serial Bus controllers, and then click Uninstall to remove it. 4. Repeat step 3 for each USB controller that is listed under Universal Serial Bus controllers. 5. Restart the computer. After the computer starts, Windows will automatically scan for hardware changes and reinstall all the USB controllers that you uninstalled. 6. Check the USB device to see whether it is working.

    Let us know if the solution above works for you.

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2017-10-30T06:51:29+00:00

    Did that before posting the initial question.  Two readers, both Qpix, and one brand new (because past experience suggested the reader may have died, so I went and bought a new one) both reacted the same way.  Attaching to a desktop and a laptop, both exhibit the same behaviour.  The driver for the new Qpix device came from MS, but in device manager it shows as a realtek item (see the image previously posted) and is the current driver.

    0 comments No comments
  4. Anonymous
    2017-10-29T11:19:29+00:00

    With help from a tech friend I've established that the card reader is displayed in device manager when recognised (1st attachment after boot/re-start), and using that info used the rt-click menu to update the driver.  The response returned was that current one was the latest.  see this image

    However, the same pattern repeats:  after valid disconnection, a 2nd or subsequent attachment isn't recognised.  To get the CR recognised again, I have to re-boot the PC, and the next attachment after that works fine.

    I have however established that with a recognised attachment, closing and re-opening explorer without disconnecting the reader does not change the attached and recognised status of the device.  So it seems that the device removal action somewhere in the process) is the part that isn't working as it should.

    The reader driver is OK (latest), so - just how many are involved in recognising a card reader in explorer?

    0 comments No comments