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

08 SEPTEMBER 2026 - Synapse & Chroma for Windows

  • August 11, 2026
  • 35 replies
  • 3643 views
DigitalAnomaly
Forum|alt.badge.img

Synapse for Windows - V4.0.86.2608311115 / Chroma for Windows - V4.0.63.2608271424

IMMERSIVE UPDATE - SEE. HEAR. FEEL

Chroma has always been about making your setup yours. This update makes it even more immersive. Three new features are rolling out, each one taking something happening on your machine and translating it into your Chroma devices in real time. No configuring scenes for every game. It just responds.

SEE - Screen Sync

Extends what's on your screen out into your setup. Colors and motion from the game get mapped to your Chroma devices as they happen, so a muzzle flash, a health warning, or a sunset over the map plays out across your room instead of stopping at the bezel.

HEAR - Mood Analyzer

Reads the emotional tone of what you're listening to and translates it into lighting. Not a volume meter that pulses on the bass, but something that picks up on whether a track is calm, tense, or euphoric and lights your setup to match.

FEEL - Impact Engine

Turns in-game audio into haptics. Explosions, gunfire, engine rumble, and impacts come through as physical feedback, so you feel hits instead of only hearing them.

 


NOTICE: END OF WINDOWS 10 SUPPORT FOR RAZER SYNAPSE 4

Following Microsoft's end of standard support for Windows 10 back on October 14, 2025, full support for Razer Synapse 4 on Windows 10 will end on October 14, 2026. As with Microsoft, this is a firm change: bug fixes and technical support for Synapse 4 on Windows 10 will not continue beyond this date.

From October 14, 2026 until October 12, 2027, any bug fixes released for Synapse 4 on Windows 10 will be limited to security updates only, mirroring Microsoft's own extended security updates for the platform. After October 12, 2027, Windows 10 support and compatibility will no longer be maintained for Synapse 4. Synapse 4 can still be used on Windows 10 and will still receive feature updates, but we cannot guarantee full functionality as we will no longer fix or address any bugs seen exclusively on Windows 10.

Moving forward, we recommend upgrading to Windows 11 to ensure the best possible experience. For more information on Microsoft's Windows 10 end of support and extended security updates, please visit Microsoft's official support page.

 


RELEASE NOTES

8 SEPTEMBER 2026

