I've recently picked up a couple PS/2 to USB adapter for use with Win 7. I've used two different machines (different hardware) and two different PS/2 devices (a keyboard and mouse) with the same results. Every time the PC boots up it detects the USB adapter and fails to load the driver. It shows up in Device Manager as 'Unknown Device'. If I unplug the adapter and plug it back in, the OS then loads the appropriate HID drivers and everything works fine.
This page contains information about installing the latest Hama USB-PS/2-Converter driver downloads using the Hama Driver Update Tool.
Why do I have to disconnect and reconnect the adapter for Windows to load the correct drivers? Is there a fix for this?
Another oddity: Every time it correctly detects the adapter (after the disconnect/reconnect) it reaches out to Windows Update for the drivers. Shouldn't it just use the drivers on the system? Any explanation here? Thanks for any info. Hi Tony, Thank you for posting your query to Microsoft Community.
I can understand the frustration when things don’t work the usual way. What is the make and model of your computer? Mouse, touchpad, and keyboard problems can have a number of causes:.Incorrect device settings.Missing updates.Corrupted or incompatible drivers.Hardware problems Please make sure that you install all windows updates How can I tell if my computer is up to date?
I would suggest you to follow few troubleshooting steps and check if that fixes the issue on your computer. Method 1: Open the Hardware and Devices troubleshooter Method 2: Step 1: Uninstall the driver from device manager and reinstall it and check if it helps. Follow the steps to uninstall the driver from device manager: a. Click Start, type Device Manager in the Start Search box, and then press ENTER. Click Continue. The Device Manager dialog box is displayed.
Note: If you are prompted for an administrator password or for a confirmation, type the password, or click Continue. In the list of device types, click the kind of device, and then locate the specific device that is not functioning. Right-click the device and then click Properties. Click the Driver tab. Click Uninstall. Step 2: Download the driver from the manufacturer website Step 3: Follow the steps to install the driver: In the Device Manager dialog box, click the Action menu, and then click Scan for hardware changes. You may receive a message that states that Windows has to install driver software for your unknown device.
If you receive this message, click Locate and install driver software (recommended). You may also receive a message that states that a hardware device is being installed and that the uninstalled device is now present in Device Manager. Hope this resolves the issue. If issue persists, you can write to us and we will be glad to assist you further.
I'm not going include the make/model of the PC as they are both custom built machines. The fact that OS behaves the same way on both machines (made up of different hardware) tells me it is not a machine/hardware issue. You said ' Mouse, touchpad, and keyboard problems can have a number of causes:' This is not a problem with the peripheral I/O devices. The issue here lies on how Windows is detecting the USB adapter.
I can have nothing plugged into the USB adapter and get the same results described in my first post. Please re-read the initial post. Both machines are completely up-to-date. Method 1: No go here.
Method 2: Didn't work either. Also, there are no manufacture drivers for the adapter. Like I said, The Microsoft HID drivers work fine.
The issue is with Windows detecting the device. If the problem isn't clear let me know and I can break it down further. My guess is that with the device plugged during boot, the BIOS on the system tries to interact and put the device in a weird state. So when the USB stack tries to enumerate, the device doesn't respond. Later when you unplug and plug the device, it sets the device back in the right mind set. If you want to find out more, collect USB trace by following the instruction on this page: Since this issue is happening on boot, jump to the last boot tracing section and follow the instruction.
Boot tracing (special tracing commands) Are you seeing this issue with only Win10? Have you run other versions of Windows on this system? -Eliyas This posting is provided 'AS IS' with no warranties, and confers no rights.