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

29 OCTOBER 2026 - Synapse & Chroma for Windows

  • Oct 28, 2026 10:59 AM UTC
  • 55 replies
  • 1885 views
Show first post

55 Replies

  • smc_work
  • Insider Mini
  • Nov 2, 2026 3:10 PM UTC
  • Using the Text function on a button could crash the app

    This is still happening for me with a Razer Deathadder V2 on Windows 11 26H2 on Synapse V4.0.63.2610281118. This needs to be fixed ASAP. I use this for work.
easyCaribbeanGreenegg784
Until Razer fixes their stuff, just manually assign the buttons in Synapse. This works for me, as someone else mentioned.

 

  • Valcart
  • Insider Mini
  • Nov 3, 2026 1:16 AM UTC

Anyone having issues with Naga v3 Pro scroll up/down not working at all? Scroll click works as usuall only scroll up/down does not work.

  • samandxiong
  • Insider Mini
  • Nov 3, 2026 2:12 AM UTC

Update: I found a workaround for the Basilisk V3 Pro + Mouse Dock Pro button issue.

On my original Basilisk V3 Pro (30K), both Scroll Mode Toggle and Cycle Up Sensitivity Stages stopped working after Synapse started. Changing the wheel mode directly in Synapse still worked.

This restored BOTH physical buttons for me:

1. Open the Basilisk V3 Pro's Customize tab in Synapse.
2. Select the DPI cycle button in the Standard layer.
3. Instead of leaving it on Default, explicitly assign Sensitivity > Cycle Up Sensitivity Stages.
4. Click Save.

It assigns the same function, but explicitly saving it appears to make Synapse generate and apply the button mapping table for the Dock. I only reassigned the DPI button; the scroll mode button started working again as well.

Before this change, the logs showed "skip empty DualLink mapping table". Afterward, the mapping table was applied successfully, and I confirmed that both buttons worked with Synapse still running.

This suggests a problem with how an all-default profile is handled through the Dock. This is a workaround confirmed on my setup, not an official fix. No firmware flashing, reinstalling, or program-file modifications were needed. I have not tested whether it survives a reboot yet.

Hope this helps others with the same issue, and gives the Razer team a useful lead.

Thanks alot for your post, I’ve had the same issue as well with V3 Pro and Mouse Dock, and I followed your instructions, that seems to be some bugs on the Default mode. After I assigned Sensitivity>Cycle Up Sensitivity Stages, it worked again, and when I changed it back to Default afterwards, it still works. Hope this would help others with the same problem. Cheers!

    technoPlumsecret864

    I'm seeing missing sensor readings on a Razer Hanbo AIO 360MM with Synapse 4.0.86.2610281118.

    On the Hanbo Performance page:
    - Fan speed: 0 RPM
    - Pump speed: 0 RPM
    - Liquid temperature: 0°C
    - CPU and GPU temperatures and clock speeds display normally.

    Razer Chroma also displays “FAN COUNT ERROR — Mismatch fan count from product description.” All three radiator fans are visibly spinning, and changing the fan preset audibly changes their speed, but Synapse continues to report 0 RPM.

    Windows Device Manager detects the cooler as Razer Hanbo AIO with no device error, and Synapse identifies it correctly. Switching the fan preset to Performance audibly increases the fan speed, but the RPM reading remains at zero.

    CPU-Z independently reports approximately 2,432 RPM on the motherboard's CPU_FAN header, while Synapse continues to show zero.

    System: Windows 11, Ryzen 9 5900X, ASUS ROG STRIX B550-F GAMING (WI-FI), RTX 5070 Ti.

    I don't have a comparison with an earlier Synapse version, so I can't confirm when this issue started.

    Is Razer investigating the missing Hanbo fan/pump RPM and liquid-temperature readings? Is there a fixed version or supported workaround?

    CookiesAccessibility statement