Discussion WARNING To ALL users of the old Logitech gamepads, joysticks, and racing wheels on Windows 10

Status
Not open for further replies.

QwerkyPengwen

Splendid
Ambassador
After three days of searching hi and low on the internet, along with then finally talking to some people over Discord I have discovered the issue with the older Logitech racing wheel's that use the older 5.10 gaming software.

The issue is pretty simple, but a huge pain in the butt and a let down.
The drivers are so old, that they no longer work with GameInput Redistributable in the newest update to Windows 10 v.2004.

If you have the Driving Force GT, G27, or another wheel from the same era that uses the older 5.10 gaming software, and cannot get games to recognize the controller, this is why.

The newest update to Windows has officially borked support for the older hardware, and games that use the old GameInput for supporting said hardware along with the old drivers for this hardware.

I am sad to see this happen and unfortunately there is nothing that can be done unless either Logitech and/or Microsoft decide to do something about it.

I do not know about lost compatibility for other hardware such as ThrustMaster.

But as it stands, the DFGT, Original GT, and G27 (and any other Logitech wheel that uses the old 5.10 version of gaming software as well as potentially other legacy Logitech devices) will no longer work as of right now with the new 2004 update to Windows 10.

I have to buy a different wheel now.

However, if there are any users here that have the DFGT, G27, or any other Logitech wheel that uses the old software, and are running on the latest 2004 update, that DON'T have any issues, and seem to have their wheel's working just fine, please let me know so I can get in touch with you and perhaps maybe discover something that might help us find a personal workaround/fix for getting these older wheels to work.
 
Last edited:
I can confirm that there is a conflict between G27 drivers and win 10 v2004. There are two ways though to make the wheel work (or at least what worked for me):
  1. Unplug the wheel's usb, wait for some secs (20 - 30) and insert it again OR
  2. Insert an other usb (e.g a usb stick) and 10-15 seconds after the wheel will turn right left (calibrating process)
It should work..

But i agree. A fix MUST come out asap....

PS I found a permanent solution. Go here to find it:

https://forum.reizastudios.com/thre...yone-else-with-this-problem.11602/#post-82404
 
Last edited:
I can confirm that there is a conflict between G27 drivers and win 10 v2004. There are two ways though to make the wheel work (or at least what worked for me):
  1. Unplug the wheel's usb, wait for some secs (20 - 30) and insert it again OR
  2. Insert an other usb (e.g a usb stick) and 10-15 seconds after the wheel will turn right left (calibrating process)
It should work..

But i agree. A fix MUST come out asap....

PS I found a permanent solution. Go here to find it:

https://forum.reizastudios.com/thre...yone-else-with-this-problem.11602/#post-82404
I believe I already said this but I will re-iterate it again.
The wheel works fine, and the drivers seem to be fine as well as the software I have to use (v5.10 of the gaming software)

The wheel is recognized by device manager.
The wheel is recognized by the software.
I can press buttons on the wheel and the software reports what button is being pressed.
I can go into the advanced properties of the wheel using the software, and go to the test section and everything works.
The wheel spins left and then right when plugged in like normal.

The issue is not that, the issue is the GameInput Redistributable and how it's borked in the new update meaning that even though the wheel works, the software works, drivers work, games will not see the wheel. Period.
Not a single game.

But, to do my due diligence, I performed all of the supposed fixes and none of them did anything for me as expected.

And Microsoft has already stated that they looked into any issues with the GameInput Redistributable, and said that there is nothing wrong with it and that they basically won't look into it any further.

However, newer game devices that use newer updated software and drivers work just fine, for example: any wheel that can use the new G-Hub software from Logitech works just fine, and games see the wheel. Products such as the G29 and the G920.

What this means more than anything to me is that with this new update, if our older wheels and such are going to work properly, Logitech themselves need to release updated drivers and add support for these wheels in the G-Hub software so that we can continue to use them.

And based on what you said here in your post, your issue was with the wheel not booting up properly, but it doesn't sound like you actually tried using it in a game.
Can you please try using it in a game or more than one game to confirm if it works for you on 2004 update?
The games I've tested personally are Dirt 3, Assetto Corsa, Forza Horizon 4, and Project Cars 2

