Hardware & Technical Windows 10 & Saitek X52 pro

Just got the X52 Pro today, when I install the drivers for the x52 pro on win 10 the mouse goes all over the place. I can get it working by disabling the programming for mouse in the device manager.Also the mouse stick on the throttle doesn't work.
And in the software the mouse xand y axis in the profiler is selecting on and off. Ive tried all available drivers.(from 42-53 plus the SD6) Any new ideas?
 
So anyone know how to get the X52 to be recognized by Windows 10 again? I haven't played in a couple of months and now my computer isn't detecting it even though its getting power and in the same old USB 2.0 port. I tried running the newest driver/software installer the 7_0_53_6_x64 version, but windows is popping up the smart screen filter and saying its from an Unknown Publisher. Any help would be appreciated.
 
It seems that I might have found a happy solution to my windows 10 BSOD problems caused by the X52pro drivers. I noticed a while back that task manager in windows did not display cpu usage correctly, it was always showing 100% cpu utilization even though that was clearly not the case. Then I tried to use Resource monitor to more closely check the processes. Resource monitor was giving totally erratic numbers and it basically froze my computer very frequently, I was barely able to close the program from all that stuttering. (Felt like computer would have been swapping constantly). I started googling about the issue and it turns out that I had to update my Bios version. My motherboard is Asrock P67 pro3, but it seems that many different Asrock MB owners have faced similar issues. So off I went and updated my Bios to the latest version offered by Asrock and it seems that it solved all my problems. Task manager now shows cpu usage correctly, Resource monitor is not stuttering and works correctly and most importantly I've not had a single BSOD since I updated the Bios around a week ago. So if there is somebody else struggling with these problems, I suggest you try this approach if all else fails. I'm currently using the drivers I mentioned in my previous post and they seem to work fine, at least for now...
 
Back
Top Bottom