Hardware & Technical Windows 10 & Saitek X52 pro
- Thread starter apolloz
- Start date
Mine works fine after an upgrade from Windows 7 (64bit). I had to reinstall the drivers and software before the profiles would work properly, but aside from that it's been fine. There's anecdotal evidence elsewhere on the forums that unplugging an X52 from a Windows 10 machine can cause all sorts of weird effects, but since I never disconnect mine (and see no point in tempting fate by doing so) I can't comment on that aspect.
Mine is working.
Using it right now, works like a charm. I actually have a bug but it has been since I switched USB port and started messing with some drivers.
So don't worry your X52 Pro will be fine with Win 10.
- - - Updated - - -
So don't worry your X52 Pro will be fine with Win 10.
- - - Updated - - -
Maybe that's what I currently experience: the clutch working only from time to time, and MFD sometime switching off, with LEDs all going back to green. And sometimes just working fine.
Hey kids, thought I'd chime in with a warning regarding X52.
My dad and I both have X52s. We have two different scenarios that are both caused by the driver as I've swapped our hardware to see the same results.
-My dad's computer does a thing where it blinks and it loses calibration quite often.
-My computer loses calibration occasionally without blinking.
Also, on both computers, if you unplug the joystick while the computer is on, you will lose control of your computer and it will blink obnoxiously.
So far, the ONLY solution has been this.
-Gut out the driver and the software
-Restart the computer
-Plug in the X52 into a different port and allow the computer to "reinstall" the driver you previously installed on its own.
-Goto control panel, and run test button dialog via searching for "set up game controllers" and looking at the Saitek x52 properties.
-Enjoy your game with the test button dialog in the background as all buttons will be enabled and the blinking problem is solved while the test dialog is running.
Saitek needs a new Win10 driver.
My dad and I both have X52s. We have two different scenarios that are both caused by the driver as I've swapped our hardware to see the same results.
-My dad's computer does a thing where it blinks and it loses calibration quite often.
-My computer loses calibration occasionally without blinking.
Also, on both computers, if you unplug the joystick while the computer is on, you will lose control of your computer and it will blink obnoxiously.
So far, the ONLY solution has been this.
-Gut out the driver and the software
-Restart the computer
-Plug in the X52 into a different port and allow the computer to "reinstall" the driver you previously installed on its own.
-Goto control panel, and run test button dialog via searching for "set up game controllers" and looking at the Saitek x52 properties.
-Enjoy your game with the test button dialog in the background as all buttons will be enabled and the blinking problem is solved while the test dialog is running.
Saitek needs a new Win10 driver.
Last edited:
Mine works like a charm
I noticed one further oddity with the X52 Pro yesterday. When I tried to use the Windows Game Controllers property sheet to adjust the brightness of the LEDs, moving the slider had no effect on the joystick and caused the control panel applet to freeze. Not even End Task could clear it; I had to force a reboot. The issue was solved by first toggling one of the LEDs to a different colour and back again, after which all of the controls including the brightness sliders worked flawlessly. Just another quirk of those slightly flaky Saitek/MadCatz drivers. YMMV.
Mode switch has gone back to the spam switch of BSOD
The MFD no longer displays the profile in use
Unplugging it causes BSOD
Plugging it in causes pc to slow down
All in all - it's a bit pants.
Still wrangling old drivers trying to get it to work at all. Certainly my custom setups that I've shared with everyone will NOT currently work.
The MFD no longer displays the profile in use
Unplugging it causes BSOD
Plugging it in causes pc to slow down
All in all - it's a bit pants.
Still wrangling old drivers trying to get it to work at all. Certainly my custom setups that I've shared with everyone will NOT currently work.
my x 52 works "IF" I avoid plugging it in until after boot up.
And then cross fingers I don't lose calibration
If I do, I need another reboot, because if you unplug- she screws up the ol' pc bigtime.
Sent a ticket into Saitek - everyone should, to get them off their butts and issue a new driver.
And then cross fingers I don't lose calibration
If I do, I need another reboot, because if you unplug- she screws up the ol' pc bigtime.
Sent a ticket into Saitek - everyone should, to get them off their butts and issue a new driver.
I just installed Win 10 and decided to give ED a go (had a 6 months break).
I had great difficulties using the official Saitek Drivers, as they were not signed.
In the end, I disabled driver signing, and used some older Saitek drivers, and now it works like a charm. On top of that, I can now have my X52 Pro connected at all times - before it caused my PC to hang at bootup.
The official drivers from Saitek's site installed alright, but when I tried making a macro, my PC became unresponsive, and I had to force a hard reboot.
Edit:
I used these drivers and software:
ftp://ftp.saitek.com/pub/software/full/Saitek_X52Pro_Flight_Controller_SD6_64.exe
ftp://ftp.saitek.com/pub/software/full/SST_Software_64_6_6_6_9.exe
I had great difficulties using the official Saitek Drivers, as they were not signed.
In the end, I disabled driver signing, and used some older Saitek drivers, and now it works like a charm. On top of that, I can now have my X52 Pro connected at all times - before it caused my PC to hang at bootup.
The official drivers from Saitek's site installed alright, but when I tried making a macro, my PC became unresponsive, and I had to force a hard reboot.
Edit:
I used these drivers and software:
ftp://ftp.saitek.com/pub/software/full/Saitek_X52Pro_Flight_Controller_SD6_64.exe
ftp://ftp.saitek.com/pub/software/full/SST_Software_64_6_6_6_9.exe
Last edited:
It's so odd. I'm seeing none of that, but have had other odd issues that others haven't seen. Having said that, I haven't been brave enough to disconnect the X52 since reading the other thread. It's possible I'd suffer the same disasters if I tried.
One thing I did do, many moons ago when I was having problems using the stick with on-board USB2 ports that shared a controller with the USB3 ports, was to install a third-party PCIe USB card (using a different chipset to the motherboard, just in case) and plug the X52 into that. So having the stick plugged into a port that's separated from the on-board chipset drivers might be helping to protect me from the worst of the problems people are seeing. But that's just speculation.
Saitek definitely seem to have a gift for writing drivers and support software that not only breaks under some circumstances, but often does so in a way that's unrecoverable and/or catastrophically bad for the current Windows session. I used to think Apple were the worst for that (iTunes handling of USB under Windows is atrocious) but Saitek has them beat hands down.
OT PS: I have to confess that for years I've been mentally reading your forum name as a single word ("ving-tet-un", like an Egyptian pharaoh or something). It was only when listening to the first of the most recent Lave Radio podcasts that I heard it read properly and the penny dropped. How embarrassing. I guess I just can't recognise gapless phrases that aren't in English. Amusingly, in the very next Lave Radio, Psykokow made the exact same mistake.
LOL. In many years of gaming online using that name, you aren't the first nor will you be the last. Vin or 21 are fine, as is David. Just not Vinge or Dave.
How do you disable the need for signed drivers?
In case this helps any X52 Pro users out there that are experiencing issues with the drivers that cause all sorts of issues with the MFD, flashing LED's, clutch settings, and random inputs. I discovered there is a severe conflict between Avast! antivirus and Saitek drivers that causes all sorts of glitches with the controller. This appears to be due to the Avast protection module which denies access to certain system folder which the X52 driver requires access to in both installation and normal use. The only way I was able cure this in Windows 10 was to uninstall Avast and the X52 drivers, manually delete all Saitek and Mad Catz folders and registry entries, then reinstall the X52 Drivers. It took me about a week to figure this out after upgrading to Windows 10, but now everything seems to be working normally. Hope this helps someone!
From command prompt (run as Administrator):
bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON (if this command fails, disable Secure Boot in your BIOS).
You will get a "watermark" in your lower right corner of Windows.
Go here for removing it: http://www.intowindows.com/how-to-remove-watermark-from-windows-10-desktop/
It's not a simple task, unless you're a little bit tech savvy, but it's doable.
Last edited: