Logitech F710 drivers not migrating to new version of Windows 10, why not?

So while in Dinput, LGS does recognise the F710 as a wireless controller, but wrong model, and Windows recognises it as a Xinput/XBOX 360

controller when you switch to Xinput, but both fail to function properly in games ?

Still seems familiar to the wireless struggle I had with this controller, but if you are having problems with keyboard/mouse as well

I wonder if the source of the problem is the USB drivers ?

Are you able to open the LGS software with the the Rumblepad 2 connected, or does the R stick fail to move the mouse cursor ?

If you are able to hold the mouse cursor in place and open LGS to Properties, do the  buttons and left stick function ?

If so, the problem with the stick is probably mechanical, and the software is working properly.

• I've used two versions of the mouse and keyboard profiling software with Win10, but will probably stay with v 8.92.67 for a few years.

I've not had any problems on Win10 with this, or the previous version of the Logi gaming software, with my mouse, keyboard and G13.

The new LGS software drivers would be signed, but I have no idea if the LGS 510 driver is signed. I haven't had any problem installing

either of the LGS software versions on Win10, so I guess it must be.

• I just went to Programs and Features to uninstall/reinstall the LGS 510 so my G27 would be correctly identified again and was reminded

I don't have to reboot. Just uninstall and reinstall. I also have to disconnect my G13 key/controller.

(if the G27 gets disconnected longer than an as yet unidentified time of say a day or two, it gets lost).

While in P&F saw another entry below LGS 8.92, with the title 'Logitech Profiler' .When I went to use my LGS 510 installer I discovered I do have a Win10 hot fix for the G27 wheel (possibly entry three in P&F).

Judging by the Read Me it  may be coded specifically for the G27 so may not help you directly, but you may still get some useful

information downloading it for a look anyway. There may be a fix for G25 and maybe Momo out there somewhere as well ?

This fix also uses the Device Manager install option. You Browse to the location you put his files and .msi in and install from there.

I seem to recall doing the same thing with the XBOX drivers when trying to get the F710 wireless fully functional, but I don't know if

I installed XBOX software manually and then located it via Device Manager after it didn't function properly, or if I extracted the files

from the installer to a folder and then Browsed to them from Device Manager, as with the Logi wheel hot fix.

The only link I have is from his Read Me to a direct download if you want to check it out. I expect I got it from the Logi forums originally.

https://mega.nz/#F!LQ9gmBQT!uijjT3dyinNLUgb9mbhCLg

• A bit lazy of Logi not to include at least the G25/27 in the newer LGS with the G29 and newer wheels, I reckon.

.

Hi BossDweeb, thanks for your reply.

I never had a single issue with Windows 7 64 bit, so far the best and most efficient version of Windows to date(IMO). I also used to have XP 64bit (in dual boot) which never took off for some reason, getting drivers and software to run then was certainly problematic! Then Vista x64. So anyway I've been using Logitechs x64 drivers for some time now and mainly had issues with their keyboard drivers and sometimes mice, I still have a Rumblepad 2 controller but it makes the mouse cursor go all the way to the left of screen when it's plugged in now (just tried it out).

Ok, when the F710 is installed as an Xbox Controller, yes it works as far as it tells me in Device Manager "This device is working properly" but still has the exact same issue; drivers not migrated listed in events.

What you were describing when selecting the drivers yourself when in device manager, that's what I meant by manually installing via the update driver tab, I think of auto as let Windows find it for me, but as it won't so manual is the only way. That function also doesn't work like it used to in previous versions of Windows, there is no option to add a game controller like previously only Xbox and Logitech is limited to a driver set from the mid/early 2000s and pretty much only for steering wheels there were 3 options. None of those were for yours either btw, and I'm dreading getting my Logitech wheel out to try and install that now. Selecting the correct driver which was installed with the x64 package, it selected it but won't migrate or utilise it.

Is driver signing really the issue?

The F710 has, or can have, some issues with the drivers due, I believe, to the wireless setup. I tried an F710 (I may have still been on

Win7 at the time too ? ) but settled on the F310 (not because of the driver issue) which is still working well on Win10 v1803.

• Have you reinstalled the Microsoft XBOX 360 Accessories software since reinstalling Windows ?

Xbox 360 Controller for Windows | Microsoft Hardware

I struggled (drove me half mad actually) with this when trying the 710, and found I had to use a round about method of

installing/reinstalling  the XBOX 360 driver via Device Manager, even though the install of the downloaded XBOX software

seemed to complete. This sounds a bit like what you described.

I don't recall the details, but basically you have to use Device Manager with the option to select the driver yourself

(from where, if I remember correctly, you basically reinstall the same software driver again ).

You should be able to find full details on the Logitech forums.

community.logitech.com/s/topic g-controllers

• My F310 gets reported as Dual Action USB when in D-input mode, but it doesn't affect the functions or profiles

(most of which go back to earlier model Logi controllers). I hadn't really focused on the name until now because the controller

functions properly.

I don't recall if the F710 was reported correctly after I got the wireless bit sorted out either, but the controller and profiles, etc worked.

Good chance it was also reported as an older wireless controller ? Logi may not have updated anything they didn't need to

when releasing the 64bit version, so the software may know about the F series ?

But when my G27 wheel gets reported as a Drive Force, or some such model, there are problems as the configuration of

the Drive Force is considerably different.  When this happens I have to uninstall and reinstall the LGS510.

(need to reboot, but no permissions or other problems, thankfully).

This shouldn't be a problem with the F710 if the wireless connection is functioning properly as the button configuration is

the same as the F310, and the earlier controllers.

btw - vibration does not work on Logi controllers with a lot of games that do vibrate when using an XBOX controller.

.

Hi Andre, and thank you for your reply.

I understand where you're going with that option, but ultimately that isn't a solution or fix it's only a band-aid for a clearly much broader issue within the framework of Windows 10. It's a inf file, no more than a simple text based instruction for how Windows should view/handle it if it was fine before, why isn't it now?

Logitech have not changed the installer or drivers since the 8th of March 2016 (digitally signed then). That driver-set affects a great deal of their hardware new and old.

Also, I won't be downloading Windows from anywhere other than Microsoft. Given the endless loop of updates and security patches, I would eventually no longer be able to do so via the update panel. Microsoft has planned this system to be identical on every PC globally, and most of my PC work is based online. It just won't work.

I am going to recommend you downgrade to Windows 10 1703.

Yes, not the best news you want to hear. These feature updates are not thoroughly engineered and are rushed mostly to meet deadlines. They have become highly unnecessary in some instances. My opinion, focus on the apps and less on having the latest version of Windows. If your apps are working fine and you are getting your work done, minimize your need to jump on the latest release.

Now, get ready to go back to your previous version. I recommend Windows 10 1703 because its the most stable and efficient release to date.

Step 1: Go to another working computer with Internet access, download Windows 10 1703 from the following link:

https://tb.rg-adguard.net/index.php?sid=74a7cf5...

Choose the following:

• Windows Final
• Windows 10, version 1703
• Windows 10 Pro + Home
• English
• x64 (64 bit) x32 (32 bit)

Step 2: create a bootable copy

https://answers.microsoft.com/en-us/windows/wik...

Step 3: perform a custom install

http://answers.microsoft.com/en-us/insider/wiki...

Step 4: how to recover your files from Windows.old:

https://answers.microsoft.com/en-us/windows/for...

Windows Update might attempt to upgrade to Windows 10 1803 again. See instructions how to block it:

https://www.groovypost.com/howto/block-windows-...

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.