Tartus v2 and Synapse 4 issue with Sept 2026 update

Having the same issue. Was playing Skyrim the other day, and all of a sudden my bindings wouldnt work. I have done the clean install, repairs, admin permissions, formats, resets, duck I even bought a new/used Tartarus v2!!! (To be fair my other one was 5 years old) Still refuses to let me change binds. I even created a new RazerID just in case!  I really hope they fix this soon

Welcome to the Club, I had to restore an OS image with Macrium Reflect from 1 week ago which had the older version of Synaspe before the sept Update to get it working again. 

Anything come of this? still broken here

I saw I had updated yesterday, but it was still broken for me.  I tried it again today just about an hour ago and suddenly the d-pad on my Tartarus v2 is working once again - and so are my keybinds.  Fingers crossed it stays that way.

I have been able to restore functionality after working with Razer Support. I had to follow these steps *exactly* to get it to work, so I can only assume it was something in the driver code itself that glitched out.

The following is from the last email I received and was able to restore functionality with.

2. Driver Cleanup Tools in sequence. 

 

We understand that you have previously attempted to use the Driver Cleanup Tools. However, we recommend trying the following alternative steps. Please ensure that each step is followed carefully and in sequence to achieve the best results.

1. Uninstall Synapse and Chroma (ensure both are uninstalled, not just one): How to uninstall Razer Synapse 4 from your Windows PC or laptop
2. Run the latest driver clean-up tool: https://rzr.to/igxb6b 
3. Restart your PC.
4. Download and install Synapse 4 from our support page: Razer Synapse 4: Advanced Device Control and Lighting Software 
5. Launch Synapse 4, then restart your PC again after the driver is installed via Synapse, and test the functionality.

Sorry, it still doesn’t work… unfortunately! 😩

Did a install of Synapse on another SSD with Windows 10 that never has had Synapse. Still the problem exsists.

What do you mean? I use Tartarus pro without Synapse. It's half a keyboard the odd button is alt and the dpad is up down left right. 20 is spacebar. Works great. The only thing I did in Synapse was make the scroll wheel volume control. Scroll click was T. 

I meant i installed Synapse for the first time on another OS/HDD and still the same issues with the software.

Hey Razer, the Tartarus V2 is still broken.. any ETA when we can use it again??
 

I hit the "keymaps show correctly but only default keys come out" problem,
found the cause in the logs, and recovered from it. Posting both.

V4.0.86.2609100850, Tartarus V2, direct USB (no KVM/hub).

Cause, from User Data\Logs\mapping_engine.log:

  02:12:04  addUsbDevice     guid c9ec4d75...   OK
  02:13:24  removeUsbDevice  guid c9ec4d75...
  02:13:42  enableInputRedirectCompleted:
              device_info[{"vendorId":5426,"productId":555,
                           "guid":"c9ec4d75..."}]
              error_reason[device not found]
            ... repeating for the next 56 minutes

The device was removed at 02:13:24 and addUsbDevice never fired again. The
app kept running for another hour calling enableInputRedirect against the
removed device. enableInputRedirect is what diverts the keypad's input to
your mappings, so with it failing the keypad just emits its default keys -
while the UI, which keeps its own device list, still shows everything as
configured and lets you edit it.

That is why reassigning does nothing: the assignment is saved fine, the
redirect is what never turns on.

Recovery that worked for me:

  1. Quit Synapse completely from the system tray (closing the window is not
     enough, it stays resident)
  2. Unplug the keypad, wait ~10 seconds, plug it back in
  3. Let Windows enumerate it, THEN start Synapse

Order matters - device first, app second. Keymaps and macros both work again.

In my log every earlier Synapse restart produced a successful addUsbDevice,
so the app recovers fine when it starts with the device already present. The
bug is that it does not re-add the device after a removal while running.

If it happens to you, that log file is worth checking before reinstalling
anything - a driver cleanup or reinstall would not have fixed this.

Windows key+x > Device Manger > Human Interface Devices > remove Tartarus or effected device and its duplicates. Restart computer then re install synapse over itself to force newest hardware drivers. DoNot uninstall first.

I hit the "keymaps show correctly but only default keys come out" problem,
found the cause in the logs, and recovered from it. Posting both.

V4.0.86.2609100850, Tartarus V2, direct USB (no KVM/hub).

Cause, from User Data\Logs\mapping_engine.log:

  02:12:04  addUsbDevice     guid c9ec4d75...   OK
  02:13:24  removeUsbDevice  guid c9ec4d75...
  02:13:42  enableInputRedirectCompleted:
              device_info[{"vendorId":5426,"productId":555,
                   "guid":"c9ec4d75..."}]
              error_reason[device not found]
            ... repeating for the next 56 minutes

The device was removed at 02:13:24 and addUsbDevice never fired again. The
app kept running for another hour calling enableInputRedirect against the
removed device. enableInputRedirect is what diverts the keypad's input to
your mappings, so with it failing the keypad just emits its default keys -
while the UI, which keeps its own device list, still shows everything as
configured and lets you edit it.

That is why reassigning does nothing: the assignment is saved fine, the
redirect is what never turns on.

Recovery that worked for me:

  1. Quit Synapse completely from the system tray (closing the window is not
     enough, it stays resident)
  2. Unplug the keypad, wait ~10 seconds, plug it back in
  3. Let Windows enumerate it, THEN start Synapse4

Order matters - device first, app second. Keymaps and macros both work again.

In my log every earlier Synapse restart produced a successful addUsbDevice,
so the app recovers fine when it starts with the device already present. The
bug is that it does not re-add the device after a removal while running.

If it happens to you, that log file is worth checking before reinstalling
anything - a driver cleanup or reinstall would not have fixed this.

Why does Razer refuse to officially acknowledge this issue they caused. I find it very disrespecting towards their paying customers. Oh look, they just happen to release a Nex Gen Tartarus V2 pro, days after this fiasco.

Seriously it would be nice for them to make a statement regarding the issue and if their is a fix in the works.