The short version
- 01Record the headset model and whether it uses USB, 3.5 mm or Bluetooth.
- 02Check the headset's mute control and select the headset as the recording input.
- 03Select the headset in the game or chat app and check whether Push-to-Talk is enabled.
- 04Allow microphone access for the intended app and check whether Windows picks up your voice.
- 05Use the matching USB, 3.5 mm or Bluetooth branch rather than mixing connector-specific steps.
- 06Compare another compatible device and retain the result before driver or hardware repair.
Start here
Check the recording device before the game
Our first comparison is Windows microphone detection versus the game or chat app. Check mute, recording defaults and the app's own input. Then choose the connection-specific branch; a USB software test does not diagnose a 3.5 mm socket.
Applies to: Razer headsets on Windows. Physical controls, detachable microphones and Synapse support depend on the model.
Choose the connection and failing test
Keep the model and connection type with the result. Test again after each matching change.
Windows responds, but the game does not
Confirm the app's chosen input and Push-to-Talk behavior.
Check the app inputA wired USB headset has no mic input
Connect directly and compare Synapse behavior.
Follow the USB branchA 3.5 mm headset is silent
Check microphone attachment, socket seating and another compatible device.
Follow the analog branchBluetooth playback works but calls do not
Check the available hands-free communication profile.
Follow the Bluetooth branchCheck mute, recording defaults and the app input
Razer's current input article checks the default recording device, the game's input, Push-to-Talk and the headset's mute control. Our recommendation is to compare Windows voice detection with the app before changing drivers; a responding input narrows the failure to the app route.
Allow the intended app to use the microphone
Razer checks microphone permission for the selected app. Its Windows recording panel also checks default recording and communication devices. Our recommendation is to allow the app you intend to use, then record whether the level meter responds to your voice.
For 3.5 mm, check the physical audio path
Seat a detachable microphone and the audio jack, and inspect the jack/port for debris. Razer compares another compatible device before attributing the fault to the computer. Its driver reinstall example names a specific Realtek device; our recommendation is to have support identify your actual hardware first.
For USB, compare direct connection and Synapse
Use a direct wired USB connection without a hub; wireless USB models need an interference check. Razer's Synapse 4 branch compares mic enhancement/side tone and exiting Synapse. If exiting helps, it directs a software reinstall. Retain the result before the driver-reinstall branch.
For Bluetooth, check the call profile
Razer's PC branch selects the available Hands-Free AG Audio endpoint as the default communication device for recording and playback, then re-pairs at close range if needed. Use the product's pairing guide. Our recommendation is to retain the displayed endpoint names because profiles vary by system.
Give support the connection and comparison result
Razer compares the headset with another compatible device. Our recommendation is to report the model, connector, Windows recording result, app input and second-device result. These distinguish app, computer and headset paths without treating every silent mic as a failed peripheral.
Frequently asked questions
Why can sound playback work while the mic stays silent?
Recording input and app permissions are separate from playback. Bluetooth also needs an appropriate communication profile. Check the microphone path rather than assuming working speakers establish a working mic.
Should every Razer headset use Synapse repair?
No. Razer's article has separate analog, USB and Bluetooth branches, and Synapse support depends on the model. Begin with the actual connection and input result.
Sources and review notes
Checked on . Razer's October 2026 article bodies read directly, including all connection-type accordions. Comparing Windows/app results, limiting permissions to the intended app and retaining endpoint names are editorial guidance. Glitchary is independent of Razer.