Troubleshooting: Razer Synapse not recognizing the Basilisk V3 X HyperSpeed or not saving changes

Applies to: Razer Basilisk V3 X HyperSpeed
Last updated: 30 October 2025

Problem

Razer Synapse does not show the Basilisk V3 X HyperSpeed, or it appears briefly and then disappears. In other cases Synapse detects the mouse but changes to DPI, polling, buttons, or profiles do not apply or do not persist after reboot. Common causes include a flaky USB path, receiver pairing issues, outdated services or drivers, profile conflicts, permission problems, or attempting to save software-only features to on-board memory.

Solution

Stabilize the hardware connection first, then refresh Synapse and its services. Re-pair the mouse to the HyperSpeed receiver if needed, verify Windows permissions, and test with a clean profile. Distinguish between software profiles and on-board memory. Save only hardware supported settings to on-board memory and export your full profiles for safety. When docks, hubs, or security tools interfere, test on a direct motherboard USB port and perform a clean boot.

Step-by-step instructions

A) Confirm the hardware link is solid

1. Set the mouse to 2.4 and plug the HyperSpeed receiver into a short USB extension on the desk.
2. Move the cursor to confirm the receiver is working without Synapse.
3. Try a different USB-A port. Prefer a motherboard port over hubs or docks.
4. Install a fresh AA battery and power cycle the mouse.

B) Restart Synapse and its services (Windows)

1. Close Synapse from the system tray.
2. Open Task Manager and end any leftover Razer processes.
3. Start Synapse again and check if the mouse appears on the Devices page.
4. If not, restart Windows and launch Synapse before other peripheral apps.

C) Refresh the receiver pairing

1. With the mouse set to 2.4, re-pair it to the HyperSpeed receiver using the official pairing utility.
2. After pairing, wait 10 to 15 seconds with the receiver still on the desk extension, then open Synapse again.

D) Repair or reinstall Synapse cleanly

1. In Apps and Features, choose Modify or Repair if available.
2. If detection is still inconsistent, uninstall Synapse and any leftover Razer drivers.
3. Reboot, then install the latest Synapse.
4. Launch Synapse and confirm the mouse appears before importing any old profiles.

E) Fix profile and permission issues

1. Run Synapse as an administrator once to ensure it can write settings.
2. Create a brand new test profile. Set a simple DPI and button remap and verify the change applies instantly.
3. If it works on the new profile, export your old profiles, delete them inside Synapse, then re-import selectively to find a problematic profile.
4. If your antivirus or endpoint protection is strict, create an allow rule for Synapse and its services and retest.

F) Understand on-board memory vs software features

1. On-board memory stores essentials like DPI stages, default DPI, polling, and basic button remaps.
2. Complex macros, app links, and certain Hypershift behaviors may require Synapse running in the background.
3. Save core settings to on-board memory and verify they persist with Synapse closed by moving the receiver to another PC.

G) Isolate the environment

1. Test with the receiver connected directly to the PC rather than through a dock or KVM.
2. Perform a Windows clean boot to eliminate third party conflicts.
3. Cross test on another computer. If the mouse is detected and changes save there, the original system has a software or policy conflict.

H) When nothing else works

1. Try a spare compatible HyperSpeed receiver and pair the mouse to it.
2. Test Bluetooth mode briefly to confirm the mouse is healthy.
3. Collect logs and a brief summary of steps taken for support, including port choice, extensions, and whether a clean profile worked.

Optional methods or tools

• USB extension cradle to bring the receiver into line of sight for stable detection.
• Profile export and import to back up and selectively restore working layouts.
• Firmware updater when available to address rare detection or power state quirks.
• System restore point before large Synapse or driver changes so you can roll back cleanly.

Best practices or tips

• Keep one minimal hardware profile with standard buttons, sensible DPI, and 500 to 1000 Hz polling so you can test behavior without software.
• Avoid stacking several 2.4 GHz receivers on the same hub. Spread them across ports to reduce radio and bus contention.
• After major Windows updates, reopen Synapse, confirm device detection, and re-save on-board memory so settings persist.
• If you rely on docks or KVMs, validate detection on a direct motherboard port for a day before returning to your usual setup.

Razer Synapse is most reliable when the underlying 2.4 GHz link is clean and Windows is not throttling USB power or blocking background services. Stabilize the receiver first with a short extension and good placement, then repair or reinstall Synapse so it can enumerate the device correctly. Re-pairing the mouse to the receiver resolves many cases where the cursor works but the software does not see the device.

Saving the right settings to on-board memory is the key to consistent behavior across PCs. Keep software profiles for complex workflows and link them to applications, but store your DPI, default stage, polling, and core remaps in hardware. This split lets you move between systems with predictable control even if Synapse is not present or is still installing.