Your done! you now have a fully functional X52 PRO running the latest SST software.So I received my X52 (non pro) HOTAS last wednesday. select 'saitek magic hotkey' device ase the new driver choos the driver named 'saitek magic bus' note: you might need to uncheck 'show compatible hardware' before the saitek driver shows up.Ħd.perform the same operation for the 'programmable hotkeys' device.
next select 'let me pick from a list of device drivers on my computer'Ħc.
on the first update driver screen choose 'browse my computer for drivers'Ħb. go to the device manager and update the driver for the programmable root enumerator device.Ħa.
the easist and quickest way to find out is if the little thumb stick on the throttle is able to move your mouse cursor.ĥ.download and install the latest version of the SST software.Ħ. install the older version of the SST software.Ĥ.confirm software driver function. download the proper version of the older SST software from the post above.ģ. Uninstall any SST software you have installed.Ģ. Ok believe it or not, using the newer sst software with the older software drivers is actually possible.ġ.
I'm leaning toward testing mode being enabled as that mode is meant for testing out new drivers under development. the person i talked to said they are not seeing this issue on their test systems, which means that their test systems either have windows test mode enabled, or windows driver signing disabled. as to whether they will actually fix the problem or not remains to be seen. The guy I talked to said he would create a incidient report and forward it to the software development department.
after all was said and done, they had me take a screen shot of the device manager, showing the problem, and take a system info report using the system information program (included with windows). I just got off the phone with madcatz (saitek) after being disconnected once (45 minutes first session, 84 minutes second session) after working the steps I already knew that wouldnt work, they had me uninstall and reinstall the device drivers and the SST software, my logitech mouse software (LGS 8.5) and disconnect my xbox360 wired controller. MadCatz says the drivers are signed, by MadCatz, not M$. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
If anybody knows of a solution to this that doesn't involve reducing windows security features, please let me know.Įrror message: Windows cannot verify the digital signature for the drivers required for this device. I will try calling back MadCatz tommorrow, but I may have to try and find an older version of the SST software. has anybody been able to get past this issue WITHOUT reducing the securit of windows by putting it into test mode or turning off driver signing? I'm not even sure you could turn off driver signing in windows 10. I can load up a profile, but when i click test profile, the only activity that is registered, is my mouse clicks (not the joysticks mouse) and my key presses. but the thing is, the SST software and the joystick software are not communicating properly. i tried calling MadCatz (who now own Saitek) and they said that the issue is because the driver isn't signed by M$, and it will not cause a problem. I have an X-52 Pro, and the SST software drivers are having a code 52 issue in the device manager.