30 MARCH 2026 - Synapse & Chroma for Windows

Has the issue of switching to this new Synapse resulting in the DELETION OF GPU DRIVERS been addressed?? You’d think that would be at the top of the list, because a program that affects mice, keyboards and headsets shouldn’t even glance in a GPU’s direction, much less render a pc inoperable!

Hi, just found this thread! I can confirm this issue and will be contributing other issues I have found.

bbbb

I can not duplicate this. Try refreshing drivers then I have also found changing the power options in Synapse 4 then set back to desired times can reset this. Also check under calibration. if nothing stands out try changing the cutoff distance and return to desired distance. I have found this reset to only need to be done once. I saw this happen to Naga v2 pro at one point. It has been good since.

I found changes in how this device reacts to different app volumes being adjusted from Windows Volume mixer. It has created an undesired effect of having low A2H by no longer seeing apps at full volume to the haptics service regardless of the listening volume.

Any more details? I have a very large set and am not experiencing anything similar that stands out.

Great to finally have release notes, both here and in the app. It was so frustrating to be told that a bug would be fixed in a future release, but they couldn’t say when, and there would be no notification when/if it happened.

So long overdue but very welcome. 👍

I also just found switching audio devices can make this come back.

Nope. Worked once. Still dropping out at some point.

I am curious about this device. What kind of issues? I have one from another brand and occasionally it will stop making changes to Windows volume mixer.  They tried to fix it at one point but it still happens. Curious if this and Freyja issues are a Windows problem. 

I had a situation tonight where I noticed Freyja not responding and I tried adjusting volumes and that volume controller didn't work either. When you open the app for either device they respond to changes but do not apply them. The solution for both was to restart the app. This Windows volume mixer not responding to changes issue goes back more than a year. I sure hope someone can find this useful.

Tartarus V2 has become a must have peripheral device for me now and not just for gaming, either. 

Excellent work on the interface for it with the Synapse software updates as well for a Windows 11 Professional based workstation.

Thank you for your reply and for sharing your experience.

In my case, the issue seems different from a volume mixer sync problem.

My Razer Audio Mixer is detected in Synapse 4, but it always shows this error:
“Unable to load Audio Drivers. We recommended removing and re-plugging the device.”

Because of this, the Audio Mixer is still completely unusable.
This is not just a case where volume changes are not being applied — the device cannot function properly at all because the audio driver fails to load.

I have already tried reconnecting the device multiple times, restarting Synapse, restarting my PC, using different USB ports, and trying different cables, but nothing has fixed it.

I previously posted the full details here:
https://insider.razer.com/razer-support-45/razer-audio-mixer-not-working-unable-to-load-audio-drivers-even-after-reconnecting-86964

So while it may possibly be related to Windows or Synapse, the main issue in my case is that the Audio Mixer driver does not load at all.

If anyone from the Razer team or support team sees this, I would really appreciate it if you could look into this issue.
Thank you.

I think I’ve found the issue. the issue is with 

HapticService

"C:\Program Files (x86)\Interhaptics\HapticService\HapticService.exe"

the vibration suddenly stopped working totally, without restarting computer, restarting chroma,synapse 4  , everything I can.  even closing all the razer services running through taskmanager until there was none, still nothing worked.  only after I ran chroma  and then enabled back the HapticService, I Got the vibration back.  the HapticService control the vibration, and it seems like it stop working for some reason. I will move this forward to razer 

Try first to disable/enable the HapticService for me it didn’t want to stop as it was stuck and being used but not really working, only after I end task it through taskmanager and enable it back everything started working immediately 

So it seems our issue is something causing the haptiservice.exe to crash, if it’s the service issue, something with chroma software or some kind of windows issue.  could be even Chroma RGB.

Everyone report to their DISCORD channel they are the developers ! the more log the faster they will fix this! they are the creators of interhaptics

https://discord.com/invite/93jU9nAX4f

Interhaptics SDK - Revolutionary Haptic Technology for Gaming | WYVRN Technologies

You can see why it stop working

[code]

uencyResonance":45}]},"StreamCharacteristics":{"Bands":2,"Points":2,"Transients":2}},{"Perception":1,"BodypartID":226,"Characteristics":{"Resolution":{"Height":1,"Angle":1,"Offset":0,"AllEqual":1},"ValueReport":[{"ActuatorType":2,"Height":0,"Theta":0,"FrequencyMin":25,"FrequencyMax":200,"FrequencyResonance":45}]},"StreamCharacteristics":{"Bands":2,"Points":2,"Transients":2}}]}"
[2026-04-17 14:47:58.112][5340] [RzInterHaptics.RpcClient] [warning] RpcClient::RpcPing failed, exception code: 1717 (RPC_S_UNKNOWN_IF)
[2026-04-17 14:47:58.308][5340] [RzInterHaptics.RpcClient] [warning] RpcClient::RpcPing failed, exception code: 1726 (RPC_S_CALL_FAILED)
[2026-04-17 14:47:58.317][5340] [RzInterHaptics.RpcClient] [warning] RpcClient::RpcPing failed, exception code: 1722 (RPC_S_SERVER_UNAVAILABLE)
[2026-04-17 14:47:58.317][5340] [RzInterHaptics.RpcClient] [warning] RpcClient::StartServerDetectThread begin join
[2026-04-17 14:47:58.317][5340] [RzInterHaptics.RpcClient] [info] RpcClient::StartServerDetectThread::<lambda_1>::operator () create sync event to wait server
[2026-04-17 16:07:15.811][22356] [RzInterHaptics.RpcClient] [info] 
[/code]

