Vista Fails to locate drivers on USB devices

[nino]

I have an odd problem where by when I insert a device for the first time be
it a memory stick, SD card or mouse vista decides that it doesn't want to
locate the driver. I have to manually tell it to look in c:/windows.....

I have bought a band spanking new Cruzer micro pen drive inserted into my
desktop(vista ultimate) and it has instantly popped up asking what i want to
do with the pen drive. I then inserted into my XPS Laptop(Vista Ultimate) and
vista complains that it cannot find the driver and its at this point i need
to manually need browse for the drivers. Once i do this for 1 device I never
need to do it again but if i put another brand of pen drivesd card in i need
to browse again. I hope ive explained that clearly lol

Thanks for any help!

Nino

 

[Samon]

Me too! Is there anyone can help me? When I plug in a usb device, vista just
cannot find the driver.
I'm so confused with that.

 

[Uwe Sieber]

I have an odd problem where by when I insert a device for the first time be
it a memory stick, SD card or mouse vista decides that it doesn't want to
locate the driver. I have to manually tell it to look in c:/windows.....

I have bought a band spanking new Cruzer micro pen drive inserted into my
desktop(vista ultimate) and it has instantly popped up asking what i want to
do with the pen drive. I then inserted into my XPS Laptop(Vista Ultimate) and
vista complains that it cannot find the driver and its at this point i need
to manually need browse for the drivers. Once i do this for 1 device I never
need to do it again but if i put another brand of pen drivesd card in i need
to browse again. I hope ive explained that clearly lol

http://www.uwe-sieber.de/usbtrouble_e.html#xp_asks_for_drivers

 

[nino]

I have found a solution to my problem at:

http://www.daemon-tools.cc/dtcc/dt-4-08-disables-vistas-t15831.html

turns out it was daemon tools at fault!

I did the following:
"
Navigate to C:\windows\inf (substitute a different drive letter for
whichever one your OS is installed on) and find the file infcache.1
You will need to have windows set to show hidden and system files most
likely. Since this is Vista, you also may need to go to the properties
and permissions for the file and take full control. Once that is done,
delete the file. Try reinstalling your device at that point and see if
it works.
"

 

[nino]

Found the issue was with daemon tools!

I did the following:

"Try this:
Navigate to C:\windows\inf (substitute a different drive letter for
whichever one your OS is installed on) and find the file infcache.1
You will need to have windows set to show hidden and system files most
likely. Since this is Vista, you also may need to go to the properties
and permissions for the file and take full control. Once that is done,
delete the file. Try reinstalling your device at that point and see if
it works."

 

[DevilsPGD]

In message <[email protected]> nino

I have found a solution to my problem at:

http://www.daemon-tools.cc/dtcc/dt-4-08-disables-vistas-t15831.html

turns out it was daemon tools at fault!

That is not correct, many of us see this issue without Daemontools being
installed.

I did the following:
"
Navigate to C:\windows\inf (substitute a different drive letter for
whichever one your OS is installed on) and find the file infcache.1
You will need to have windows set to show hidden and system files most
likely. Since this is Vista, you also may need to go to the properties
and permissions for the file and take full control. Once that is done,
delete the file. Try reinstalling your device at that point and see if
it works.
"

Indeed, this fix works in many cases.

 

[Wandering]

How could it possibly not be "correct" and how could you possibly know it
was not? He didn't claim any more than that he had solved his problem that
way, and showed what he did. It is certainly correct, though it may not
apply to you. Use what you can, and leave the rest. No need to judge
another's success here.

 

[DevilsPGD]

In message <[email protected]> "Wandering"

How could it possibly not be "correct" and how could you possibly know it
was not? He didn't claim any more than that he had solved his problem that
way, and showed what he did. It is certainly correct, though it may not
apply to you. Use what you can, and leave the rest. No need to judge
another's success here.

I can claim it's not correct because the symptoms described occur
without Daemontools being installed, and do not always occur with
Daemontools being installed, even on identical hardware configurations.

The fix is valid, the cause is misidentified.