Installed SW-221 now USB port shows Unknown Device - can't update driver
I installed the Linxcel USB 2.0 Sharing Switch, now my printer is not recognized by the computer. Device Manager shows the USB port as Unknown Device and no driver loaded. I attempt to load the printer driver but get a message that it can't be updated. I have uninstalled the the USB switch software and plugged the printer in direct, but am having the same problem.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
I had the same issues here and switched the USB cables to newer ones and the switch showed up and downloaded the drivers immidiately. It ended up being a incompatibility not with the KVM switch itself but the USB 2.0 cables that were used. Try it on one port and see if that helps?
no its not, sometimes that device or the port connection are not installed yet properly. To check it on the device manager, see to it that the connection on your Belkin Switch are functioning. Or try another port or USB connection, it might work there.
Your problem has nothing to do with the Operating System (Vista), it has something to do with the brand of your computer. I have similar problem before, I have Vista (Dell), but the time I connected another Vista (Sony Vaio), everything worked correctly.
This is what you need to do:
1. You have to make sure that you are using a standard USB keyboard and mouse.
2. Connect first the keyboard and mouse directly to the Vista computer to see if the USB ports of your computer are working properly.
3. You may power cycle the KVM switch by disconnecting it from the computers (including the keyboard and mouse) and leave it disconnected for 2 minutes.
4. Reconnect everything after two minutes and then reboot the computers.
5. Try using different USB keyboard if problem exist after power cycling the KVM switch.
It looks very straight forward. You need to install the driver software on each of the computers then run a USB cable from each computer to the USB switch. Connect these cables to the end of the USB switch that has the four sockets. Next run a USB cable from the end of the USB switch with one socket to the device you wish to control.
When you want to use the USB device from a computer you can select it by right clicking on the USB status icon in the task bar and selecting "Switch" or you can use the hotkey Ctrl+F11 for Windows or Alt+F11 for Mac.
If you find this solution useful I hope you'll rate it...unfortunately most people don't seem to find the time. People like myself are not getting paid for these solutions we're just trying to help.
I have had the same problem off and on since I bought my Iogear 2-port kvm switch over a year ago. I have a DYNEX wired, multimedia, usb keyboard and a Dynex wired usb mouse. The operating system on my desktop is Windows XP, SP3 and on my laptop it's Windows XP professional.
Yesterday, my keyboard "died" on me about 8 times and each time it requires unplugging the keyboard usb cable from the switch and my laptop, rebooting, then plugging the usbs back in. Really, really frustrating and annoying. I'm not a techno guru, but I got to thinking that maybe the keyboard driver might be the culprit. I decided to go to Control Panel, clicked on Keyboard, then Hardware/Properties/Driver/Update Driver. I clicked on "update driver" and let it find one automatically. It took what seemed like a long time for it to find the driver but it found one. The device name changed to KeyMaestro P2360, the driver updated, and I noticed 2 additional files were added to the System 32 directory.
It's only been a day but so far so good. My keyboard hasn't failed yet since the keyboard driver update. I don't know if this is the solution for you or not, but it seems to be the one for me. I'll know for sure if I can through a few days without it failing again.