Hardware & Technical X52 woes... again and again

Regular X52. And a brilliant idea.

In Device Manager, it was coming up as X52 and failing every time. So I tried a different driver. Update Driver -> Browse my Computer -> Let me Pick. Picked the other driver for a regular USB device. And now it's working. Perfectly. Except I've lost my ED profile somewhere along the way. Whoops.
 
Regular X52. And a brilliant idea.

In Device Manager, it was coming up as X52 and failing every time. So I tried a different driver. Update Driver -> Browse my Computer -> Let me Pick. Picked the other driver for a regular USB device. And now it's working. Perfectly. Except I've lost my ED profile somewhere along the way. Whoops.

So you managed to manually select the correct device driver and it's now working?

Dorry to hear about the profile though.
 
Last edited:
I've had this exact issue, and sorry if someone has already suggested this:

You have to completely uninstall the drivers, re-boot, erase any remnants of the drivers, reboot. Then re-install, then wait specifically for it to ask you to plug in the stick. If you
plug in too soon, you get this loop.

To solve for this, only install the drivers, none of the other nonsense, and do not use the disk that came with the stick.

Like I said, I pulled my hair out over this.

EDIT: Glad you got it working!
 
Last edited:
I finally got x52 drivers working last month after a clean install of win10. After today's Win10 update the drivers won't install. I tried everything Saitek said to do and they will not install. I find it strange that everything else works but my X52. I doubt this is a Win10 problem but lousy support from Saitek. The beta drivers are about 2 months old with no update in sight. What a mistake buying a Saitek product. Any suggestions on a better joystick?
 
I run the X-55 without issues. Some have gone to the Warthog but I really like/need the yaw in the JS. Plus the Warthog is quite expensive.
 
I use mine in conjunction with voice attack. I find it to be a real nice x52 pro stick.

I needed a clean install to get it to work right though.
 
The majority of the time these issues are down to USB drivers and nothing to do with the stick drivers, far too many people leave windows to handle the installation of the USB drivers and that causes problems.
 
There is a program called 3DChip that I had to use in Windows 10 (never had to use it before in any Windows in the past) which basically recognize all of your plugged devices in your PC and then find you the right drivers (or the ones that should work) for the OS you are using.

It is quite simple and helped me to make my Sound Card work on Windows 10, which with the drivers I had (official ones) it never worked. Windows 10 is a pain the asp when it comes compatibility sadly but also Saitek drivers always were a pain in the asp to install as far as I can tell.

You can download it here: http://sourceforge.net/projects/dpchip/

Hope it can help with your problem, it is quite easy to use but plug your Joystic before executing the program. Then if it shows up on the list, you will see which drivers you need to install and it will give you the direct download link for it. Install the driver and see if it works.

If it doesn't, blame Saytek/MadCatz (I own a MMO7 mouse and it works fine on Windows 10).
 
So you managed to manually select the correct device driver and it's now working?
No, I had to manually select the wrong device driver and now it's working. I should have screenshotted the box, but I was pretty flaked out at this point. It was a random generic USB-something driver that Windows suggested. Selecting it appears to have given Windows the ability to use the downloaded Saitek driver in place of whatever it was trying to use before - probably

I've had this exact issue, and sorry if someone has already suggested this:

You have to completely uninstall the drivers, re-boot, erase any remnants of the drivers, reboot. Then re-install, then wait specifically for it to ask you to plug in the stick. If you
plug in too soon, you get this loop.

To solve for this, only install the drivers, none of the other nonsense, and do not use the disk that came with the stick.

Like I said, I pulled my hair out over this.

EDIT: Glad you got it working!
Thankyou. I found exactly the same info and tried it a few times. A clean install wasn't enough; I went in and reinstalled Windows itself a few times with no joy. The actual fix was unexpected, random and utterly bizarre.

I finally got x52 drivers working last month after a clean install of win10. After today's Win10 update the drivers won't install. I tried everything Saitek said to do and they will not install. I find it strange that everything else works but my X52. I doubt this is a Win10 problem but lousy support from Saitek. The beta drivers are about 2 months old with no update in sight. What a mistake buying a Saitek product. Any suggestions on a better joystick?
I was told Monday when I pushed Saitek tech support for some good news. I'll be pleasantly surprised if there's something available then, but I'll be waiting for others to clear the way regardless. I've done my bit on behalf of these charlatans' QA department.

