Logitech F710 on Windows 10 May 2020 Update (2004)

Anonymous
2020-05-29T07:38:27+00:00

After updating to Windows 10 May 2020 Update (2004), my Logitech F710 Stopped working.

The workaround on installing it as Xbox Controller, which worked for the previous Windows versions does not seem to work anymore.

After trying to install it as Xbox controller it stays as "Wireless Gamepad F710" under "Other devices"

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2020-07-06T19:09:40+00:00

Hi,

I tried all hints described in this thread without luck - F710 refused to work on my gaming PC.

As a last resort I plugged in wireless adapter into my HP laptop (also running Win10 2004) and to my surprise it was detected correctly.

Comparing registry entries I noticed that key Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\046DC21F0305 contains only 1 REG_BINARY value on my PC (osvc: 00 00) while on HP laptop there are 2 REG_BINARY values:

osvc: 01 90

SkipContainerIdQuery: 01 00

From device manager I removed "Wireless Gamepad F710" device, unplugged wireless receiver, restarted PC. When it started I set the values of the above key as on my HP laptop.

After wireless receiver was plugged in it was detected correctly:

This was the only change I had to do.

Was this answer helpful?

300+ people found this answer helpful.
0 comments

106 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-07-01T14:00:08+00:00

    Yeah it doesn't work mate. Device manager reports a Code 19 error. You sure you're running Win 10 2004? Maybe it works for older versions.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-06-29T01:49:22+00:00

    Are you sure that you have modified registry correctly?

    You only need to add those 4 values, others are created by windows before or add/modify by windows after setup completed.

    Also, '61B2908B' should be unique for each F710. Make sure you check out yours first.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-06-28T21:01:50+00:00

    Found a workaround that dosen't need to mess around Windows.

    1. Connect the F710 with x-input mode.
    2. Open the 'Device Manager'.
    3. Find out 'Wireless Gamepad F710' and open the 'Properties' dialog.
    4. Switch to 'Details' tab, check out the value of 'Device instance path' property. It should be something like 'USB\VID_046D&PID_C21F\61B2908B'.
    5. Run the "Registry Editor'.
    6. Open key 'Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_046D&PID_C21F\61B2908B'.
    7. Add 4 string values as below(name : value)
      • ClassGUID : {d61ca365-5af4-4486-998b-9db4734c6ca3}
      • Driver : {d61ca365-5af4-4486-998b-9db4734c6ca3}\0000
      • Mfg : @xusb22.inf,%msft%;Microsoft
      • Service : xusb22
    8. Disconnect and reconnect the F710.
    9. Wait for the setup.

    If everything had been done correctly, the F710 should appear in 'Devices and  Printers' as a game controller and works just fine.

    Device Manager then says the configuration information in the registry is incomplete or damaged.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-06-27T07:03:06+00:00

    Direct input mode don't need any driver.

    Just switch to D mode then connect the F710 and never switch to X mode when connecting.

    My purpose was getting F710 to work in x-input mode by force OS to use Xbox 360 game pad driver,

    since direct input was not supported by most of new games and F710 is way better than many common Xbox one game pad.

    Was this answer helpful?

    0 comments