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$.

[Chris Solomon]

thats what i thought you did. just making sure

[GegeTS]

Hi all, just a latest question : before you reinstall the latest SST software (from madcatz one) as you described, did you install the latest saitek(madcatz) drivers i.e. for the X52 Pro or have you installed the SD6 drivers from saitek. As when installing all these stuff you may have to install the correct driver for your controler before installing the software SST part.

What is the best ? Installing the most recent driver (Madcatz) for the controler and then downgrade the driver SST software via Peripherals manager by the SD6 Saitek SST software ?

I'm stay a bit confused between the driver controler and the SST software update. Sorry if I missunderstand some of your explanations.

[kpt. baton]

Hi, identical problem, the solution presented here did not work. One simple solution is to put Windows 8.1 in test mode which accepts unsigned drivers but this creates other problems,like Arma 3 anticheat software refuses to run. I had it run in test mode for two months but decided to fix it today.

What worked for me just now: (CREATE RESTORE POINT FIRST :) )

uninstalled SST software (not joystick drivers, I did not touch them, they are the latest ones from Saitek)

From device manager uninstalled:
Control Panel > Device Manager > Programming Support > Uninstall all Programmables


From registry:
+HKEY_CURRENT_USER
+System
+CurrentControlSet
+Control
+Media Properties
+Private Properties
+Direct Input


Deleted any folder inside the Direct Input that begins VID_06A3 also folders SAITEKHOTKEYS, SAITEKKEYBOARD and SAITEKMOUSE

Then installed SST software for X52 (my stick is X52 Pro) (Smart Technology 7_0_27_13 - downloaded today from Saitek website) - it detected Programmable Root Enumerator normally and Programmable Hotkeys, Programmable Support for Keyboard and Programmable Support for mouse with exclamation marks (error 52)
Then I doubleclicked on Programmable Hotkeys, update drivers, browse, let me pick and selected the only one showing, at which stage windows installed it correctly, automatically installed the other two as well and everything works now. Driver version is 7.0.27.13 from 16/04/2013
Windows 8.1 64 bit

(link that gave me this ideas - https://forums.frontier.co.uk/archive/index.php/t-153006.html)

[Chris Solomon]

doing what you did decreases the security of your system. when i was running win 7 i briefly put windows into test mode using the device stage visual editor, and the madcatz drivers started working briefly. but the moment i took windows out of test mode, they stopped working again.

also doing what you did requires messing around with registry permissions which is a dangerous task and should never be performed unless you know what you are doing and are ready to accept the concequenes of what happens if you royally screw thing up. the driver change process you describe is mostly identical to what i did in my solution for my x52 pro.

I haven't used my x-52pro in a whil as it's been connected to my old XP desktop which has fallen into disuse after the 500Gb PATA drive 'got stuck' intenrally. I would probably get a new HDD for the PC, but i can no longer find PATA drives of equal size or price. my 500Gb cost me around $40-$60 brand new. now you can only find smaller size PATA drives for $100 - $200 and up. I do plan on scavenging most of the components of the system eventuallyu as it has some good hardwar on it that is still considered up to date. sorry got sidetracked.... back to the topic..

The only drivers disc i have are older XP/VISTA drivers that came wit joystick when i bought it. and they -might-- work on win7 but saitek changed from using the term SD to SST for it's software since the version i have. so my solution, given the fat that I had no other previous version availible works. if you have a previous version of the madcatz software that works, then please, post the file name of the setup file, so i can look for it on the saitek archive page.

I have dual boot win10 (formerly win7) and win8.1 setup on my machine, I will try dualbooting again and try my solution as posted to see if it works on 8.1 Pro WMC. I am hesitant however, because i found that 8.1 will cause massive file corruption anmd filesystem failure if it accesses ant drive that windows 10 has accessed. I have already lost 1Tb worht of data twice to this problem. I am still trying redownload all my steam games from the last incident. Heres hoping that excluding access to my primary and my data drive (make win8 think the drives have no drive letter) will be enough to safeguard my stuff, So if you don;t hear from me for a week or more, it means Win8 ate my win10 install again.

One last note: on my machine my computers hotkeys (TOSSYSHID) were registered in the directinput key, so just willy nilly deleting stuff can have very detrimental effects on your system

[GegeTS]

kpt. baton původně napsal:

Hi, identical problem, the solution presented here did not work. One simple solution is to put Windows 8.1 in test mode which accepts unsigned drivers but this creates other problems,like Arma 3 anticheat software refuses to run. I had it run in test mode for two months but decided to fix it today.

What worked for me just now: (CREATE RESTORE POINT FIRST :) )

uninstalled SST software (not joystick drivers, I did not touch them, they are the latest ones from Saitek)

From device manager uninstalled:
Control Panel > Device Manager > Programming Support > Uninstall all Programmables


From registry:
+HKEY_CURRENT_USER
+System
+CurrentControlSet
+Control
+Media Properties
+Private Properties
+Direct Input


Deleted any folder inside the Direct Input that begins VID_06A3 also folders SAITEKHOTKEYS, SAITEKKEYBOARD and SAITEKMOUSE

Then installed SST software for X52 (my stick is X52 Pro) (Smart Technology 7_0_27_13 - downloaded today from Saitek website) - it detected Programmable Root Enumerator normally and Programmable Hotkeys, Programmable Support for Keyboard and Programmable Support for mouse with exclamation marks (error 52)
Then I doubleclicked on Programmable Hotkeys, update drivers, browse, let me pick and selected the only one showing, at which stage windows installed it correctly, automatically installed the other two as well and everything works now. Driver version is 7.0.27.13 from 16/04/2013
Windows 8.1 64 bit

