Monday, 12 December 2016

Logitech Formula Force Drivers for Windows 10 64 Bit (x64)



Almost 20 years on, the Logitech Wingman Formula Force still works in windows. Released around the time USB was just arriving on the market, these robust wheels date from back in 1998.

Logitech discontinued driver development in 2006, however Saitek did release a 64bit driver based on the Immersion SDK. A primitive Force feedback design by today's standards, but it still works with most modern games.

This driver was adapted by Sly_North from the below Saitek source. 

To breath a new bit of life into the Logitech Wingman Formula Force, here is a Windows 10 Driver (signed) that will permit installation into Win10 x64 bit without the need to disable driver signing.


UPDATE [Jan 2020] - This driver no longer installs on fresh Windows 10 OS. This is due to MS changing signing requirements under fresh installs in Windows 10. The below driver is signed with SHA-1, which is no longer trusted, thus not supported in newer releases of Windows 10. I'm looking for a volunteer to re-sign these driver with SHA256 as per Practical Windows Code and Driver Signing

Enjoy!

SHA256 C132B429B25D1AC0186C65A699FE6AC3131827E3E13297E8F507325B2B31B047

Saitek Source (updated 9/5/19)
SHA256 ECC4B98757FFBF53501A7D239CE3FA3B4D05B9543F091CA156D9EDE1ED44DB6F

Last version of Logitech Gaming Software (LGS) to support the wheel (Windows XP 32bit)
lgs460enu.exe

