A Problem With X52 Pro Drivers …. Solved
-
For some reason, unexpected to me, my X52 Pro stopped interacting with it’s software/drivers. I plugged it in and it functioned in BMS, but nothing lit up, no MFD, no profile editor, etc. It was running as if it were a generic device in Windows.
I tried reinstalling drivers (of which I have SEVERAL versions), but the re-install never properly completed and created all sorts for shutdown and startup problems. I scoured the internet and found post after post and thread after thread about difficulty with Saitek drivers in Win7 and Win10 in particular. I did all the ‘totally remove all traces of Saitek drivers’ dance …. MULTIPLE times. All to no avail. Windows would ‘see’ the X52 Pro; you could get to the game controller. But no settings would work … can’t set LEDs, MFD, dead zones, etc.
I tried all the ridiculously STUPID hoop-jumping solutions that Saitek has on it’s Support/FAQ site. Does. Not. Work.
Than I ran across a post that included a clue. It had to do with USB 2 vs USB 3. The X52 Pro won’t work on USB 3. I knew this. Had not had an issue previously, but herein lies the clue … one fix was to ‘disable USB 3 support in the motherboard BIOS.’ There were other suggestions, but all related to somehow altering or working around USB 3. This is the thread: https://www.flightsim.com/vbfs/showthread.php?305576-X52-Pro-Driver
This is what I think (i.e. speculation on my part) is happening: With Windows 10, Intel/Motherboard manufacturers are updating how USB 3 is applied/implemented at the system level. These changes create an incompatibility with (?some … ?all) Siatek X52 Pro drivers, at least on some systems.
This mattered to me because I had recently updated by Motherboard BIOS. I rolled back to a slightly earlier BIOS version and, voila, X52 Pro works just like it always did.
Happy it’s working …. , but not so happy that Saitek doesn’t seem to have the first F’king clue about how to fix their own drivers … :mad: … :dhorse:
Here’s a decent video on how to completely remove all trace of Saitek drivers and software if you need to start completely fresh (BTW, I think the tips that you’ll find here and all over the web about disconnecting from the internet are a red herring):
Those steps DO work to completely remove old drivers, but they don’t fix the problem described. Also, while I’m not sure, I suspect this would also apply to the non-pro X52.
My system specs:
i5 4590 OC’d @3.7 GHz / MSI Z87-GD65 / MSI GTX970 OC’d / 32GB HyperX RAM / Rosewill Hive 650W / 2X SSD (360GB) / 2x 1TB WD Blue HD / CoolerMaster N600 Case / 32" ASUS 2560x1440 Monitor / 64-bit Win7 Pro
Using TM Warthog Stick; X52 Pro Throttle; Track IR 5 w/pro clip; MFDE
-
I have an x 52 and after updating win 10 , it said my drivers werent installed
In my device mgr. I tried couple different things
Selected the generic device and its working great.
Dont know why , dont care at the moment.
It works even though i havent been flying lately but did check and it worked in sim.
This is madcatz install thogh too. -
For some reason, unexpected to me, my X52 Pro stopped interacting with it’s software/drivers. I plugged it in and it functioned in BMS, but nothing lit up, no MFD, no profile editor, etc. It was running as if it were a generic device in Windows.
I tried reinstalling drivers (of which I have SEVERAL versions), but the re-install never properly completed and created all sorts for shutdown and startup problems. I scoured the internet and found post after post and thread after thread about difficulty with Saitek drivers in Win7 and Win10 in particular. I did all the ‘totally remove all traces of Saitek drivers’ dance …. MULTIPLE times. All to no avail. Windows would ‘see’ the X52 Pro; you could get to the game controller. But no settings would work … can’t set LEDs, MFD, dead zones, etc.
I tried all the ridiculously STUPID hoop-jumping solutions that Saitek has on it’s Support/FAQ site. Does. Not. Work.
Than I ran across a post that included a clue. It had to do with USB 2 vs USB 3. The X52 Pro won’t work on USB 3. I knew this. Had not had an issue previously, but herein lies the clue … one fix was to ‘disable USB 3 support in the motherboard BIOS.’ There were other suggestions, but all related to somehow altering or working around USB 3. This is the thread: https://www.flightsim.com/vbfs/showthread.php?305576-X52-Pro-Driver
This is what I think (i.e. speculation on my part) is happening: With Windows 10, Intel/Motherboard manufacturers are updating how USB 3 is applied/implemented at the system level. These changes create an incompatibility with (?some … ?all) Siatek X52 Pro drivers, at least on some systems.
This mattered to me because I had recently updated by Motherboard BIOS. I rolled back to a slightly earlier BIOS version and, voila, X52 Pro works just like it always did.
Happy it’s working …. , but not so happy that Saitek doesn’t seem to have the first F’king clue about how to fix their own drivers … :mad: … :dhorse:
Here’s a decent video on how to completely remove all trace of Saitek drivers and software if you need to start completely fresh (BTW, I think the tips that you’ll find here and all over the web about disconnecting from the internet are a red herring):
Those steps DO work to completely remove old drivers, but they don’t fix the problem described. Also, while I’m not sure, I suspect this would also apply to the non-pro X52.
My system specs:
i5 4590 OC’d @3.7 GHz / MSI Z87-GD65 / MSI GTX970 OC’d / 32GB HyperX RAM / Rosewill Hive 650W / 2X SSD (360GB) / 2x 1TB WD Blue HD / CoolerMaster N600 Case / 32" ASUS 2560x1440 Monitor / 64-bit Win7 Pro
Using TM Warthog Stick; X52 Pro Throttle; Track IR 5 w/pro clip; MFDE
Hello, Agave_Blue
Uninstall the USB 3.0 driver, to see what happens and plug the cable into the USB 2.0 port, see if it will work. -
Hello, Agave_Blue
Uninstall the USB 3.0 driver, to see what happens and plug the cable into the USB 2.0 port, see if it will work.Yes. Good thought. I think that would work too. I’m happy as it is now. But there is something (at least on some systems/applications) where newer USB 3.0 implementations interfere with the X52/X52 Pro drivers.
Hopefully this thread will help put someone with that kind of problem on the right track for resolution.
-
Yes. Good thought. I think that would work too. I’m happy as it is now. But there is something (at least on some systems/applications) where newer USB 3.0 implementations interfere with the X52/X52 Pro drivers.
Hopefully this thread will help put someone with that kind of problem on the right track for resolution.
Hi,
After Saitek was sold, hardware trouble began. -
Hi,
After Saitek was sold, hardware trouble began.Sold to madcatz…yes. Logitech is not madcatz.
-