I’m afraid we won’t get any more answers here because I think that Jim Keir is no longer active here and that XPForce is no longer being developed either…? The last update was in September 2020
Okay. Plan B. Can you shut down icue and anything else in the task manager and try an install to see if that works? Please keep me in the loop and let me know as this is going to be very important to me.
Incidentally, I believe Jim does still get in here and as for updates, I seem to get something certainly every fortnight although that is just a quick blink when it initializes and I have been too short of time to delve deeper.
I don’t dare to install it on my fresh pc … If something goes wrong or doesn’t work together, then I can do a complete new installation … I’ll try to contact Jim via his website to clarify this before the installation.
As far as I understand it the installer isn’t trying to overwrite Corsair files but some shared files that Corsair (and other processes) are currently using and therefore blocking. While I don’t know exactly which files those are it really shouldn’t be a problem. I’m guessing it might be that XPForce comes with newer versions of some shared libraries or frameworks or something similar.
I honestly don’t remember. But I had it reinstalled a few days ago, and I had no warning. Also, I have updated iCUE last week, and got no warning either.
I have found out that the issue with the yoke slamming from one side to the other was actually an issue in my yoke… so that is working fine now.
I don’t think that what was happening to me is applicable to @bernard1954 , since my yoke is self built…
Hello Jim, I have a problem and wonder if you can help. New license yesterday. I am setting up a new Win 11 machine and it sees the G940 as one device. A scan with XP Force shows nothing at all, despite restarts, plugging into different sockets, etc. Anything you or others can do to help would be much appreciated, so thanks in advance.
I think I’ve found a workaround for the problem with hanging on startup. This is a driver problem, either in a DirectInput or Sidewinder FFB2 component, which must have been changed in a recent Windows update. There’s a new beta available at Downloads | The Hangar on the BETA tab. If you’ve been having this lockup, can you tell me if this helps? I’ll put this as a live update in a week or so unless I’ve heard there are problems.
It doesn’t overwrite any files by Corsair, AMD, or anything else. This is likely to be an update to core Microsoft runtime components which are used by almost everything; if this hadn’t updated them, something else would have done. There would be no need to reinstall anything else afterwards. The files that are installed are provided, pre-packaged and signed by Microsoft so everything is above board. Microsoft’s package only changes things if they are out of date.
The last program update was Saturday 14 August, 2021 ? You should get update warnings when they’re available, unless you’ve disabled the online check. I don’t come on here very often just because of day-job time pressures!
Sorry, I can’t add much. If it’s showing up as a force-enabled device anywhere, it should show up here. All I can suggest is that you might need manufacturer’s drivers, sometimes the ones included with Windows are OK for a general stick but don’t cover the force aspect. I don’t have a G940 to test with, so can anyone else help?