However it is my understanding that there are many programs out there that conflict with the X-52 for one reason or another, and these conflicts may be made all the worse by differences in how Windows 10 handles drivers as opposed to Windows 8.1. I have been issue free for 2 days now as this is the first time I have been able to use my X-52 at all since I upgraded to Windows 10. That being said, I am currently running the latest driver for the X-52 Pro, I believe it's version 7.0.40.9圆4, and I don't use the programming software. There are other ways they could have accomplished what they wanted to do as well. It is probably bad practice for Avast to block access to a commonly used system folder as well. Probably not the best way for them to go about it, but it is what it is. I'm very confident that Avast was the problem in my case, and I'm sure I can't be alone in this as Avast does indeed lock out that folder, which the Saitek drivers also demand access to.
There may be other factors in play on your system depending on what you have installed. This did it quickly and easily: ģ) Go to the control panel (not settings!) select "Uninstall a program", then uninstall anything with Saitek or Mad Catz as the Manufacturer.ģa) If you get error messages in step 3, download the Fixit Utility here: and use it to uninstall all Saitek and Mad Catz entries.Ĥ) Right click on the Start menu, select run and type in "regedit" without quotes and hit enter.ĥ) In Regedit, navigate to HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInputĦ) Delete all Saitek Keys, Delete all keys starting with VID_06A3&PIDĨ) Install your X52 driver of choice and test. NOTE: This procedure is fairly advanced and should only be attempted by those who are comfortable with mucking around with permission settings and the registry.ġ) Uninstall Avast! and set Windows Defender as antivirus.Ģ) Reset permissions on the C:\Windows\Temp folder. I did the following to successfully correct this: If you are running Avast! (and possibly any other antivirus with self protection) and unable to open this folder, you are likely to experience issues with the X52 drivers at some point as the drivers periodically access this folder particularly during uninstallation and reinstallation resulting in incomplete installations and eventual random glitches. Ok the tip off to Avast! being the issue was my inability to access the C:\Windows\Temp folder.
0 kommentar(er)
