X52 Pro SST issues UPDATE: fix for SST software driver found

[Chris Solomon]

I have an X-52 Pro, and the SST software drivers are having a code 52 issue in the device manager. 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. but the thing is, the SST software and the joystick software are not communicating properly. 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. 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 will try calling back MadCatz tommorrow, but I may have to try and find an older version of the SST software. If anybody knows of a solution to this that doesn't involve reducing windows security features, please let me know.

error message: Windows cannot verify the digital signature for the drivers required for this device. 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. (Code 52)

MadCatz says the drivers are signed, by MadCatz, not M$.

[Rogen]

I have the same issue. Win7 x64 (which requires fully signed drivers)

The file is SaiBus.sys version 7.0.39.0 and it says it's not digitally signed which sure sounds like it is the problem file to me.

As this is a file supplied by Saitek the issue is firmly in hte hands of the Saitek developers to resolve. i.e. to ensure the driver file is correctly signed.

[Chris Solomon]

I to call mad catz (saitek) tommorrow about this issue. If they trt to give me any guff, I will start working my way up th foof chain by asking for his supervisor, if i need to i will ask for his suervisor as well. the excuse they tried to pawn off on me the first time i called is a load of sh!t

you basically found out all the information on your system that i found on mine. (although i'm now running win10)

if they can get the device drivers signed then there is no reason they could not get the sst driver signed.

[GegeTS]

And plus about X52 pro if you plug it into a USB3 connector, the screen panel on the throttle lever don't display anything. The X52 must be plugged into a USB2 connector to be able to show informations on the throttle lever display. I believed the USB3 was back compatible with USB2. However I have no problem with my Logitech G25 wheel plugged in a USB3 connector althought Logitech preconise to plug it on a USB2 but is well functionning plugged into a USB3 here. A bit out of this thread subject but it seems also driver related I guess. ( W7 64 Pro and latest Saitek drivers). I'm thinking Madcatz won't pay money to microsoft to obtain a signed driver...

[Chris Solomon]

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. 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). The guy I talked to said he would create a incidient report and forward it to the software development department. So i guess the balls now in thier court. as to whether they will actually fix the problem or not remains to be seen. 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. I'm leaning toward testing mode being enabled as that mode is meant for testing out new drivers under development.

[GegeTS]

Ok here under W10 and X52 Pro plugged in a USB3 powered HUB all is functionning apart only something showing in task manager with a warning yellow sign "Programable root enumerator" with the same code 52 like the driver is not MS signed or approved...However the X52 is well recognized in peripherals and printers and functionning with FSX

[Chris Solomon]

by 'USB3' I assume you mean USB 3.0? also, try testing out a profile. you will find that because windows has disabled that device driver, that no profiles will not function. You can load them onto the joystick, but they do nothing. you will only have basic joystick functionallity, with no programability. since i started this thread i have moved from Windows 7 Ultimate SP1 x64 to Windows 10 Pro

[GegeTS]

Chris Solomon původně napsal:

by 'USB3' I assume you mean USB 3.0? also, try testing out a profile. you will find that because windows has disabled that device driver, that no profiles will not function. You can load them onto the joystick, but they do nothing. you will only have basic joystick functionallity, with no programability. since i started this thread i have moved from Windows 7 Ultimate SP1 x64 to Windows 10 Pro

Yes Chris I mean USB 3.0...And after testing you are right any profiles aren't working even if loaded with the SST software in FSX that's do nothing. Very annoying. As you said only basic functionnality.

[Chris Solomon]

Ok, I found saitek's software archive. the only problem is, determining which file is the right one. Obviousl it needs to have either the X-52 Pro or SST in it's name, but there are many files to choose from. I can confirm the software driver files signed by saitek work, but not any of the ones signed by those idiots at madcatz. link will be posted at end of post, anybody who wants to help out, I'm looking for a version of the SST that has as close to the same level of functionality as the latest version from the idiots over at madcatz. the person who finds the right file gets a cookie.

ftp:/ftp.saitek.com/pub/software

[Chris Solomon]

ok, found a sst version that does not throw off any errors when setup is run. software drivers work too. the software is extremely basic, but it does work. I will experiment to see if I can get the software drivers to work with the newer SST software.

64-bit: ftp:/ftp.saitek.com/pub/software/xpvista/SST_SD6_16_64_Software.exe
32-bit: ftp:/ftp.saitek.com/pub/software/xpvista/SST_SD6_16_32_Software.exe

this sst version was tested on a Windows 10 Pro machine, so it should work on 7, 8/8.1, and 10

[Chris Solomon]

Ok believe it or not, using the newer sst software with the older software drivers is actually possible.

here is the fix:

1. Uninstall any SST software you have installed.
2. download the proper version of the older SST software from the post above.
3. install the older version of the SST software.
4.confirm software driver function. the easist and quickest way to find out is if the little thumb stick on the throttle is able to move your mouse cursor.
5.download and install the latest version of the SST software.
6. go to the device manager and update the driver for the programmable root enumerator device.
6a. on the first update driver screen choose 'browse my computer for drivers'
6b. next select 'let me pick from a list of device drivers on my computer'
6c. choos the driver named 'saitek magic bus' note: you might need to uncheck 'show compatible hardware' before the saitek driver shows up.
6d..perform the same operation for the 'programmable hotkeys' device. select 'saitek magic hotkey' device ase the new driver

your done! you now have a fully functional X52 PRO running the latest SST software.

[GegeTS]

Thank you Dear Chris to have found the solution. I will try as soon as possible and give feedback if it is well running here. At least for the programmable root enumerator things...

[Chris Solomon]

no problem.... guess i get the cookie.... it was just as big a problem for me as anyone else

my first hint that the whole thing was working was i was able to now move the mouse cursor around using the mouse control thats on the throttle. I'm a little surprised that the combination of the older saitek signed drivers and the newer madcatz sst software actually worked as well as it did. I wholly expected those idiots at madcatz to have done some kind of code changes that would not have allowed the older drivers to work...... maybe i gave them too much credit tho.

[Rogen]

Hi Chris,

Great job at finding driver files that actually function.

Just a short update on installing them.

The driver files can be extracted from the exe itself with a utility such as 7zip and then installing the driver files just as you say.

Takes away the need to install/uninstall the actual application.

The files themselves are located at the root of the exe when it is opened in 7Zip.

e.g. You'll see...
saibus.cat
saibus.inf
saibus.sys
saimini.sys

Just drag them out into a suitable location and then point the driver update (#6 onwards) to the location with the have disk option.

Cheers :-)

Tony M

[Chris Solomon]

you got the root enumerator and the hotkey device installed with out installing the sst? how? windows no longer allows driver install through the .inf and the drivers are not tied to an actual device. If you install the current SST and then do a custom install of the driver, the drivers will not show up automaticly, because the have not been registered by windows. getting them registered and installed by windows is possible using the update driver feature, but it is a little more complicated than what an average user might be able or willing to go through.

also when the setup for sst is run, even is it is canceled without installing the sst software, those files you mentioned reside with the setup files in c:\windows\temp\saitek

the same is true for the current version of the SST only it resides in c:\windows\temp\MadCatz

[Rogen]

Nothing special...

Just chose the driver with the problem in device manager.

Followed by

Update Driver Software/
Browse my computer for driver software/
Let me pick from a list of device drivers on my computer/
Chose the item in the list as per your instuctions/ (6c)
Used the Have Disk option to browse to the extracted driver files/
Chose the saibus.inf

Basicly 6c & 6d from your instructions.