18 SEPTEMBER 2026 - Synapse & Chroma for Windows | Razer Insider
Skip to main content
StickyPatch Notes

18 SEPTEMBER 2026 - Synapse & Chroma for Windows

  • August 11, 2026
  • 42 replies
  • 4829 views
Show first post

42 Replies

  • Romeike
  • Insider Mini
  • September 9, 2026

Unfortunately this patch broke the joystick on the Tartarus v2. The only way to restore function is to disable the software - but of course then you lose your button mappings.

Mine works. Broken how?

 

Unfortunately the directional joystick is now unresponsive. It worked before the release applied and works normally when Synapse is disabled. On starting the Synapse services the joystick no longer works but the mapped buttons work fine.

    THIS update broke the  the Tartarus v2 and many ppl pointed out in the comments and why there is no reply from the support 
    synapse is not fully supporting  the Tartarus v2  u guys need to fix this soon because these updates works well with other keyboards the non d-pad keyboards 
    fix it as soon as possible 

      brentpan
      • brentpan
      • Insider Mini
      • September 9, 2026

      the lighting on my Razer Monitor Stand Chroma is not performing properly after this update. shutting the synapse app makes the light work properly again somehow. please help

      Thermaltake868

      And still after updating to latest synapse on both laptop and PC still same problem. On laptop I have Deathadder V3 Pro on PC V4 Pro. Both machines running Win 11 Pro with latest updates, and both machines act same when shutting down PC. And that is with razer app waiting to be closed for second or two. And you still didn’t manage to fix that after months and months of use.

      Razer.ScarletRouge
      Forum|alt.badge.img

      Hey there, ​@Romeike

      I'm sorry to hear that the recent patch broke the joystick functionality on your Tartarus V2. No worries, I will create a case for you and forward your concern to our Higher Technical Support Team for further investigation and assistance. To proceed, please send me a PM and provide the following details so I can kickstart your case:


      Device’s serial number: 
      Full Name:
      Email address associated with Razer ID:
      Phone number:
      Country:


      Thank you!



      *Thread locked to curb conversation to PM. 

        psolem
        • psolem
        • Insider Mini
        • September 10, 2026

        And again today its broken….. chroma studio has reset my layout and wont save anymore, Visualizer stopped working completely, mouse not detected, freyja not detected…
        Windows updates done, windows restarted, razer apps restarted, razer services restarted, repaired razer apps, reinstalled razer apps… I dont understand what is the actual problem here Razer… Your obviously breaking things.. we obviously need help… hundreds of dollars on devices and hours configuring software and NO HELP from Razer is completely unacceptable… this is ludicrous and should be illegal. I am seriously so tired of spending over an hour trying to get this stuff to work EVERYTIME I turn on my pc… or my wife turns on her pc… or my buddy turns on his pc… its the same story over and over and over...

          • Phoen1x_
          • Insider Mini
          • September 10, 2026

          The recent update seem to have broken my Naga hex v2 a bit as well, so not just peoples Tartarus. 
          The mouse cant seem to use the top buttons in front of the scroll wheel as mouse 4/5 anymore. Even tho they are set to those buttons in synapse, they use their default dpi up/down function. 

          Binding the buttons to left/right click seem to work, and some other random binds i tried, but mouse 4/5 does not work for some reason, which is quite annoying. Tried reinstalling synapse, restarting the pc, plugging into different usb ports, reset mouse to factory settings, create new profiles ect. Nothing seems to work.

          I do have a razer naga pro, and mouse 4/5 works fine on that, so of all my devices the naga hex v2 is the only one with any issues ive noticed.

            BlueLagoongeotools555

            How incompetent do you have to be to release an update that breaks so many things? It’s as if you don’t even test your own updates. The QA team should have been fired already.

              How incompetent do you have to be to release an update that breaks so many things? It’s as if you don’t even test your own updates. The QA team should have been fired already.

              At this rate, an unfinished Synapse 5 will be out before anything in Synapse 4 will be fixed.

                uli2258
                • uli2258
                • Insider Mini
                • September 12, 2026

                A workaround I got suggested by Copilot: Switch your d-pad mode to 8-way, map the directions manually to keyboard navigation up/down/left/right, and disable the diagonals. That worked for me. I don’t know if that works for people having issues with the pad in 8-way mode, though.

                Hi again,

                Did we actually get an update today? I see the patch note has today’s date but it still says July 31st on the build number. Also, no signs of an update process.

                Looks like the D-Pads on the Tartarus’ are being addressed but there is still nothing on the “keymap switching delay” and “keymap overwriting” bug. Please prioritize this Razer.

                brentpan
                • brentpan
                • Insider Mini
                • September 14, 2026

                the lighting on my Razer Monitor Stand Chroma is not performing properly after this update. shutting the synapse app makes the light work properly again somehow. please help

                 

                no fix on the latest update 

                • HULSMANS
                • Insider Mini
                • September 15, 2026

                My Tartus v2 stopped working after this update. It says the mappings I have need Synapse 4 installed, which it is. I tried repair, I tried uninstalling, restarting, and reinstalling. Nothing. I use it for work as well as games, so this is killing my workflow.

                My Tartarus V2 is no longer detected in the Synapse software. It is useless now.

                brentpan
                • brentpan
                • Insider Mini
                • September 18, 2026

                the lighting on my Razer Monitor Stand Chroma is not performing properly after this update. shutting the synapse app makes the light work properly again somehow. please help

                 

                no fix on the latest update 

                STILL NOT FIXED

                 

                • kazuxxxx
                • Insider Mini
                • September 19, 2026

                Macro key names show as raw numbers after IMPORT - still broken on V4.0.86.2609100850

                The 8 September entry lists this as fixed:
                  "Sequence macros reverted key assignments to raw scan codes on app relaunch"

                The relaunch path may be fixed, but the IMPORT path is not.
                V4.0.86.2609100850, Razer Tartarus V2, Windows, Japanese/JIS keyboard.

                Minimal reproduction
                1. Create a new macro and record a few keystrokes - press 1, 2, 3, 4
                   -> the event list correctly shows the key names 1, 2, 3, 4
                2. Restart Synapse
                   -> still correct. The names persist.
                3. Export that macro to XML (Macros > ... > Export)
                4. Delete the macro
                5. Import the XML you just exported, unmodified
                   -> every keyboard row now shows a bare number: 49 50 51 52

                Step 5 uses Synapse's OWN export file with no edits, so this is a clean
                round-trip failure inside the import path.

                49-52 are Windows VIRTUAL-KEY codes (0x31-0x34 = '1'-'4'), not scan codes.
                The scan codes for those keys would be 2, 3, 4, 5. The UI appears to print
                the raw Makecode value from the XML instead of resolving it to a key name.
                The changelog wording says "scan codes", which may be pointing at the
                wrong layer.

                Why this matters
                All of my existing macros went to numbers after the September update -
                presumably the update re-read them through the same code path. Re-recording
                a macro from scratch restores the key names, but re-importing it does not,
                so there is no way to restore a macro from a backup without losing
                readability. With 28 macros of 7-29 rows each, editing one is guesswork -
                there is no way to tell which row is which key.

                The stored data itself is fine: Makecode holds correct values, the sequence
                is intact, and the macros execute correctly in game. Mouse rows are
                unaffected and still read "Left Click". This is display only.

                Already tried, no change
                - Restarting Synapse and the Razer Synapse Service, rebooting
                - Switching the Synapse UI language away and back
                - Checking Windows input languages
                - Repair install, and a clean reinstall after removing
                  C:\ProgramData\Razer\Synapse4 and %LOCALAPPDATA%\Razer\Synapse4

                Happy to supply the exported XML and screenshots.

                 

                • kazuxxxx
                • Insider Mini
                • September 19, 2026

                 

                 

                Correction to my earlier post: import is NOT the trigger.

                I had this wrong. The key names revert to raw numbers on their own, without
                importing anything.

                What actually happens, on V4.0.86.2609100850:

                  - Right after Synapse launches, the macro list shows correct key names.
                  - Later in the same session it shows raw numbers instead.
                  - Importing a macro produces the same result immediately, but that is just
                    one way to trigger it, not the cause.

                I confirmed it is not my data and not one broken install: a second PC, same
                Synapse version, same account, same cloud-synced macros, showed correct key
                names right after launch and then switched to numbers as well. Both machines
                now behave identically.

                So this is the September changelog entry recurring:
                  "Sequence macros reverted key assignments to raw scan codes on app relaunch"
                It is not limited to relaunch.

                What the data looks like once it has reverted - exporting the macro in that
                state gives only:

                  <KeyEvent><Makecode>50</Makecode><State>0</State></KeyEvent>

                with ScanCode, KeyEvent/Type and flag all absent. A macro that still displays
                names correctly carries one of two things:

                  freshly recorded        -> <ScanCode> present (sibling of KeyEvent)
                  added via Keyboard menu -> <Type>Alphanumeric</Type> inside <KeyEvent>

                Re-adding a single row through the Keyboard function menu restores that one
                row's name. Editing the XML does not help - I tried putting <ScanCode> back,
                renaming it lowercase, and adding <Type>Alphanumeric</Type>; an import strips
                all three and keeps only Makecode and State.

                Two details that may help locate it:

                - The internal field is lowercase "scancode". From User Data\Logs\macro5.log:
                    #### create ui item {"Type":1,"KeyEvent":{"Makecode":49,"State":0},
                                         "flag":0,"selected":false,"isPairing":false,"scancode":2}
                  but the exporter writes <ScanCode>. Every other field in the XML matches the
                  internal key name exactly (flag, selected, isPairing).

                - Makecode is not always a Windows virtual-key code. Right Shift records as
                  Makecode 310 with ScanCode 54, i.e. 256 + scancode. That matches the report
                  of "right shift turns into 310" in
                  insider.razer.com/razer-support-45/macros-issues-for-razer-snyapse-4-89812

                Macros still execute correctly. The impact is that long macros become
                impossible to edit, because there is no way to tell which row is which key.

                Razer.ScarletRouge
                Forum|alt.badge.img

                My Tartus v2 stopped working after this update. It says the mappings I have need Synapse 4 installed, which it is. I tried repair, I tried uninstalling, restarting, and reinstalling. Nothing. I use it for work as well as games, so this is killing my workflow.

                My Tartarus V2 is no longer detected in the Synapse software. It is useless now.

                Hey there, ​@HULSMANS 

                Thank you for sharing your concern here. Please try running the Razer Driver Clean-up Tool, and let me know via PM if the issue persists so we can proceed further. Thank you!

                CookiesAccessibility statement