As for other suggestions - I have none. The HOTAS market is too small; I've never found another stick at the same price point. Which probably explains the appalling service, come to think of it.

There is a program called 3DChip that I had to use in Windows 10 (never had to use it before in any Windows in the past) which basically recognize all of your plugged devices in your PC and then find you the right drivers (or the ones that should work) for the OS you are using.

It is quite simple and helped me to make my Sound Card work on Windows 10, which with the drivers I had (official ones) it never worked. Windows 10 is a pain the asp when it comes compatibility sadly but also Saitek drivers always were a pain in the asp to install as far as I can tell.

You can download it here: http://sourceforge.net/projects/dpchip/

Hope it can help with your problem, it is quite easy to use but plug your Joystic before executing the program. Then if it shows up on the list, you will see which drivers you need to install and it will give you the direct download link for it. Install the driver and see if it works.

If it doesn't, blame Saytek/MadCatz (I own a MMO7 mouse and it works fine on Windows 10).
Looks interesting, thanks.
 
In Device Manager, it was coming up as X52 and failing every time. So I tried a different driver. Update Driver -> Browse my Computer -> Let me Pick. Picked the other driver for a regular USB device.

Thank you!
I was having the same problem, and this solved it. For some reasons, selecting the generic USB driver lets the installation of the Saitek's one (that usually stopped dead after the request to plug the controller in) reach the end successfully. Now everything works again.
 
ok guys need some advice please...im a hotas user myself...I use a homebrew version,a single cyborg x for flight stick,and a gamespower throttle that I made into a separate usb...all works well as expected,but I have always been wanting a x52...

this Monday coming I have 3 options...
get a x52 with a new turtle beach headset
or
get a x52 pro
or
go for x55 version?

also im on 8.1....I have tried to go to windows 10 via the free upgrade offered 5 times now,and each time win 10 boots I cant open folders or do anything it just hangs lol

x55 looks cool with its buttons and knobs to twiddle lol,but I like the lights and the screen on the x52..


what is a space pilot to do in this situation gents?
 
Last edited:
I have an X52 Pro and had huge issues with getting it working right with Windows 10, after having it working flawlessly in Windows 8 and 8.1 and before.

The solution I have is to use:
Driver Version 6.2.2.4
Software Version (for Profiles) 7.0.27.13

Other driver/software combinations cause varying errors, including crashes, keyboard and mice not working, so on and forth. As it is, with the above, if I have the X52 Pro plugged in to the USB2 port, it prevents the Windows 10 screen saver / monitor sleep from activating. Also I get some corruption on the throttle display. Aside from that it is usable. At the moment I am using a USB hub built in to my monitor, and testing showed it makes no difference if plugged into the back of the PC (the only ports on the front are USB3).

You might have to go in via Device Manager to forcibly un-install different drivers. Then re-install the ones above. The ones above are available on some Saitek FTP site which I can't remember the link for right now.
Of course, I make no guarantees this will work for anyone else, but it works for me. I tried the newest GA drivers available on Sunday (I think they date around July/August), and they didn't work - reverted back to the combination above and it's back to (almost) working .

R
 
Regular X52. And a brilliant idea.

In Device Manager, it was coming up as X52 and failing every time. So I tried a different driver. Update Driver -> Browse my Computer -> Let me Pick. Picked the other driver for a regular USB device. And now it's working. Perfectly. Except I've lost my ED profile somewhere along the way. Whoops.

Can confirm as a temporary fix/workaround. The problem is caused by the latest windows 10 update. I updated today and my x52 stopped working.
 
Also had issues getting the stick to work.
Even though I had my stick connected to an usb 2 port, I had to disable the 'iusb3mon' driver from intel to get it working.
If I leave that one running, I can't use ANY usb device after plugging in the x52 and rebooting the system.
-
Don't remember exactly how I disabled it though.
I now read it is possible to remove it with the 'Add/Remove programs' feature, but that surely wasn't there when I had that issue.
-
Found out because I could boot my system properly after initial windows installation, but never after installing the mainboard's driver cd (if the x52 was plugged in).
When installing the drivers one by one, it always failed after a reboot once the intel usb3 drivers had been installed.
And that all was without installing anything from saitek, so it was going wrong at the hardware level already.
 
Back
Top Bottom