Fixed

  • Stability & Reliability
    • Synapse could get stuck on a processing or loading screen when adjusting settings on certain cameras
    • Opening the Feedback page during application launch could prevent Synapse from minimizing or auto-starting properly
    • Background services and notification components failed to initialize properly during silent startup
    • Dashboard could become unresponsive or fail to load correctly in certain scenarios
    • Philips Hue integration did not automatically launch in the background when Synapse started
    • Installation could fail silently on certain system configurations
    • Firmware update notification prompts did not dismiss when clicking outside the dialog window
    • Synapse introduction tour did not complete properly for new users
  • Device Detection & Connectivity
    • Keyboards could appear offline with no Chroma effects after unlocking the PC if the keyboard had been powered off before locking (affects BlackWidow V4 Pro 75% and other wireless keyboards)
    • Peripherals connected via multi-device HyperSpeed dongles were not detected correctly after reconnecting or waking from sleep
    • Certain wireless mice were not recognized by Synapse when connected via dongle
  • Chroma RGB
    • Lighting Effects
      • Quick Effects and custom lighting failed to re-apply on devices that were powered on during system suspend or screen lock
      • Gaming Mode LED did not light up on the F10 key after certain keyboards woke from sleep
      • Lighting effects could flicker or fail to persist correctly when switching device states
      • Chroma RGB lighting on mice connected via dual-link failed to synchronize correctly
      • Tidal wave center point alignment setting did not apply correctly in Chroma Studio
      • Refreshing the device page could incorrectly reset the dim lighting option on certain mice
    • Chroma Studio
      • Chroma Studio could freeze when saving custom lighting effects or adjusting selected areas
    • Chroma Visualizer
      • Chroma Visualizer displayed visual flickering and wave effect glitches on launch
      • Accessing settings within Chroma Visualizer caused active device tabs to close unexpectedly
      • Chroma App could get stuck in a downloading or updating state
  • Key Mapping & Customization
    • Button Remapping
      • "Save Remapped Button" popup still appeared after closing the key mapping panel without making any changes on certain keyboards and keypads
      • F1–F3 keys could not be used as standard function keys on certain portable keyboards
      • Holding FN + F2/F3 for volume adjustment did not work on certain keyboards
      • Multimedia, function, and volume controls stopped working after closing Synapse on certain devices
      • Remapped keys were missing the "Requires Razer Synapse" warning indicator on certain devices
    • Snap Tap & Rapid Trigger
      • Snap Tap settings failed to report errors or apply correctly on certain analog keyboards (including Huntsman V3 Pro)
      • Secondary function assignments could not be changed or saved on certain keyboards
      • Snap Tap toggle remained greyed out for supported analog keyboards even when eligible
    • Macros
      • Macro assignments on scroll wheels or certain secondary devices triggered incorrect key outputs
      • Sequence macros reverted key assignments to raw scan codes on app relaunch
      • Macro recording dropped inputs if the first recorded keypress was the Numpad Period key
      • Global Shortcut "Play while assigned key is pressed" option did not trigger the assigned macro
    • AI Launcher
      • AI Launcher option was missing from the key assignment panel on certain keyboards and mice
    • Gaming Mode
      • Gaming Mode toggle settings were not retained after waking from sleep on certain keyboards
  • Audio & Sound
    • Sensa HD (Haptics)
      • Sensa HD haptics profile incorrectly displayed as "disabled" on the dashboard while actively running
      • Audio-to-Haptic (A2H) feedback experienced noticeable latency in supported games
    • Microphone
      • Microphone sidetone settings reset to default after restarting the computer
      • Headset microphones unexpectedly switched the default Windows audio input device
      • Peak level indicator lights were unresponsive on certain streaming microphones
    • Audio Visualizer
      • Audio Visualizer displayed visual flickering and wave effect glitches on launch
  • Performance & Hardware Controls
    • DPI & Polling Rate
      • Custom DPI values and polling rate settings did not save or apply correctly on certain mice and keyboards
    • Volume & Media Controls
      • Holding dedicated volume buttons did not continuously adjust volume while Synapse was running
    • Cameras & Streaming Devices
      • Device page could get stuck in a processing state when adjusting sampling rate on certain Razer cameras
  • Profiles & Settings
    • Synapse 3 profile imports could result in corrupted profile states or missing macro bindings
    • Auto-switch game profiles failed to launch automatically for certain titles
    • Cloud sync profile prompts appeared repeatedly for certain wireless devices
    • Auto-launch checkbox setting did not save correctly after refreshing
  • UI/UX
    • Updated device illustrations and product images across a wide range of keyboards, mice, headsets, cameras, and peripherals
    • Fixed various layout, alignment, and display issues across device pages, settings panels, the dashboard, and Chroma Studio
    • Resolved missing or incorrectly displayed UI elements across key mapping, lighting effects, and device setup screens
    • Fixed display scaling and text clipping issues at high Windows display scaling settings (175%+)
    • Restored missing "More Information" firmware update links on the Devices & Modules page
    • Controller setup tutorial updated to reflect the correct intended design
  • Localization
    • Fixed unlocalized text strings, truncated labels, and missing translations across non-English languages including French, German, Korean, Japanese, Russian, Spanish, and Simplified/Traditional Chinese
    • Corrected localization issues in the Sensa HD haptics tab, AI Launcher menu, and various tooltip strings

