Flash drive recognition delay

[srynznfyra]

Every time I plug my flash drive in to my windows 7 x64 PC there's a delay of about a minute before it gets recognized by the operating system (where it seems to be doing nothing - the light on the drive is just on not flashing). The drive's fine as it gets instantly recognized on Linux and OSX.

This always coincides with two errors in event viewer: both event ID 7011, and the same error:

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the <service> service.

Except one of the errors is with the ShellHWDetection service and the other is the LanmanServer service.

Any ideas why this is happening? It didn't happen before with my old flash drive. The new one's a Corsair 8GB voyager drive is that helps.

cheers

 

[Kirsch]

Quick simple question:

Have you tried using it in a different USB Port? Or on someone else's PC?

 

[srynznfyra]

Quick simple question:

Have you tried using it in a different USB Port? Or on someone else's PC?

thanks for your reply

I've tried using different USB ports, and (as I said although could have been more clear) have used it on different computers using different operating systems (although no other computers using windows 7).

edit: just tested on a windows 7 laptop and it loads instantly.

 

[Kirsch]

edit: just tested on a windows 7 laptop and it loads instantly.

That's what I was looking for


1. Click the Start button, type regedit, and hit Enter.
2. In the Registry Editor, click the registry subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.
3. In the details pane, locate the ServicesPipeTimeout entry, right-click that entry and then select Modify.

Note: If the ServicesPipeTimeout entry does not exist, you must create it by selecting New on the Edit menu, followed by the DWORD Value, then typing ServicesPipeTimeout, and clicking Enter.

4. Click Decimal, enter 1000, and then click OK
5. Restart the computer.

Try the flash drive again

 

[srynznfyra]

Great, thanks that did the job

Although it's strange, there must have been something causing that service do whatever it did that timed out :sarc:

problem solved anyway

 

[Kirsch]

Glad I could help!! Rep is appreciated

 

[Senderman49]

Really sorry but that did not work for me!

 

[JVN]

It worked for me at October 2012.
Thanks