Razer Synapse 2 not seeing Mamba TE *RESOLVED* | Razer Insider

Razer Synapse 2 not seeing Mamba TE *RESOLVED*

  • 29 April 2020
  • 1 reply
  • 2 views

I am having a couple of problems with my mouse and its ability to interface properly with Razer Synapse.

My Razer Mamba TE has worked well and was always able to be seen by Synapse 2 ever since I bought it. Today I received a new Black Widow keyboard and I had to download Razer Synapse 3. Ever since I downloaded Synapse 3, my mouse cannot be seen by either version of Razer Synapse. My computer still sees the mouse just fine. The mouse does function, however I cannot access any of the customization tools through either version of Synapse. The mouse does not even appear on the list of available devices to customize. I am wondering if two different versions of Synapse looking for and possibly supporting the same device is keeping it from being available to be seen by either. I have uninstalled and reinstalled Razer Synapse 2 to try to fix the problem, however that has been ineffective.

This is a small side problem, but the mouse wheel on my Mamba TE will occasionally scroll up when I try to scroll down. I roll the mouse wheel down and for the most part, it scrolls down, but 1/5 times, it scrolls up a little bit before continuing its downward scrolling. This has been a persistent problem for a long time and I am just curious to see if there is anything I can do to fix it.

EDIT: I plugged my Mamba TE into another computer that has Razer Synapse 2 installed and the computer DID see the hardware. This seems to be an issue with Synapse not seeing the hardware on my PC rather than an issue with the hardware itself.

EDIT2: I fixed the issue by uninstalling Razer Synapse 2, then doing a repair on Razer Synapse 3. Once the repair went through, Synapse 3 saw my mouse. Then I reinstalled Synapse 2 in order to manage my legacy hardware. This thread can be closed/deleted

This topic has been closed for comments

1 Reply

Userlevel 7
Thank you for updating your thread. I will be locking this as resolved to prevent hijacking.