This issue is not mine alone, but the same for others I had talked with when we all did our troubleshooting for both the Driving Force GT and the G27 wheels.
 
I 've tested all my racing titles. AC, RRE, AMS2, ACC, rF2, DR2.

All work as expected
Interesting.
You're the first person I've come across who is on the 2004 update to Windows and using the older hardware with the older v5.10 of the Logitech Gaming Software and is having things work.

Interesting that what you did to make things work for you doesn't work for me or other's that I know of that had this issue.

And this so called "permanent fix" isn't so permanent since as I stated, it did nothing for me and others, so I wouldn't exactly call it permanent nor a fix unless it first and foremost actually works for specific individuals.

As it stands my wheel works flawlessly now that I reverted back to 1909 because my PC kept locking up on the newest update.

Rolling back was easy enough for me thankfully because I already had a USB installer created that contained 1909, but rolling back for others who have to make a new installer isn't going to be as easy since they'll have to track down an ISO for 1909 instead of using the Media Creation Tool, because that tool as of right now is updated with 2004.
 
Interesting.
You're the first person I've come across who is on the 2004 update to Windows and using the older hardware with the older v5.10 of the Logitech Gaming Software and is having things work.

Interesting that what you did to make things work for you doesn't work for me or other's that I know of that had this issue.

And this so called "permanent fix" isn't so permanent since as I stated, it did nothing for me and others, so I wouldn't exactly call it permanent nor a fix unless it first and foremost actually works for specific individuals.

As it stands my wheel works flawlessly now that I reverted back to 1909 because my PC kept locking up on the newest update.

Rolling back was easy enough for me thankfully because I already had a USB installer created that contained 1909, but rolling back for others who have to make a new installer isn't going to be as easy since they'll have to track down an ISO for 1909 instead of using the Media Creation Tool, because that tool as of right now is updated with 2004.

Ι completely understand your frustration. It seems that - to some users - there is a conflict between v2004 and older v5.10 LGS.

When i said "permanent solution" i was referring to the fact that my wheel was not calibrating UNTIL a usb stick was inserted.

Anyway, maybe a cumulative update will eventually fix this problem. We just keep our fingers crossed..
 
Ι completely understand your frustration. It seems that - to some users - there is a conflict between v2004 and older v5.10 LGS.

When i said "permanent solution" i was referring to the fact that my wheel was not calibrating UNTIL a usb stick was inserted.

Anyway, maybe a cumulative update will eventually fix this problem. We just keep our fingers crossed..
yeah, hopefully by the time Windows forces the update on me and stops supporting 1909 something will have been changed and it'll work like it should.

But until then I'm gonna stay on1909 now LOL
 
  • Like
Reactions: Haris1977
After three days of searching hi and low on the internet, along with then finally talking to some people over Discord I have discovered the issue with the older Logitech racing wheel's that use the older 5.10 gaming software.

The issue is pretty simple, but a huge pain in the butt and a let down.
The drivers are so old, that they no longer work with GameInput Redistributable in the newest update to Windows 10 v.2004.

If you have the Driving Force GT, G27, or another wheel from the same era that uses the older 5.10 gaming software, and cannot get games to recognize the controller, this is why.

The newest update to Windows has officially borked support for the older hardware, and games that use the old GameInput for supporting said hardware along with the old drivers for this hardware.

I am sad to see this happen and unfortunately there is nothing that can be done unless either Logitech and/or Microsoft decide to do something about it.

I do not know about lost compatibility for other hardware such as ThrustMaster.

But as it stands, the DFGT, Original GT, and G27 (and any other Logitech wheel that uses the old 5.10 version of gaming software as well as potentially other legacy Logitech devices) will no longer work as of right now with the new 2004 update to Windows 10.

I have to buy a different wheel now.

However, if there are any users here that have the DFGT, G27, or any other Logitech wheel that uses the old software, and are running on the latest 2004 update, that DON'T have any issues, and seem to have their wheel's working just fine, please let me know so I can get in touch with you and perhaps maybe discover something that might help us find a personal workaround/fix for getting these older wheels to work.

I was having the same issue with my G29.
My solution was to use the old “Logitech Gaming Software” instead of Ghub. Luckily, it’s still available from the Logitech site.
 
Status
Not open for further replies.