Applied an Optional Hardware Windows Update on Dec 18th for genesys
Genesys USB Mass Storage Device. Went away on vacation after powering
off the computer, came back and couldn't read from the reader. Went
into Device Manager and it had an ! or ? next to Genesys USB Storage
Device. Tried doing a rollback but that didn't work. Multiple installs,
disables, enables, rediscoveries, etc failed. Continued to receive
error 19 or error 10's.

Did some searching on the Internet and found out that a mid Dec update
caused the issue. Checked Windows Update History and Dec 18th the
Genesys device driver was the last one installed. I needed to use
system restore to prior to it and it again works.

I don't remember the card reader manufacturer (might be a CompUSA
branded model) but on the bottom is listed:
9 In 1 Card Reader
Model No: CR-V10-U29G

Here's links to other postings about the exact same issue starting
after the update was listed on the Windows Update site mid December:
http://www.computing.net/hardware/ww...rum/40028.html
http://forums.hexus.net/showthread.php?t=63059

Without doing the update (which I've now hidden), Device Manager lists
USB Mass Storage Device vs the Genesys USB Mass Storage Device it lists
after the Windows Update.

It's either incorrectly identifying and replacing a device it shouldn't
or the lastest Windows Update for that device is not compatible with
all devices which used the previous driver.

For the future do not get Driver Updates from Windows Update.
Instead go directly to the hardware manufacturer.

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar
http://www.dts-l.org


<davidnj@gmail.com> wrote in message
news:1136170102.223598.94260@o13g2000cwo.googlegro ups.com...
> Applied an Optional Hardware Windows Update on Dec 18th for genesys
> Genesys USB Mass Storage Device. Went away on vacation after powering
> off the computer, came back and couldn't read from the reader. Went
> into Device Manager and it had an ! or ? next to Genesys USB Storage
> Device. Tried doing a rollback but that didn't work. Multiple installs,
> disables, enables, rediscoveries, etc failed. Continued to receive
> error 19 or error 10's.
>
> Did some searching on the Internet and found out that a mid Dec update
> caused the issue. Checked Windows Update History and Dec 18th the
> Genesys device driver was the last one installed. I needed to use
> system restore to prior to it and it again works.
>
> I don't remember the card reader manufacturer (might be a CompUSA
> branded model) but on the bottom is listed:
> 9 In 1 Card Reader
> Model No: CR-V10-U29G
>
> Here's links to other postings about the exact same issue starting
> after the update was listed on the Windows Update site mid December:
> http://www.computing.net/hardware/ww...rum/40028.html
> http://forums.hexus.net/showthread.php?t=63059
>
> Without doing the update (which I've now hidden), Device Manager lists
> USB Mass Storage Device vs the Genesys USB Mass Storage Device it lists
> after the Windows Update.
>
> It's either incorrectly identifying and replacing a device it shouldn't
> or the lastest Windows Update for that device is not compatible with
> all devices which used the previous driver.

Yes, normally the case and what I do. But if MS is offering them up
there, they should work properly which is the reason for my posting
here.

I imagine there's lots of folks that could do Windows Update, see a new
driver and install it and "break" their device. First time I've "ever"
had a problem over all the years and I handle a slew of computers.

The drivers on windows Update come from the hardware manufacturers.
But only after extra testing paid for by the hardware manufacturer to
demonstrating they also meet Microsoft standards.
Because of this extra testing, newer drivers are often available directly
from the manufacturer.
As a minimum check with the manufacturer before installing drivers.

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar
http://www.dts-l.org


<davidnj@gmail.com> wrote in message
news:1136200720.736516.103290@g43g2000cwa.googlegr oups.com...
> Yes, normally the case and what I do. But if MS is offering them up
> there, they should work properly which is the reason for my posting
> here.
>
> I imagine there's lots of folks that could do Windows Update, see a new
> driver and install it and "break" their device. First time I've "ever"
> had a problem over all the years and I handle a slew of computers.