(link that gave me this ideas - https://forums.frontier.co.uk/archive/index.php/t-153006.html)

Thanks to Chris Salomon and you kpt.baton the last solution worked here like a charm. I have tryed also to install the latest (from madcatz) SST software after have been installed and uninstalled the other one for the X52 (no pro as @kpt suggested) and the result was a icon warning over all the programmable root enumerator stuff. So applyed the update driver choosing the SD7 from 2013 Year for the X52 (no Pro version) via device manager and all the warning icons disappeared and all is well functionning now. When I use my X52 Pro I didn't use the saitek pluggin to display the frequencies on the throttle panel. The only problem I get too is when I set the clutch button on my X52 Pro throttle as a switch to load a particular profil that doesn't run very well. I use both the clutch button and the POV1 on the stick to choose what profil I want to load but the selection scroll is a bit hard and not functionning very well. Althought now I can play with a particular profil overall to be able to use the pinkie on the stick and the mode rotary button to get more buttons mapping.

Thanks to have found a good solution to fix this annoying programmable root enumerator stuff.

PS: Yes Chris if I could to send you some cookies or cake as a thanks I probabily do that ;-)

[Chris Solomon]

i tried my solution on windows 8.1 and it worked likeit did on windows 10, so cpt. baton, I will assume the reason it did not work was due to user error.
the fact that you had more recent driver or the fact that you were using the x52 software not the x52pro software may have been at fault. I am using the X52Pro software and drivers for my X52 Pro joystick

[Chris Solomon]

there appears to be some issues with my use of the older drivers, mainly, the MFD backlight keeps turning off. if some one has a copy of the Madcatz SST where the software device drivers work, or a version of the saitek software that is newer than the one in the links i posted let me know. I would love to get a hold of the setup file.

the othe issue which i am stil investigating, is unplugging the x52pro triggers a bug in windows 10 on my machine where the mouse starts to move slowly and for every mouse movement the PC speaker beeps, or when the mouse button is pressed the pc speaker beeps. additionally when ever i unplug the x52 pro, the USB subsytem of windows stops working. Because the issue with the mouse was occuring before i started trying to hook-up my x52pro, it is something with windows. I don''t think its hardware, as it occurrs with multiple mice on both USB and PS/2 ports. I did notice that the last time i happened, when i moved the mouse thumb stick on the throttle, the pc speaker beeped just like it did whenever i moved the mouse. but as i said, this is a windows 10 issue and not a joystick related issue.

[Chris Solomon]

managed to find SST 7.0.27.13 on the ftp site (joy!)
I wil bgin testing my fix using this version of SST shortly.

64-bit: ftp:/ftp.saitek.com/pub/software/full/Smart%20Technology%207_0_27_13%2064bit.exe

32-bit: ftp:/ftp.saitek.com/pub/software/full/Smart%20Technology%207_0_27_13%2032bit.exe

i wish the ftp site was better organized.... finding stuiff is a bit of a pain like it is.

also found a beta version that is slightly newer than the one above

ftp:/ftp.saitek.com/pub/software/beta/Software_7_0_33_91_BETA.zip

i dont know if it's 32 or 64 bit. might contain both.

[Chris Solomon]

OK... tried my fix using the version posted above. it worked. after installing sst 7.0.27.13, i checked to make sure everything was working, and then installed the latest version. once again the programable root enumerator was disabled by windows.
I reverted the softwar driver programmable root enumerator back to the previous version and the other software devices followed suit. thanl you to kpt.baton for finding the proper version that i was looking for. You get the COOKIE!

[Chris Solomon]

          For KPT. BATON ONLY!
       _.:::::._
     .:::'_|_':::.
    /::' --|-- '::\
   |:" .---"---. ':|
  | : ( O R E O ) : |
   |:: `-------' ::|
    \:::.......:::/
     ':::::::::::'
        `'"""'`   

[GegeTS]

XD. Yes well done Chris. I done the exactly same procedure install as your described just above and as you I got a warning icon (althought not disabled) over all stuff Programmable root enumerator. reverted back to the 7 version from 2013 year and it worked like a charm not showing any error on programmable root enumerator stuff.

Thanks to all finding the best solution to fix this code 52 error.

PS: your 7.0.27.13 64 bits file version link is exactly the same as for the X52 (no Pro) SST software version avalaible on the Madcatz web download site ;-)

[Chris Solomon]

it helps that the same SST is used for the x52 and the x52 pro. the only real difference in terms of software, is the hardware drivers that get installed prior to the SST

where did you locate the driver on the madcatz site? i looked there could not find anything on the x52, x52 pro or previous versions of the software. the only place i could find the current version even was the saitek site

[GegeTS]

Chris Solomon původně napsal:

where did you locate the driver on the madcatz site? i looked there could not find anything on the x52, x52 pro or previous versions of the software. the only place i could find the current version even was the saitek site

HERE[www.saitek.com]

You may choose on the drop down list pro flight range then the X52.

If you get the madcatz main page site you can browse to the saitek flight hardware and on top down left page you have SUPPORT and DOWNLOAD items by choosing download you get the page linked above

[Chris Solomon]

ok, i thought you meant the madcatz portion of the site not the saitek portion. unless madcatz pulled the version that had issues, 7.0.27.13 is not the latest version. the version that had issues had a 2015 date, which is why this thread exists

[GegeTS]

indeed Chris it is the Saitek portion...Yes the latest X52 Pro 2015 version has some bug in comparison with the X52 from 2013 year.