XP Pro and USB devices suddenly not recognized

[teresauark]

I manage a number of XP Pro machines. Suddenly, starting yesterday and
today, we have a problem with "new" USB devices being ignored upon
connection; USB devices which are currently connected (such as printers and
keyboards) still work, unless they are unplugged and reconnected. Affected
items are USB jumpdrives, memory cards (SD, CF, etc.) and anything else USB
that is freshly attached to the computer, whether or not it was been
connected before. Rebooting makes no difference. I have run SFC with no
errors being detected. Any suggestions are greatly appreciated; we are
administering final exams and the inability to use jumpdrives is causing
havoc. Many thanks!
Teresa
--
T

 

[M.I.5¾]

"teresauark" <teresauark@discussions.microsoft.com> wrote in message
news:6500A635-6D62-472F-BEAB-5B31B186796B@microsoft.com...
>I manage a number of XP Pro machines. Suddenly, starting yesterday and
> today, we have a problem with "new" USB devices being ignored upon
> connection; USB devices which are currently connected (such as printers
> and
> keyboards) still work, unless they are unplugged and reconnected.
> Affected
> items are USB jumpdrives, memory cards (SD, CF, etc.) and anything else
> USB
> that is freshly attached to the computer, whether or not it was been
> connected before. Rebooting makes no difference. I have run SFC with no
> errors being detected. Any suggestions are greatly appreciated; we are
> administering final exams and the inability to use jumpdrives is causing
> havoc. Many thanks!
> Teresa

See my reply to Sheisty (about two threads away). This is a common problem.

 

[teresauark]

ANy chance you can specify what post "Sheisty" was, or just go ahead and copy
the reply to me? It may be about two threads away but I'm sorry, I'm not
finding it anywhere in the list...
--
T


"M.I.5¾" wrote:

>
> "teresauark" <teresauark@discussions.microsoft.com> wrote in message
> news:6500A635-6D62-472F-BEAB-5B31B186796B@microsoft.com...
> >I manage a number of XP Pro machines. Suddenly, starting yesterday and
> > today, we have a problem with "new" USB devices being ignored upon
> > connection; USB devices which are currently connected (such as printers
> > and
> > keyboards) still work, unless they are unplugged and reconnected.
> > Affected
> > items are USB jumpdrives, memory cards (SD, CF, etc.) and anything else
> > USB
> > that is freshly attached to the computer, whether or not it was been
> > connected before. Rebooting makes no difference. I have run SFC with no
> > errors being detected. Any suggestions are greatly appreciated; we are
> > administering final exams and the inability to use jumpdrives is causing
> > havoc. Many thanks!
> > Teresa
>
> See my reply to Sheisty (about two threads away). This is a common problem.
>
>
>

 

[M.I.5¾]

"teresauark" <teresauark@discussions.microsoft.com> wrote in message
news:45FBF352-421D-4ACF-AB8F-F8753A14ACD0@microsoft.com...
> ANy chance you can specify what post "Sheisty" was, or just go ahead and
> copy
> the reply to me? It may be about two threads away but I'm sorry, I'm not
> finding it anywhere in the list...
>

My mistake. It was Alan I replied to (right next to Sheisty in my reader).

FYI, I wrote:

"This is a known XP issue that crops up from time to time. The only
solution that I know of is to do a system restore to a time when you know
this worked."

 

[teresauark]

Thanks, M.I.53/4 -- unfortunately a system restore is not an option for me on
these machines at this time, but is good to know it's not "just me". Thanks,
T
--
T


"M.I.5¾" wrote:

>
> "teresauark" <teresauark@discussions.microsoft.com> wrote in message
> news:45FBF352-421D-4ACF-AB8F-F8753A14ACD0@microsoft.com...
> > ANy chance you can specify what post "Sheisty" was, or just go ahead and
> > copy
> > the reply to me? It may be about two threads away but I'm sorry, I'm not
> > finding it anywhere in the list...
> >
>
> My mistake. It was Alan I replied to (right next to Sheisty in my reader).
>
> FYI, I wrote:
>
> "This is a known XP issue that crops up from time to time. The only
> solution that I know of is to do a system restore to a time when you know
> this worked."
>
>
>