This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Update 39.0.3 disabled programmable keys on Logitech G700s mouse . . . How to get them back?

  • 1 tontu
  • 3 am na jafe-jafe bii
  • 5 views
  • i mujjee tontu mooy ttii

more options

The G700s provides customized buttons collected in a profile pertaining to a specified application . . . My profile for for T-bird works . . . as well as those for wordprocessing and even windows explorer . . . and the Firefox one worked too, until this latest update.

I've already deleted and re-written the profile, uninstalled and reinstalled the mouse software . . . to no avail.

The same mouse and software still work on my other computer, which has not updated to 39.0.3. Mainly I assigned keyboard shortcuts -- CTRL-W to close a tab, "middle click" to open in a new tab -- nothing elaborate, just to have control of the screen from the mouse in one hand.

Any one know what the update did to disable them?
The G700s provides customized buttons collected in a profile pertaining to a specified application . . . My profile for for T-bird works . . . as well as those for wordprocessing and even windows explorer . . . and the Firefox one worked too, until this latest update. I've already deleted and re-written the profile, uninstalled and reinstalled the mouse software . . . to no avail. The same mouse and software still work on my other computer, which has not updated to 39.0.3. Mainly I assigned keyboard shortcuts -- CTRL-W to close a tab, "middle click" to open in a new tab -- nothing elaborate, just to have control of the screen from the mouse in one hand. Any one know what the update did to disable them?

All Replies (1)

more options

This may have been cured in update 40.0. Has anybody else found relief?