Improvements

  • Improved multi-device HyperSpeed pairing stability and device compatibility across mice and keyboards
  • Enhanced Sensa HD haptics engine with improved Audio-to-Haptic (A2H) feedback responsiveness
  • Updated Audio Capture component for improved Chroma Visualizer performance

 


PREVIOUS RELEASE NOTES

31 AUGUST 2026

New

  • Razer BlackShark V3/V3 Pro Series - Added Competitive Mode, ULL Smart Switcher and 2nd Roller Disable
  • New THX Game Profiles
    • Dead as Disco
    • Deep Rock Galactic: Rogue Core
    • Dispatch
    • Echoes of Aincrad
    • Forza Horizon 6
    • Gothic 1 Remake
    • Hades II
    • Meccha Chameleon
    • Mina the Hollower
    • Mouse: P.I for Hire
    • Pragmata
    • REPLACED
    • Slay the Spire II
    • Subnautica 2
    • Warhammer 40,000: Darktide
    • Witchspire
  • Rename Razer Resonance to Impact Engine

Fixed

  • Razer Naga V3 Pro - Key assignment, scroll mode, and DPI adjustment issues
  • Razer Blade 18 (2026) - EQ settings not being applied
  • Mecha BREAK crashing with Synapse

25 AUGUST 2026

Fixed

  • Mice not working when paired with a wireless keyboard dongle and Snap Tap is enabled

18 AUGUST 2026

Fixed

  • Increased CPU utilization when using system monitoring

11 AUGUST 2026

New

  • New Chroma App Features
    • Screen Sync
    • Mood Analyzer
    • Razer Resonance

35 Replies

AlphaTay
  • Insider
  • August 12, 2026

Hi, pretty sad for Long Live WIndows 10 Extended Security Updates


  • Insider Mini
  • August 12, 2026

Did not know exactly which update brick the support from simhub.
but simhub did not control any lights since at least the august update. It could be broken before because i used a Chroma RGB version from Feb or March i think.
Please investigate the bug.


Rolacka
  • Insider Mini
  • August 12, 2026

This update appears to have broken the charge level indicator for my Deathadder v4 its always saying 100% despite it needing charging even when plugged in via usb it still says 100% battery level even though its clearly  charging at the moment..


  • Insider Mini
  • August 13, 2026

Just thought I would note somewhere that after this update my Razer Naga V2 Pro is no longer reliably connecting to my PC over a wired connection. When I plug it in it either flickers with purple on the razer symbol (not the side buttons) and just constantly beeping like something has just been connected or just won’t connect at all. I got it to reconnect once briefly by using a different USB port but that only lasted a few minutes at best and I couldn’t get it to do it again. At least once Windows noted that it didn’t recognize the device and or something of that matter as well but I couldn’t force it to give me the same alert so I could type it out exactly. Luckily it appears that the wireless 2.4ghz dongle is working just fine and it is still charging fine from the pc without any issues it appears. Hope this gets fixed soon, I prefer using my device wired because I use the dongle for other devices that aren’t my gaming PC that I switch between.


  • Insider Mini
  • August 16, 2026

I cannot tell what the mood analyzer does, whenever I enable it, it seems to just do the regular spectrum cycling and nothing more, I’m not sure if there is something wrong with it or if I need to update something further, but any info would be much appreciated.


psolem
  • Insider Mini
  • August 16, 2026

DId this update change anything in the Razer Chroma API?
I may not be wording it correctly, but my issue is several of the devices I was lighting in my development project have suddenly stopped working.
I am using Razer Chroma SDK for Unity installed from https://github.com/WyvrnOfficial/Unity_ChromaSDK.git and all WAS working well until this update.. Now I am only getting lights on mousepad, mouse and mouse dock. Keyboard, Seiren, Tartarus, Aether strip have all stopped responding to requests to light up.
I think the problem might be in ChromaAnimationAPI, specifically ChromaAnimationAPI.SetEffectCustom2D(int device, int[ ] colors) is no longer working.
Can anyone confirm if this update changed this API?
Is anyone else suddenly having issues using this API or lighting some devices?


