I would like to report a reproducible issue with the Razer Tartarus Pro on Synapse 4.
After a cold boot, the Tartarus Pro fails to output default keyboard binds and custom keyboard binds. The device is still detected by Synapse 4, profile switching appears to work, and macros can still work. Keyboard-output binds do not function until the Tartarus Pro is unplugged and reconnected.
The issue appears to occur when the previous shutdown was initiated using Windows shutdown.exe with a timeout value greater than zero, for example: shutdown /s /t 60
Microsoft documents that when the shutdown timeout period is greater than 0, the /f parameter is implied. Microsoft also documents /f as forcing running applications to close without warning users. The issue does not appear to occur when using a full shutdown with no timeout, for example: shutdown /s /t 0
This suggests the issue may be related to Synapse 4 or the Tartarus Pro driver stack not handling Windows forced application closure or shutdown timing correctly when shutdown.exe is used with /t > 0.
This issue was not present when using the same Tartarus Pro on Razer Synapse 3. It only appeared after moving to Synapse 4. The Tartarus Pro is listed by Razer as a Synapse 3 and 4 supported device, so this appears to be a Synapse 4 regression rather than a general Tartarus hardware fault.
Please pass this on to your testing teams to validate and rectify.
VERSION:
Windows 11 Pro 25H2
Razer Synapse Version 4.0. [removed by moderator]
Razer Tartarus:
- firmware version 1.2.0.0
- UI version 1.0. [removed by moderator]
- Middleware version 1.0. [removed by moderator]
Thank you.