Synapse 2.0 Incompatible with Windows 2004 Update | Razer Insider

Synapse 2.0 Incompatible with Windows 2004 Update

  • 5 August 2020
  • 5 replies
  • 15 views

I've tried multiple clean installs, device driver sweeps, and I found something that might be helpful for support. Version 2.0.29.2 RazerSurround works. However if Synapse 2.0 is updated to the current version, the audio immediately becomes crackly and broken. Unfortunately using version 2.0.29.2 of razersurround on its own leaves out having macro options for my legacy software. However if you use default macro settings then this will fix RazerSurround for you.

I'm asking support for help with this. Is there a way to stop Synapse 2.0 from auto updating every time I install? Is there a way to rollback the version similar to graphics card drivers? Is there an ETA on when we will be able to use razer surround again and when will we see Synapse 3.0 support for legacy devices? I know this is subjective but considering we're using the oldest hardware we are probably some of your most loyal customers, but I feel left in the dirt.

TLDR; old version of razersurround works on its own but when you add synapse 2.0 with updates it breaks. I know I can roll back to 1909 but would hope there's a better solution.

This topic has been closed for comments

5 Replies

Userlevel 7
You can opt to go offline on Synapse 2.0 to stop automatic updates, but I highly recommend rolling back to 1909 if you can. Do note that legacy devices were designed for an older architecture so most of them will probably not work with Synapse 3.0.
Have you figured out a fix?

Edit:

How do you use surround on its own? I'm trying to get it to work without all the cracking sounds but I can't figure it out. I don't need synapse but I also don't know how I can use surround without it.
Userlevel 7
No, there is no fix for this yet, and you need to have Synapse installed before you can install the legacy surround sound.
I just had to revert back to windows 1909. I hope you and windows are able to work out a fix for it, or, hopefully, its fixed in the next windows patch.
Userlevel 7
Amazonitedatathink348
I just had to revert back to windows 1909. I hope you and windows are able to work out a fix for it, or, hopefully, its fixed in the next windows patch.

Did you notice any sort of improvement after reverting to version 1909? If the problem persists, even after doing so, please send me a PM so I can help you further isolate the issue. *Locking the thread to curb conversations to PMs.