[code]

[2026-04-16 05:17:46.630][5340] [RzInterHaptics.RpcClient] [info] DLL version: 1.0.0.5
[2026-04-16 05:17:46.630][5340] [RzInterHaptics.RpcClient] [info] Establishing connection to RzInterHaptics RPC with session "TestSession"
[2026-04-16 05:17:46.632][5340] [RzInterHaptics.RpcClient] [warning] RpcClient::RpcPing failed, exception code: 1722 (RPC_S_SERVER_UNAVAILABLE)
[2026-04-16 05:17:46.632][5340] [RzInterHaptics.RpcClient] [error] RpcClient::GetAllDeviceIDs failed, hr: -2147467259
[2026-04-16 05:17:46.632][5340] [RzInterHaptics.RpcClient] [info] RpcClient::StartServerDetectThread::<lambda_1>::operator () create sync event to wait server
[2026-04-16 05:17:46.637][5340] [RzInterHaptics.RpcClient] [error] RpcClient::GetAllDeviceIDs failed, hr: -2147467259
[2026-04-16 05:18:04.869][5340] [RzInterHaptics.RpcClient] [info] RpcClient::StartServerDetectThread::<lambda_1>::operator () wait result: 0
[2026-04-16 05:18:04.871][5340] [RzInterHaptics.RpcClient] [info] InterHaptics app successfully registered "C:\Program Files (x86)\Interhaptics\HapticService\HapticService.exe"
[2026-04-16 05:18:09.382][5340] [RzInterHaptics.RpcClient] [info] DeviceAdded "3909-{cbb87b7f-67c4-53ee-986d-127f84cff70b}"
[2026-04-16 05:18:09.382][5340] [RzInterHaptics.RpcClient] [info] RpcClient::GetMetadata deviceID: "3909-{cbb87b7f-67c4-53ee-986d-127f84cff70b}", metadata: "{"DeviceName":"Esther 

[.code]

And this when it working fine

[code]

[2026-04-17 16:07:15.812][22356] [RzInterHaptics.RpcClient] [info] DLL version: 1.0.0.5
[2026-04-17 16:07:15.812][22356] [RzInterHaptics.RpcClient] [info] Establishing connection to RzInterHaptics RPC with session "TestSession"
[2026-04-17 16:07:15.812][22356] [RzInterHaptics.RpcClient] [info] RpcClient::InitRpc ping successfully.
[2026-04-17 16:07:15.812][22356] [RzInterHaptics.RpcClient] [info] InterHaptics app successfully registered "C:\Program Files (x86)\Interhaptics\HapticService\HapticService.exe"
[2026-04-17 16:07:15.812][22356] [RzInterHaptics.RpcClient] [info] RpcClient::GetAllDeviceIDs jsonData: "["3909-{cbb87b7f-67c4-53ee-986d-127f84cff70b}"]"
[2026-04-17 16:07:15.813][22356] [RzInterHaptics.RpcClient] [info] RpcClient::GetMetadata deviceID: "3909-{cbb87b7f-67c4-53ee-986d-127f84cff70b}", metadata: "{"DeviceName":"Esther 

[/code]

So what happened now is the freyja just stopped working suddenly while in FFXIV Online disabling SENSA HD gives vibration back so what I did is Closing Chroma and all razer apps through the tray icon Disabling hapticservice /enable open chroma back again and vibration works with sensa so it is 100% something with the hapticservice

Why  are you not able to fix the minimize bug after starting the synapse app after a system start?

Minimize option is already marked in the options but every time synapse starts with the main window. 

Is that problem so big that a team can’t fix it?

My System:

Win10 full úpdated
CPU Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz   3.70 GHz
Memory    64,0 GB
HD Space 466 GB SSD NVMe Samsung SSD 970, 466 GB SSD NVMe Samsung SSD 970, 224 GB SSD KINGSTON SKC300S37A240G, 224 GB SSD KINGSTON SKC300S37A240G
GPU NVIDIA GeForce RTX 2080 Ti (11 GB)

 

I am a user of the 2025 Razer Blade 16, and I am reporting a bug that appeared after the recent Synapse 4 update.

The issue is that upon every boot, the value for the "CPU Voltage Optimization" option under the "Razer Blade 16 - Performance" tab is being automatically forced to "1".

This symptom started occurring immediately after the latest Synapse 4 update. I would appreciate it if the development team could investigate this and release a fix in the next update.