Lrbrownii
  • Insider
  • August 17, 2026

After begging to have Razer Chroma light strip set and Chroma Addressable RGB controller working properly in my PC for over a year. Quitting Synapse was the best thing I ever did.

My PC actually works. We added Pro Click v2 vertical and Razer handheld dock and I made the plugin for Razer Kitsune. 

 

I sure enjoyed my time with Synapse 3 but it seems it is time to move on. The last couple months sure have been nice not to deal with the constant issues I have had with Synapse 4 for the last two years.

 

Sure wish I could use my Razer system with Razer software but I guess that will never happen...


Lrbrownii
  • Insider
  • August 17, 2026

Why does my PC not work with Synapse software? 

The last couple of months has been great not using this software.


omegabetaalpha0

It was good to see the more frequent updates as well as changelogs that address the myriad of bugs Synapse has.

But now these updates are quickly turning into an add-more-bloat cycle rather than fixing what's broken.


Lemonalleybest668

chroma will not finish the update, tried deleting and reinstall multiple times, no go


ItzAzphrinx
  • Insider Mini
  • August 20, 2026

I cannot tell what the mood analyzer does, whenever I enable it, it seems to just do the regular spectrum cycling and nothing more, I’m not sure if there is something wrong with it or if I need to update something further, but any info would be much appreciated.

It shows the waves and colors depends how loud the audio is (It’s not similar to visualizer). It will auto detect depends what application you’re running, and it just works for me all the time.


Can we get a full breakdown on what these new immersive options are meant to do? I can’t find info anywhere. For example, what devices does Razer Resonance apply to? I see a headset pictured, but doesn’t it and the Razer Freyja both already have haptics? Does this improve upon the existing audio to haptic option for the Freyja? Currently, enabling it disables the haptics on the Freyja completely.


  • Insider Mini
  • August 30, 2026

Tottally lost the connection to Chroma Apps. Does not respond to the launch of games, apps, etc. Also stopped to work with Asus Chroma Control. All switches and allowances are set as usual.


  • Insider Mini
  • September 7, 2026

This update killed my Tartarus Pro. 

 

If I exit Synapse and Chroma then it works completely and totally, though with default mappings, thought hat loses all the lighting I bought the Tartarus and .Huntsman for, as well as all the mapping for my Huntsman, Tartus, and Naga, 

 

Can you fix that, then allow the option to go totally offline? I’ve had so many hangs from bad cloud syncing, and so many issues with updates that I do not trust Synapse with any online connectivity. 


Will_Crespo
  • Insider Mini
  • September 8, 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.


  • Insider Mini
  • September 8, 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.


psolem
  • Insider Mini
  • September 8, 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?


Horog
  • Insider Mini
  • September 8, 2026

Synapse 4 update bugs for me…

  • Dashboard - Device tiles do not remember their positions. I drag them into the correct order, but after restarting Synapse, the order is not preserved.
  • Global Shortcuts - I had shortcuts bound to switching Chroma profiles, and they stopped working. Newly configured bindings do not work either.
  • Linked Games - Game names are not centered in the tiles, and long names are truncated and end with "...".
  • Huntsman V3 Pro 8KHz - the keys in the top-right corner (see image) do not work correctly:
    - Button 1 ... Multimedia - Previous Track ... does not work with Spotify
    - Button 2 ... Multimedia - Next Track ... does not work with Spotify
    - Button 3 ... none of the available settings for this button work with Spotify (Play / Next Track / Previous Track)
    - Button 4 ... Volume up / down / mute does not work ... instead, it scrolls the page in the browser

Everything described above worked correctly in the previous version!!!

 

 

I use the following Razer devices:
- Huntsman V3 Pro 8KHz
- Naga V3 Pro
- Mouse Dock Pro
- Firefly V2

