XP USB Flash drive trying to configure as "New Hardware found"
I plugged a USB Flash drive into my Dell Windows XP Pro and it came up with
a message that new hardware was discovered and prompted for a configuration
disc in the config wizard, which, of course, there is none. Does anyone know
what would cause this and how to fix it?
Re: XP USB Flash drive trying to configure as "New Hardware found"
"Bill Fuller" <someone@nospam.com> wrote:
^^^^^^^^^^
If you don't have a mail address with "SolutionPro, Inc." stop abusing a
registered domain name! Shall others get all the spam on behalf of you?
> I plugged a USB Flash drive into my Dell Windows XP Pro and it came up
> with a message that new hardware was discovered and prompted for a
> configuration disc in the config wizard, which, of course, there is
> none.
Click "Install the software automatically (Recommended)", and then click
"Next". Do this twice in order to install the default drivers.
Re: XP USB Flash drive trying to configure as "New Hardware found"
Thank you for your help.
"Detlev Dreyer" <detdreyer@flashmail.com> wrote in message
news:495d7ba969283d66cfe643b68fcc34b0@d-d.mvps.org...
> "Bill Fuller" <someone@nospam.com> wrote:
> ^^^^^^^^^^
> If you don't have a mail address with "SolutionPro, Inc." stop abusing a
> registered domain name! Shall others get all the spam on behalf of you?
>
>> I plugged a USB Flash drive into my Dell Windows XP Pro and it came up
>> with a message that new hardware was discovered and prompted for a
>> configuration disc in the config wizard, which, of course, there is
>> none.
>
> Click "Install the software automatically (Recommended)", and then click
> "Next". Do this twice in order to install the default drivers.
>
> --
> d-d
Re: XP USB Flash drive trying to configure as "New Hardware found"
Ok, I finally found the problem. For some strange reason, the usbstor.*
files were missing from c:\windows\inf. I have NO idea how they got deleted.
Google search noted that the problem I had was being experienced by
others... however, there was never a solution offered for this or a
potential cause.
If this happens to you, try looking in windows\inf.