F keys stopped working after update

[Kovoet]

After getting my new Logitech G502x plus mouse I updated my software. But now found out since the update my F keys have stored working. I cannot get them to work and I have uninstalled and reinstalled, still no joy.
And ideas guys

 

[mclaren85]

Will you re-flash the mouse please?

 

[Bill_Bright]

"Re-flash the mouse"? Ummm, flashing is a "firmware" update term. And the OP said he already uninstalled and reinstalled the drivers. Also, F-keys are a keyboard function so not sure what they have to do with the mouse.

@Kovoet - we really need more information. Is this the computer listed in your computer specs? And did you reinstall the drivers for the keyboard?

You might also try a “cold” reboot. By “cold”, I mean shut down the computer and flip the master power switch on the back of the power supply (if your supply has one) to off (or “O”), or unplug the power supply from the wall for about 15 seconds. Then turn the master power switch to on (or “|”), or reconnect the power cable and boot up and see what happens. By totally removing power, you reset the PSU. It also removes the +5Vsb standby voltage all ATX Form Factor power supplies are required to supply whenever the power supply is plugged into the wall and (if applicable) the master power switch is set to on. This standby voltage is distributed throughout several points on the motherboard, including RAM for faster boots, and the USB ports too. This also keeps alive several features, including “wake on keyboard” and “wake on mouse”, and the network interface for “Wake on LAN” commands. A cold reboot ensures any device settings that may be held by the standby voltage are released, then reset when power is restored.

 

[Deleted member 185158]

Couple things to try.
Uninstall GHub.
Or use GHub to alter the Function key, called FN key inversion.

 

[skizzo]

so your F key has died? if only there was a key to press that would pay respect to that......

F

 

[Kovoet]

I use a logitech G915 tkl and windows 10. It only happened when I updated the logitech driver. What I did today was uninstall the drivers and found the older version of the driver and it is now working. I thought I did something wrong.
It only updated the driver when I started using the new mouse. I usually only use logitech mice and keyboard because I have always liked the software. Not this time but it's all the RGB which is causing the trouble.

 

[Bill_Bright]

I am glad you were able to sort this out and thanks for posting back with your solution. That may very well help someone else who encounters the same problem.

I would keep an eye on the Logitech site for yet another updated driver. If none appears soon, now that you know how to resolve this, you might try again. It could have just been a fluke the first time around.

That said, my typical philosophy when it comes to driver updates is, "If it ain't broke, don't fix it!" That is, I don't update my drivers just because a new one is out there. If my hardware is working fine, I don't update unless the readme/change log for the new driver indicates it fixes a problem I am having, or addresses a security issue I might have.

The above is particularly true for basic hardware devices (keyboards, mice, drives, monitors) because they all must comply with basic industry standards and Windows native drivers know how to do that very well. Manufacturer specific drivers simply add support for extra, non-standard, features - such a RGB.

The only possible exception for me, is graphics drivers. I tend to keep those pretty current.

This same philosophy, btw, applies to motherboard BIOS updates. Except, sometimes, for brand new motherboard models just released by the maker, typical BIOS firmware is very stable and bug free. New BIOS versions that come out after the motherboard leaves the factory typically just add support for new CPUs and other devices released after the board left the factory. If I don't need that support, no need to flash the BIOS - a task that always comes with risks.