None of the following helped:
- Clean installation of Windows 11
- Clean installation of Synapse 4
- Different user account in Synapse 4
- Razer Driver Clean-up Tool


is there a way to rollback this update on my machine? it broke the functionality of the Tartarus V2 joystick.. again...


  • Insider Mini
  • September 8, 2026

The latest update from September 8th has brought back the same problem you had resolved with the July 8th update:

  • D-Pad not working
    • Razer Tartarus Pro
    • Razer Tartarus V2

FIX IT AGAIN PLEASE


  • Insider Mini
  • September 8, 2026

This update (Sept 8th) broke my Tartarus V2, was working fine yesterday. Today I turned on my PC, Synapse updated and all my custom key bindings stopped working saying that they required Razer Synapse, which is obviously installed. Already repaired, uninstalled, cleared files with the Razer tool, reinstalled and the issue persists. Windows 11.

 

Screenshot sample:

 

 


  • Insider Mini
  • September 8, 2026

Same as everyone else, DPad is not working. It works perfectly fine when software is closed. 4 button and 8 button does not make a difference. Only closing synapse


It’s been over two months since I made a support ticket about the “switching between keymaps delay” bug on my Tartarus. It used to be instantaneous up until late June’s update.

After all these updates and no word from Razer, it still won’t register the keymap switching if hit a second time too fast. I must wait for it to register a second keymap press. IE: Currently on keymap 1, hold button for keymap 2, press a command, release sets back to keymap 1. If I hit keymap 2 again for another command (or any other command in keymaps 3 or 4) way too fast, it will not register the switch.

I use the Tartarus V2 for work and Pro for home and it has completely ruined my workflow. There is latency on either Tartarus versions on both computers. I never had the D-pad bug on either one though. I really do not understand the amount of regressions in these updates!!


psolem
  • Insider Mini
  • September 8, 2026

It’s been over two months since I made a support ticket about the “switching between keymaps delay” bug on my Tartarus. It used to be instantaneous without latency up until late June’s update.

After all these updates and no word from Razer, it still won’t register the keymap switching if hit a second time too fast. I must wait for it to register a second keymap press. IE: Currently on keymap 1, hold button for keymap 2, press a command, release sets back to keymap 1. If I hit keymap 2 again for another command (or any other command in keymaps 3 or 4) way too fast, it will not register the switch.

I use the Tartarus V2 for work and Pro for home and it has completely ruined my workflow. There is latency on either Tartarus versions on both computers. I never had the D-pad bug on either one though. I really do not understand the amount of regressions in these updates!!

I have this problem exactly. And I've noticed if I didn't wait for that delay and stay clocking buttons too fast it will overwhelm the whole profiles key maps. I also don't have d pad issues but this keyboard switch delay has plagued me for a while, before this immersive update.


It’s been over two months since I made a support ticket about the “switching between keymaps delay” bug on my Tartarus. It used to be instantaneous without latency up until late June’s update.

After all these updates and no word from Razer, it still won’t register the keymap switching if hit a second time too fast. I must wait for it to register a second keymap press. IE: Currently on keymap 1, hold button for keymap 2, press a command, release sets back to keymap 1. If I hit keymap 2 again for another command (or any other command in keymaps 3 or 4) way too fast, it will not register the switch.

I use the Tartarus V2 for work and Pro for home and it has completely ruined my workflow. There is latency on either Tartarus versions on both computers. I never had the D-pad bug on either one though. I really do not understand the amount of regressions in these updates!!

I have this problem exactly. And I've noticed if I didn't wait for that delay and stay clocking buttons too fast it will overwhelm the whole profiles key maps. I also don't have d pad issues but this keyboard switch delay has plagued me for a while, before this immersive update.

I have reported the “original keymap overwritten to the keymap you’re switching to” bug as well. I think the delay we are experiencing is their “fix” but I can still overwrite the keymap if I am not careful. What a mess. I’ve been using these devices since the first Nostromo N52TE and I’ve never experienced anything like this.