Synapse 2.0 and Deathadder Chroma problem | Razer Insider
Skip to main content

Synapse 2.0 and Deathadder Chroma problem

F
Hi there, Synapse 2.0 doesn't seem to recognize my Deathadder Chorma anymore (maybe since one month or so). I tried to uninstall Synapse, to delete every directory named "Razer" and uninstall mouse from the Device Manager but nothing happened. The Device Manager correctly displays both Deathadder Chroma and the BlackWidow Ultimate but Synapse 2.0 shows me only the kewyboard (Blackwidow). Screenshots attached. Any tips? Thanks!
Did this topic help you find an answer to your question?
This topic has been closed for comments

5 Replies

Razer.Caziel
  • Razer.CazielRazer Support
  • I am the Lightbringer
  • 4792 replies
  • April 4, 2020
Do you have another mouse connected? If not, please uninstall the HID mouse driver as it is possible that it is causing communication issues between the DeathAdder Chroma drivers and the app. Shoot me a PM if the problem persists.
F
Razer.Caziel
Do you have another mouse connected? If not, please uninstall the HID mouse driver as it is possible that it is causing communication issues between the DeathAdder Chroma drivers and the app. Shoot me a PM if the problem persists.
Hi! I resolved the problem with iobit Driver Booster. When i downloaded Synapse 2.0 from razer site i got an old version of it. Driver Booster downloaded a recent version of Synapse and now the mouse work properly. Fun fact: when i tried to "update" form Synapse (before Driver Booster solution) i had "the software is up to date". Now i run the 2.21 ver.
Razer.Caziel
  • Razer.CazielRazer Support
  • I am the Lightbringer
  • 4792 replies
  • April 4, 2020
@firstLimeGreenheat668 Thanks for sharing the fix you found! If I may ask, do you remember what the build number of your operating system was when you encountered the problem? I'd like to try to recreate this myself, so I can verify if it works on different systems.
F
Razer.Caziel
@firstLimeGreenheat668 Thanks for sharing the fix you found! If I may ask, do you remember what the build number of your operating system was when you encountered the problem? I'd like to try to recreate this myself, so I can verify if it works on different systems.
sure! Win 10 Pro v. 1909 (17/03/2020) SO build 18363.720
Razer.Caziel
1 person likes this
  • Razer.Caziel
    Razer.Caziel
Razer.Caziel
  • Razer.CazielRazer Support
  • I am the Lightbringer
  • 4792 replies
  • April 7, 2020
I'll be working on this. Thanks again for updating the thread. PM me if you need assistance with anything, but for now, I am locking this thread to prevent hijacking.
CookiesCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings