This tiny Go-based tray app prevents the Razer BlackShark V2 Pro wireless headset from disconnecting due to microphone inactivity.
This is a workaround as Razer hasn't been able to fix their Sh*t
It does this by launching ffmpeg
in the background to continuously open the mic input — keeping it "alive" and preventing idle timeouts or power-saving disconnections.
Another workaround is to Disable Allow the computer to turn off this device to save power
in device manager. (it didn't work for me) Link here
- Install ffmpeg
- Download the executable and run it.
- (Optional Autostart) Shortcut
RazerMicKeepAlive.exe
to%appdata%\Microsoft\Windows\Start Menu\Programs\Startup
folder
- 🖥️ Tray icon with clean Quit button
- 🎯 Launches
ffmpeg
to keep mic active silently - ⚙️ Fully self-contained Go app (no GUI window)
- 🪶 Lighter than running OBS
Run in terminal:
ffmpeg -list_devices true -f dshow -i dummy
Look for your mic, e.g.:
"Microphone (Razer BlackShark V2 Pro 2.4)"
Copy that exact string.
git clone https://github.com/ndanilo8/razer-mic-keepalive.git
cd razer-mic-keepalive
go mod init razer-mic-keepalive
go get github.com/getlantern/systray
Then edit main.go
with the string above:
micName := `Your Device Name Here`
go mod tidy
go build -ldflags="-H=windowsgui" -o RazerMicKeepAlive.exe main.go
-H=windowsgui
ensures no terminal window pops up when you launch it.
Just double-click RazerMicKeepAlive.exe
. It will:
- Start
ffmpeg
in background - Show a system tray icon
- Keep your mic open and stable
- Prevent Random Razor Disconnects
To stop it: Right-click tray icon → Quit
If you want to kill ffmpeg
manually from script or terminal:
taskkill /IM ffmpeg.exe /F
- Press
Win + R
, typeshell:startup
- Place a shortcut to
RazerMicKeepAlive.exe
there
OBS keeps the mic open but:
- Uses CPU/GPU
- Always stays running visibly
- Less elegant than a background tray tool
This app does the same thing in <1MB and silently. Install and forget. Something that Razer doesn't know
tl;dr; just google "Razer Blackshark Disconnects"
Razer BlackShark V2 Pro wireless headsets are known to randomly disconnect, after using this headset the issues seems to be related to the microphone is not actively being used (e.g., not in a call or being recorded).
After deep investigation using:
- 🪵 Windows Event Viewer
- 🧪
Get-PnpDevice
, Kernel-PnP logs, and System logs - 🔍 USB tracing tools (e.g., USBDeview)
...its found:
- Windows continues to show the dongle as connected and "OK"
- No new PnP or driver crash events are triggered during the disconnection
- The only events visible are from the first time the dongle was inserted
The headset only disconnects when the microphone is not being used by an application. If an app (like OBS, Discord, etc) holds the mic open:
- The headset stays connected indefinitely
- No dropouts or audio loss occur
At least very rarely...
This strongly indicates:
- The issue is not caused by Windows
- It's likely due to Razer's firmware or driver stack entering an idle state and failing to wake the microphone channel properly
- There’s no system-level workaround, because Windows never sees the device as "disconnected"
Razer fix your sh*t
MIT — do whatever you want.
systray
by Lanternffmpeg
for the device-level capture