Latest update to Synapse completely broke it | Razer Insider
Question

Latest update to Synapse completely broke it

  • 18 September 2023
  • 4 replies
  • 668 views

Userlevel 1

The latest update 20230915 completely broke Synapse for me. I can't even see it on my taskbar or start menu. It's still running in the background under task manager. I still see the install files for it in file explorer. It just won't open at all. All my Razer devices are not in LED sync and my settings are inaccessible.

So far I have tried repairing Synapse through the installer directly and it didn't fix anything. Next step is to uninstall Synapse and do a fresh install. I've had Synapse for over 2 years on my PC and never had any problems at all. Anyone else been experiencing this issue recently?? Any help would be appreciated or just letting Razer know this issue exist would be nice.


4 Replies

Userlevel 1

Update: I just finished completely uninstalling and reinstalling Synapse. Even removing any traces of Razer under programs files and deleting any existing drivers left over. It still isn’t opening. I can’t see it under my taskbar and start menu even though it’s still running under task manager. It has to be either something wrong with the latest Synapse update or a Windows update somehow broke Synapse. I updated Windows at the same time as Synapse on Friday 9/15 when the new update released. Seriously nobody else is having this issue?? I can’t be the only one, seeing as I have spent the last 2 days troubleshooting this and removing everything Razer related on my PC.

Yap, I have the same problem and it happened in the same way.

I solved it. Use Revo Uninstaller Pro and do a forced uninstall.

I’ve been having issues with Synapse 3 since around the same time as you. It seemed to go sideways for me around the time of the Windows 11 23H2 update. But it could have also been the update to synapse, or maybe Cortex. It all happened around the same time for me.

 

At first, Synapse wasn’t starting when launching Windows. Then recently it stopped detecting my laptop (Blade 16). At this time, I followed the steps laid out in this Reddit thread: https://www.reddit.com/r/razer/comments/4hyqog/synapse_not_detecting_anything/

 

Below is the comment (not mine) that helped:

 

I have just fixed my issue thanks to Razer support, here's the instructions I was given. Hopefully it helps you!

What you described sound like a common driver conflict issue, as the system uses a different driver, causing Synapse to not recognise it.

Please kindly uninstall both Razer Synapse and Razer Core from your PC and delete all files in C:\Program Files (x86)\Razer and C:\ProgramData\Razer directories. These folders are hidden by default, so please be sure to unhide them. We want to ensure that there are no residual files remaining that may corrupt your installation. This is important so please kindly do so. Restart your computer afterwards.

Go into device manager, go to Keyboards/Audio inputs and outputs/Mouse and other pointing devices, uninstall HID Keyboard/Mouse Drivers and all other Razer product drivers, and restart your PC. Be sure to select delete drivers as well when uninstalling. Restart your computer again.

Turn off all Firewall and Anti-virus software to prevent any conflicts. Then, install the latest version of Razer Synapse

Please do not reuse a previously downloaded version of the Synapse installer. Please kindly redownload and reinstall Synapse.

The main key for me, which I had not fully tried before, was to uninstall ALL HID Keyboard and Mouse drivers in Device Manager, not just the Razer device.

When I restarted my PC, it popped up with a prompt to install the Razer software - I think this is another red herring!!! This popped up for me when I was setting up Windows originally, but this time I ignored it and made sure to install the latest Synapse software instead.

 

This seems to have partially resolved the issue, in that Synapse 3 is now detecting my laptop (for now). It’s still not loading at startup though, so that will require more troubleshooting. If I figure anything out, I will report back.

 

Wanted to share because this issue seems somewhat common, but there is a shortage of working fixes that I have been able to find thus far.

Reply