Credits: Leshcat of leshcatlabs.net for signing the drivers to make this happen and to Sly_North for the original Saitek driver mod. (http://web.archive.org/web/20160102083612/http://forums.logitech.com/t5/Logitech-G-Controllers/Wingman-Formula-Force-and-Windows-7-x64/td-p/428223?nobounce)





103 comments:

  1. Hi,
    Could you make the file available please.
    I'm searching drivers for th E-UA2 logitech.
    Thank you very much

    ReplyDelete
    Replies
    1. Unfortunately this post is about this specific model, that shared a driver/tech with other Immersion SDK wheels.

      Delete
  2. Pretty good post. I just stumbled upon your blog and wanted to say that I have really enjoyed reading your blog posts. Any way I'll be subscribing to your feed and I hope you post again soon. Big thanks for the useful info. click here

    ReplyDelete
  3. thank you, sorry for the inconvenience you could make a video with the steps to perform the installation for more extensive help to the community thanks

    ReplyDelete
    Replies
    1. You might want to look at https://www.youtube.com/watch?v=jyKrxxXOvQY

      Delete
  4. hello there. I have the formula force wheel and notice this is working for others. I do not have the native gameport on my mobo yet have the rockfire gameport to usb adapter. will this program work in tandum with the rockfire drivers?

    ReplyDelete
    Replies
    1. also how does everyone else connect these serial gameport wheels? I was told the rockfire would be the converter between analog to digital but it does not pick up my wheel

      Delete
    2. This Wheel is USB (+Serial RS232/DB9). These Drivers are for USB only. I suspect you might have a different wheel.

      Delete
  5. This comment has been removed by the author.

    ReplyDelete
  6. What files will I use on this repository for Windows 10 64 bit?

    ReplyDelete
    Replies
    1. The Zip file is the signed driver. The other files are provided for reference, should someone want to compare to the originals.

      Delete
  7. Unfortunately this post is about this specific model, that shared a driver/tech with other Immersion SDK wheels.

    ReplyDelete
    Replies
    1. Correct. If your wheel looks like the one pictured and you connect via USB it will work.

      Delete
  8. My Wheel looks exactly the same, just in Yellow. But the native Port isn't USB. I hava a USB-Adapter tho. Will this work? I can't seem to get the installation done. The .exe doesn't find me device.

    ReplyDelete
    Replies
    1. BTW the Model Number is E-ZA1

      Delete
    2. No this driver is strictly for the red wheel.

      Delete
  9. This driver seems to no longer work on the latest build of Windows 10?

    ReplyDelete
    Replies
    1. What error are you getting? And what version build /release of Windows are you running?

      1903/1909?

      Delete
    2. The calling of Force Feedback effects by various x64 applications causes Access Violation crashes on Windows 10 x64 1909.

      Delete
  10. Managed to get it working by disabling driver signing.

    ReplyDelete
  11. HELP!
    please give the driver link. yui on which windows does the steering wheel work?

    ReplyDelete
  12. HELP!!!please give the driver link. yui on which windows does the steering wheel work?

    ReplyDelete
  13. A little complicated method can be if you install VMWare or other virtual machine software and you install Windows XP over that. On installed virtual machine you can install the drivers of the Logitech Wingman Formula Force without any problem. You install your wheel-based games to Win XP virtual machine and you play on it. :)

    ReplyDelete
    Replies
    1. Yes this is an alternative to these drivers. However 3D games do not run as well under VMware IMO.

      Delete
    2. I tested with Need For Speed Underground 2 and Most Wanted. They run a lit bit slower like on host and there is some flashing, but it works with the original Logitech Wingman drivers. I used integrated video card. Maybe the performance can be better with native video card.

      Delete
  14. my pc runs windows 8.1 and i have the exact same wheel but yellow instead of red. when i plug in the game port to usb adaptor to my pc only the left led lights up and neither this or the logitech software detects the wheel. someone help?

    ReplyDelete
    Replies
    1. This driver isn't for the yellow wheel. This is only for the red wheel. They may look the same, but have different internals.

      Delete
  15. Been trying to make this work for years, but cannot make it work. The files everybody points to are always the same. I get "The hash for the file is not present in the specified cataloque file. The file is likely corrupt or the victim of tampering." :(

    ReplyDelete
    Replies
    1. You need to use the zip file. Logitech_FormulaForce_E-UA2_Windows7_64bits.zip This is the modified Saitek R440 Force Wheel drivers.

      Try https://www.7-zip.org/download.html if you are having issue unzipping.

      Delete
    2. This comment has been removed by the author.

      Delete
    3. The SHA values of the files do not correspond with the ones in Security Catalog

      Delete
    4. Not sure how that could be. The drivers haven't been modified. The only change as per the link above was the Device ID in the inf. The drivers and catalogue have been re-signed. Check the signature on the drivers. If they're invalid, I'd be suspicious something is modifying the files on your PC.

      Not had any one else report this issue.

      Delete
    5. Nothing wrong with my W10, it works when disabling driver signing. QED :)

      Delete
    6. Are the signatures valid on the .sys files?

      I note they're signed with SHA1, so if you are on a modern OS windows may not accept the SHA1 signature. MS has dropped support for SHA1 signed drivers.

      https://support.microsoft.com/en-gb/help/4472027/2019-sha-2-code-signing-support-requirement-for-windows-and-wsus

      I suspect if the driver was installed in an earlier Win10 Build, it will continue to honor the install. However if it's a fresh install, then the SHA1 policy is enforced during install of the driver.

      Delete
  16. Nice to see you are still around and posting!!
    I did use the zip file, no issues with unzipping.

    ReplyDelete
  17. This comment has been removed by the author.

    ReplyDelete
  18. Saved my wheel, installed successfully,great job!
    One question, how do I calibrate the wheel? I remember in old days windows has a game controller app in control panel to do it. In win10, it disappears.
    In NFS game, my accelarator padal keeps the arrow key down like beheavour, not function in the game.

    ReplyDelete
  19. To further dig out the root cause of my problem, I finally find that in my old XP system, the game controller setting has one checkbox option:combined axis. But in Win10, in the game controller panel, I can't find the similar setting, which cause the gas and brake pedal doesn't work in the game, how to solve it?

    ReplyDelete
  20. C:\Windows\System32\joy.cpl

    ReplyDelete
  21. @bARt, what is the use of this file? I tried another logitech driving force pro installation, seems only after installed logitech's driver, game software etc, the HW setting can have more parameter configuation. The worst case for my Formula force wheel is:the gas pedal is always at 100% when it is untouched.

    ReplyDelete
  22. @bARt, googled the function of joy.cpl. Thanks and yes I already find the access to it. Can't upload the picture, let me explain in detail. In property's test tab, I got a square with a cross in it, labeled:X Axis/Bra.. the cross is always at center bottom, once step on brake pedal, the cross go up to center top. On square's top right there is a red to blue color bar,labeled Gas. Without touch, it is full color, once touch gas pedal, the color bar reduce to 0.That is, the gas is at 100% when untouched. There are also 6 buttons below. The wheel steering and the buttons are working fine, just the pedals seems not right.

    ReplyDelete
  23. having the same issue as bArt: "The SHA values of the files do not correspond with the ones in Security Catalog"
    Problem:Also the disabling of the drivers check does not work.
    Zip Files are unzipped, Driver install results in: "Hash for file not in catalog.File is probably damaged or was changed without permission". Any idea how to get the good old wheel back to work?

    ReplyDelete
  24. Is this a fresh install of Windows 10? I suspect MS doesn't support SHA1 hashes with fresh installs.

    ReplyDelete
  25. I am having the same issue as mcmichael, Windows version 1903, trying to install for first time on new system. I receive the Hash error and attempting to use the .exe stops when prompted to connect the device.

    ReplyDelete
  26. up date, I was able to use the drivers and get things working by disabling driver signing enforcement and manually installing the driver from device manager. Thanks for the links. I used a version of this driver years ago.

    ReplyDelete
  27. Thanks Rob for posting this up. I have had my Wingman Forumla Force working with Windows 7 64 for years using the Saitek drivers. I just updated to Windows 10 and the wheel now won't work properly. The driver was installed/installs and the wheel is recognized and can be calibrated, but Force Feedback appears to cause games to crash. Strangely, the wheel will work fine if i force Assetto Corsa to 32bit mode, but is no good under windows 10 when running in 64 bit mode. ForceTest also won't work. Stumped as to what the problem is. Appreciate any suggestions.

    ReplyDelete
  28. Event viewer says...
    Faulting application name: rundll32.exe_shell32.dll, version: 10.0.18362.1, time stamp: 0x8ceb427f
    Faulting module name: SaiQFF04.dll, version: 6.0.4.1, time stamp: 0x46372b3b
    Exception code: 0xc000041d
    Fault offset: 0x0000000000005a80
    Faulting process id: 0x13e8
    Faulting application start time: 0x01d5d76e4432ac06
    Faulting application path: C:\Windows\system32\rundll32.exe
    Faulting module path: C:\Windows\system32\SaiQFF04.dll
    Report Id: db1a9aca-87ba-4863-a2a0-376b8760d167
    Faulting package full name:
    Faulting package-relative application ID:

    ReplyDelete
  29. Hey bro, can you give me original CD driver ? Cause this driver make program crash everytime using ffb in win10 and my CD driver is gone, can you give me that ?

    ReplyDelete
    Replies
    1. See the original post. I've linked to it.

      32 bit only and only Windows XP and older.

      Delete
  30. This comment has been removed by the author.

    ReplyDelete
  31. Are thats LG software waorking and detected perfectly on win XP 32 bit ? Cause when i try to use this in compability mode at win 10 64 bit thats software not detect my wheel

    ReplyDelete
  32. Thanks for the Saitek drivers, I am trying on Win 10 1809. It does not really work well as the paddles are not detected and there are some difficulties with the brake pedal being activated when gas is pressed. Have some trouble getting Steam to detect it as a actual wheel instead of xbox controller as well. FFB worked once for me in Dirt Rally and it is very strong.

    Also no Logitech Gaming Software (lgs) works anymore on 64-bit that supports the wheel. Even with lgs460 software which is the last to support this wheel is on Windows 98/ME only, per the list in the supplied readme. It does not support this wheel on Win XP, only USB HID devices listed in section 1.3.1 is supported on XP with lgs460.

    1.3.1 USB HID DEVICES

    WingMan Formula GP USB
    WingMan Formula Force GP
    WingMan Formula (yellow wheel)
    Logitech Driving Force
    Logitech MOMO Force
    Logitech Racing Force
    Logitech Racing Wheel
    Logitech Driving Force Pro
    Logitech Force 3D Pro
    Logitech Formula Force RX

    1.3.2 LEGACY USB DEVICES

    These products are supported under Win98/ME only.

    WingMan Force
    WingMan Formula Force

    1.3.3 GAMEPORT DEVICES

    These products are supported under Win98/ME only.

    WingMan Formula (black wheel)
    WingMan Formula (yellow wheel)


    1.3.4 SERIAL PORT DEVICES

    These products are supported under Win98/ME only.

    WingMan Force
    WingMan Formula Force

    ReplyDelete
  33. Two Questions:
    - Is this also working for Wingman Formula Force GP?
    - Which node (under the Device Manager) stands for the Wheel? Iam asking this, because I wanted to install the Driver manually but did not find the correct node.

    ReplyDelete
    Replies
    1. Checkout the .inf file for the HWID and then run powershell and use the command

      ##ALL USB DEVICES##
      Get-PnpDevice -PresentOnly | ?{$_.Class -eq 'USB'} | fl


      ##WHEEL VID/PID##
      Get-PnpDevice -PresentOnly | ?{$_.InstanceId -like 'USB\VID_046D&PID_C291*'} | fl

      Delete
    2. Which .inf file do you mean (this one: ".\Logitech_FormulaForce_E-UA2_Windows7_64bits\FF04_x64\SaiFF04.inf")?
      Or from the driver of my wheel (Wingman Formula Force GP), that supports only WinXP?
      When I use 'Get-PnpDevice -PresentOnly | ?{$_.Class -eq 'USB'} | fl', I can not really see, which device the Wheel is. Should the output contain 'USB\VID_046D&PID_C291' (that it does not contain on my system)?

      Sorry for the additional questions.

      Delete
  34. Wingman Formula Force GP is a different wheel.

    The .inf in the provided download.
    https://drive.google.com/open?id=1GSBy4NowuRJyDknjNG4h1lGCa_ysnA4r


    Only the .inf in the FF04 directly is modified. The others aren't used.

    USB\VID_046D&PID_C291 is the HWID from the modified .inf

    If you do not see this ID, then your wheel is either not conencted or a different model (as above, GP is different to this wheel).

    Just try searching for USB\VID_046D

    That is the Logitech Vendor/manufacturer ID they use in many of their products. https://devicehunt.com/view/type/usb/vendor/046D

    ReplyDelete
  35. Thank you for your help.

    I also realized that my Wheel is a different one. For it (Wingman Formula Force GP) the "old" logitech Software LSG 5.10 is working under Win10. So, I could solve it.

    Again, thank you for your support.

    ReplyDelete
  36. ciao a tutti, novità per i nuovi Win10?

    ReplyDelete
    Replies
    1. This is a english forum. If you want help , you are best to post in English and specific details.

      What are you asking?

      Delete
  37. Hello,
    I recover a logitech wingman formula force and I want to use it to play ETS2 but in my periphery manager, my wheel don't have the driver up to date. I search on internet but I don't find the good driver.
    So I would like to know if you have the driver or where can I find it. I'm in Windows 10 x64

    ReplyDelete
    Replies
    1. 1st step is to confirm the wheel you have.

      Right click the start menu and select Windows Powershell (Admin)

      Then paste in this command. It will list all Logitech wheels connected to the system (whether a drive exists or not).

      Get-PnpDevice -PresentOnly | ?{$_.InstanceId -like 'USB\VID_046D*'} | fl

      With any luck you'll see "USB\VID_046D&PID_C291".

      If not, copy the output and post back here.

      Note: This Blog post is only for the wheel pictured in the blog. If it's different, then you'll need another driver.

      Delete
    2. I did the 1st step and I see "USB\VID_046D&PID_C291\5&39CEA24A&0&1" many time so I don't know if it's the good wheel or not. But it's the same that the picture.

      Delete
    3. If you see that USB ID, then this drive will work. However if you'll need to disable driver signing in Windows 10.

      https://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/

      Delete
    4. But when I go on device manager and I check the pilot for my steering wheel, it says that the pilot is not installed. So I don't know what can I do for resolve this.

      Delete
    5. Pilot?

      If you run this command in powershell

      Get-PnpDevice -PresentOnly -Class USB | ft -AutoSize

      What is shown against the USB\VID_046D&PID_C291?
      What is the friendlyName?
      Search for that in Device Manager.

      Delete
    6. I don't have USB\VID_046D&PID_C291 in powershell when a run the command but I have
      USB\VID_046D&PID_C52B\5&39CEA24A&0&5, I don't if it's the same thing. The friendly
      name of this is composite USB periphery.

      Delete
    7. That's a Logitech Unifying receiver for mouse /keyboard. Unless you see the USB\VID_046D&PID_C291, the driver will not work.

      Delete
    8. What do I need to do for it toi work ?

      Delete
    9. This comment has been removed by the author.

      Delete
    10. Unfortunately it could be many things? Without physically inspecting it just guesses.

      I presume you have the power supply connected for the wheel? Are you seeign a green LED on the whee at all?

      To see if it's being detected at all.

      In Powershell:

      1.
      Disconnect the from the computer and run this command
      $d1 = Get-PnpDevice -PresentOnly -Class USB

      2. Plug in the wheel, wait 30 seconds

      3. Run this command
      $d2 = Get-PnpDevice -PresentOnly -Class USB

      4. Then run this command
      Compare-Object $d1 $d2

      If you see output, then this is the wheel USB ID. Please post it.

      If you see no output, then the wheel is not being detected by the PC/OS and there is a fundamental electrical issue, which you'll need someone local to diagnose.

      Delete
    11. I see the green light on my wheel.
      But when I use the command compare I don't see an output.
      Can the problem come from the generation of my pc ? Too recent ?

      Delete
    12. Not a generation problem. USB is a standard. There is some fault with the wheel.

      Confirm the command is working with another known working USB device.

      Do you see a green light without it connected?

      Delete
    13. The command is working with a mouse plug.
      I see a green light without it connected on my pc

      Delete
    14. I would say there is an electrical fault with the wheel. If it has power and another USB device registers with the command and the Wheel doesn't, then that rules out any PC issue.

      Delete
    15. So there is nothing to do to resolve this ?

      Delete
    16. Fundamentally, software cannot fix physical hardware issues. You could take it somewhere to get looked at, but I'd suggest it would be cheaper to buy a new wheel. You can pickup G25/G27's pretty cheap secondhand.

      Delete
    17. This comment has been removed by the author.

      Delete
    18. Ok I try to see that. Thanks a lot for your help and your patience.

      Delete
    19. I get the following:
      Win32_PnPEntity: USB Serial Converter (DeviceID = "USB\VID_0403&PID_6001\FTAPH9IA") =>

      Am trying to install the driver on this but it seems not to work - and the wheel is not recognised by the lgs software

      Delete
    20. If I understand right, you are using a regular USB Serial converter with the wheel. Unfortunately the driver doesn't support Serial (RS232) connections. Only native USB.

      As the wheel design dates back to platforms where USB wasn't a standard, Logitech/Saitech offered serial (RS232) option to connect the wheel, but that was quickly phased out.

      Only USB connection is support and that must be via the propriety adapter. The Adapter AFAIK, is passive. Simple pin plug conversion. I don't have the PIN outs, but someone maybe able to assist with that.

      Delete
    21. See this image. You need that USB to DB9 Adapter in the picture

      https://pc.watch.impress.co.jp/docs/article/981109/logi_1.jpg

      Siome references to the PIN out.
      https://www.eevblog.com/forum/chat/logitech-wingman-formula-force/


      Linux Support
      https://github.com/torvalds/linux/blob/master/Documentation/input/joydev/joystick.rst#i-force-devices

      Delete
  38. This comment has been removed by the author.

    ReplyDelete
  39. Hi there. I've been using this driver for many years on my Windows 7 64 bit. Been working great. I'm trying to get it to work in Automobilista 2 but it crashes to desktop more often than not. When it works it's only luck. The wheel works in Project Cars 2 which is the same game engine as AMS2. Any thoughts?

    ReplyDelete
  40. Try disabling FF in game

    ReplyDelete
    Replies
    1. Disabling FF basically defeats the purpose of having a wheel. FF works fine in Project Cars 2.

      Delete
    2. There was a version of this wheel (Yellow) that didn't have FF, so I'm not sure I agree with that statement.

      In short, it's not a driver thing, rather you need to take it up with the game developer. In my experience, they won't care as they're only interested in supporting current wheels, that they can actually still purchase.

      Delete
  41. Does this still work. I have the Formula Force and the Logitech software hasn't recognized I have anything plugged in.

    ReplyDelete
    Replies
    1. Yes. You need to disable driver signing if you are not using Windows 10, that was previously upgraded (inplace upgrade).

      This driver doesn't integrate with the Logitech Wingman Software. It's standalone.

      Delete
    2. I have disabled the signing but neither the lgs or saitek are recognizing the wheel. Which file in the google drive do I need to install? Thanks for your help

      Delete
    3. was able to get it installed, now a different problem Assetto Corsa crashes when I start the track. Doubt you know of that fix. Thanks for the driver!

      Delete
    4. Maybe try disabling FF in the AC. That has worked in some games.

      As this wheel uses a old implementation of FF SDK, some games well tested and crash.

      Delete
  42. Thanks to this post and to entering Win10 Test Mode I could install the Saitek drivers for my Wingman Formula Force... But I can't get the Logitech Monitor to work correctly (lgs460_x64.exe package), its main window is not shown when I double-click.

    ReplyDelete
  43. @Joandreu, none of the LGS software work for LWFF in Win 10. I tried ws365enu.exe, it can install on Win 10 but Profiler won't work, but with this and the Saitek drivers the wheel at least works with some games on Win 10.

    Working games on Win 10 (with FFB):
    Project Cars 2
    Dirt Rally

    Crash:
    ETS 2 (FFB must be disabled in game to make it work, otherwise crash, you can temporarily delete SaiQFF04.Dll* then untick FFB in game.)

    *To totally disable force feedback delete/move SaiQFF04.Dll in Windows/system32 folder. This is for some games like ETS2 where you can't disable FFB because the game crashes on load.

    Also the contents of my SaiFF04.inf is a little different, I have the China version of LWFF wheel so maybe my hardware ID is different:

    [SAITEK_MODELS.NTamd64]
    %HID_NAME%= SAI_HID_Inst, HID\VID_046D&PID_C291
    %USB_NAME%= SAI_USB_Inst, USB\VID_046D&PID_C291&REV_0100

    Overall it does the job for some games if you are not picky and can settle for 180 degrees turning, the force feedback is still strong and can be adjusted in these games. It's not a loud wheel either. I could not get my paddle shifters to work, and the pedals do feel clunky.

    For an older system on Win98 it would be better because you can use the Logitech profiler and adjust combined/separate pedals for old games.

    Alison has a trove of information here: http://alison.hine.net/gpl/controls/logiiff.htm

    And here's a ball bearing conversion / teardown: https://youtu.be/r9Ob4xQ93yY

    ReplyDelete
  44. Many thanks! "Assetto Corsa" recognizes the wheel in 32bit mode, I will try this setup by now.

    ReplyDelete
  45. Thanks Rob!

    I initially had trouble installing the driver, but once I found the wheel in the device manager under Human Interface Devices, it worked.

    ReplyDelete
  46. Thank you ! the drivers for win 32 work well with win vista . I'm using old PC for playing Rfactor 1, and no need more ! I found the red wheels (for only 5€) with db9 port. i make au adapter to usb and IT'S RUN !!! (force feed back too). I have lots of old wheels and this Red one and the yellow to, are the most precise. The FFB is quiet compare to the logitech Force GT (GT4 wheel). And the pedals base is very stable !
    With win10, i must start with the advanced boot options & F7, to install 64 bit driver. The wheels works , but no FFB. not matter.

    ReplyDelete
  47. Glad it worked out for you

    ReplyDelete