• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Drivers not working

K

kokokoko

Junior Member
Hi, I recently purchased a wheel and pedals and installed a .exe file which claimed to install the drivers however the wheel and pedals still come up as unknown. I then decided to extract the .exe file and retrieve the .inf files and manually set them up with the device however after extracting the .exe file I only got .dll and .exe and CAB and HDR files. Please help, it will be a shame if my wheel doesn't work.

Thank You
 
I made progress, sometimes the device is unknown, sometimes it is called an xbox controller, sometimes it is called a broken human interface and in the very rare occasion it works for 10 seconds. It is a euro quantum wheel and pedal set and the driver which I am currently hating is an LS-USBMX1/2/3
 
I am running windows 8.1 and I got the drivers from a disc. When I tell windows to check for updates it always says it is up to date. Very rarely when I plug in the device it says it is an xbox controller. This is really strange because I managed to get it working fully correctly once but it broke after 10 seconds and I have had no hope since.
 
OK, either my googling took me to an older/wrong product, or the company only "thought" their drivers would work in 8.1. If you pull up the unknown device in device manager, does it see anything in the files you extracted?
 
If it worked briefly and stopped working, then it sounds like a hardware issue. Open the property sheet for the unknown device in Device Manager, go to the Details tab, and look at the hardware IDs.

Windows matches those hardware IDs to the IDs found in INF files. If the device was successfully detected as a controller at some point, that means that Windows was able to identify that hardware ID and match it to something. And if it later then became unknown, then, most often what has happened is that the device is malfunctioning and is either no longer sending a hardware ID or sending a mangled hardware ID. (And yes, I've seen this happen before with dead/dying hardware.) In which case, there's nothing you can really do, since this would be a problem on the hardware side of the fence and is not a driver or OS issue.
 
Last edited:
You must log in or register to reply here.

TRENDING THREADS

Back
Top