Stitek X55 & X52 and Windows 10

Chip Patton

Chip Patton
So I had an issue when I upgraded to Windows 10 with both My Stitek x55 and X52pro HOTAS systems. Basically after I upgraded the stick wouldn't work and windows wouldn't recognize it and the Stitek driver installer also wouldn't recognize it.

I prefer the X52 pro so that's what I first noticed it on. Naturally, I'm about to RMA this stick and go grab the X55 out of the closet. I plug it in and to my surprise the same thing happens. The chances of two sticks being faulty after an upgrade, well, I'd have better chances of hitting the megamillions jackpot.

So I did some digging, some very deep digging on Google. I found no solutions but found that Windows 10 has an issue with dealing with USB drivers -- namely it has issues getting rid of old drivers and replacing it with a current driver. I don't know all the technical details as I don't have source code access to windows, but I can tell you what I did to permanently fix the issue:

In the device manager I found the joystick that had the malfunctioning flag (the yellow !) and it said "Unknown USB Device" or something to that tune. I tried to manually install the driver there and it gave me an error something to the tune of "the driver is missing an attribute and could not be installed, perhaps it is a driver intended for Windows 95 or later". Strange error right? Its actually normal.

So I got a little sly, I forced windows to "recognize" the joystick as a "generic USB device". This purges the driver it was using and forces windows to disassociate the device with the old driver. Suddenly, the X52 pro lit up with all of its lights, the LCD lit up, and the Stitek installer's "Next" button came to life. I finished the "windows 10" driver update and all was well.

(The way to force the use of a driver like that is to right-click the device and click "Update Driver", then use the second option to chose your own driver, and then "browse from a list". Once you browse from that list, you can find the USB category and find "Generic USB Device", click that and hit "next")

When Stitek came out with the W10 driver, it happened again. Once again I went to the device manger, found the "malfunctioning USB Device" manually installed the "Generic USB Device" driver, and viola, it worked again.

So just a note, for you guys that are about to send your HOTAS systems back for RMA, give this a shot first. Let me know if it worked.
 
Last edited:

Calaban

Calaban
The fix to this problem, (worked for me), was to first delete the Saitek beta drivers and software, all the MadCatz drivers and software (search for madcatz in the delete programs list), reboot, and then....

[let the excitement build a sec.. ;) ]

Go up one directory from the beta folder in the Saitek FTP page, and find the "SST 6.6.6.9" driver. Works like a charm.
 

Chip Patton

Chip Patton
Calaban said:
The fix to this problem, (worked for me), was to first delete the Saitek beta drivers and software, all the MadCatz drivers and software (search for madcatz in the delete programs list), reboot, and then....

[let the excitement build a sec.. ;) ]

Go up one directory from the beta folder in the Saitek FTP page, and find the "SST 6.6.6.9" driver. Works like a charm.
Click to expand...

Oh I tried this, even after the restart W10 still held on to the driver and named it as a "malfunctioning USB device". I've noticed some users have had the same issues in the forums, even after following the MadCatz support page and are RMAing their devices which means they will send them back a refurbished device that's usually in worse condition than the one they sent back (bad idea).
 

Calaban

Calaban
I had that issue too, but for me it turned out I just didn't remove enough MadCatz stuff. There was a "software development" thing hiding in the works.
 
Last edited:

Albasil

A
Follow instructions on saitek site for beta drivers works fine, as long as you follow the bit uninstall previous ones and delete all instances of it. Beta works well
AB
 

Paul Bambury

P
There does appear to be a problem installing the latest drivers (7.0.47.1) if you have Windows 10 with the November update, where the driver installation program can't find the hardware and you end up with an 'Unknown device'. Further attempts to install the driver give the error "The driver installation file for this device is missing a necessary entry. This may be because the INF file was written for Windows 95 or later. Contact your hardware vendor."

I raised a ticket last night with Saitek and they got back to me very swiftly with a solution

Due to some changes operated by Microsoft in their latest updates some our USB connected devices have some issues.

Please try the following workaround that solved this matter on some of our customers PCs:

Run the driver installer - the beta driver from the Madcatz site, then do as instructed and plug your X52 in. Let the installer run. Once Windows has completed its process, you'll need to go to device manager. From there, right click on the X52 or the unknown device if the X52 does not come up (with the exclamation mark in a yellow triangle on it) and select 'Update Driver.'

You'll need to choose 'Let me pick...' and then choose the first device - Generic USB Device or similar - NOT the X52 one.

Your X52 should then be recognised by Windows 10 and your installer should continue with its installation process.
Click to expand...

I can confirm that this worked work for me
 
Last edited:

Deleted member 110222

D
I'm going to upgrade to 10 in the next couple of days. Is it pretty much guaranteed that I'm going to have a fun little time with the drivers for my HOTAS? I use a standard X52.
 

Calaban

Calaban
its what I went through with my win10 upgrade (basic x52)

You may see ghost mouse inputs, with soundcard buzzing, and upon unplugging the x-52 you may see all usb plug and play functionality vanish (if you unplug the keyboard usb, it wont find it again)
 

Chip Patton

Chip Patton
Hambut_Bulge said:
There does appear to be a problem installing the latest drivers (7.0.47.1) if you have Windows 10 with the November update, where the driver installation program can't find the hardware and you end up with an 'Unknown device'. Further attempts to install the driver give the error "The driver installation file for this device is missing a necessary entry. This may be because the INF file was written for Windows 95 or later. Contact your hardware vendor."

I raised a ticket last night with Saitek and they got back to me very swiftly with a solution



I can confirm that this worked work for me
Click to expand...

Exactly, they need to post this in their knowledge base. I have no faith in MadCatz's support tickets :p
 

diventkna

D
NullAndVoid said:
Still can't believe MadCatc still has a beta driver for Win10, they have had months to sort that out.
Click to expand...

Did a clean install of Win 10 64 and can confirm that the latest x55 drivers work ok (no previous drivers present). X55 is not my problem the b****y Cyborg V5 Keyboard drivers are truely knacked, even the beta win 10 64bit ones!
 

bapef

B
Hambut_Bulge said:
There does appear to be a problem installing the latest drivers (7.0.47.1) if you have Windows 10 with the November update, where the driver installation program can't find the hardware and you end up with an 'Unknown device'. Further attempts to install the driver give the error "The driver installation file for this device is missing a necessary entry. This may be because the INF file was written for Windows 95 or later. Contact your hardware vendor."

I raised a ticket last night with Saitek and they got back to me very swiftly with a solution



I can confirm that this worked work for me
Click to expand...


I can also confirm that this works, however it also leads to a reproducible BSOD in Windows 10. Whenever I select a profile for my x-52 pro in the profiler software, play ED for awhile and then go to select a different profile or clear profile the OS crashes and the system throws various errors when doing so some mentioning the saitek drivers others being extremely generic in nature but always when trying to move from a selected profile.
 
You must log in or register to reply here.
Back
Top Bottom