AUDIO GUIDE / FIX A PROBLEM

MicDrop connected but no sound? Check the audio path

Fix a silent MicDrop connection by checking the Windows source, captured output, phone route, microphone cable, and application input in order.

START HERE

A connected session does not prove that the selected audio source contains sound. Check the Windows app output, MicDrop’s captured device, and the phone’s actual output in that order. Test microphone return as a separate path.

If the PC itself has no playback before you start MicDrop, begin with the general Windows no-sound checklist. Establish a working source before testing the phone connection.

First identify which direction is silent

“No sound” can mean no desktop playback on the phone, no phone microphone in a Windows app, or both. Name the direction before changing settings. If pairing or Connect never completes, use the connection guide instead.

For playback, leave microphone sending off and use the phone speaker. For microphone return, select the built-in phone microphone and use a private Windows recording. Simplifying the route makes the first failed stage easier to find.

Desktop playback: start at the Windows source

  1. Play a familiar local clip and confirm it is audible at the PC's selected output.
  2. Check the source application's volume and its per-app output in Windows. An application assigned to a USB headset will not necessarily appear on a different default speaker output.
  3. Stop the MicDrop host and select that actual playback device in Desktop audio source under Audio. Save and restart it.
  4. On the phone, enable Play desktop audio, connect, and raise media volume gradually.

If an output was unplugged, disabled, or renamed by a driver change, choose an available endpoint deliberately. MicDrop retains explicitly selected endpoints and reports them missing rather than silently substituting a different one.

Next isolate the phone output

Disconnect Bluetooth for a speaker-only check, or explicitly select the speaker where supported. Confirm the effective output after connecting. A chosen device name alone does not prove the operating system opened that route.

On Android and iPhone, MicDrop's Diagnostics include Start local output test to check phone playback without the Windows connection. If local output also fails, investigate phone volume, routing, and device availability. If local output works but the streamed source is silent, return to the Windows source and session diagnostics.

If the speaker works and a headset does not, test the headset with another phone audio app and compare media playback with microphone-enabled use. Those are different route conditions.

Microphone return: follow the reverse path

Checks for phone audio missing on Windows
StageCheck
Phone captureCorrect microphone, permission granted, Send microphone enabled, not muted
Windows hostPhone microphone destination set to an available virtual-cable playback endpoint (such as CABLE Input)
Windows receiverMatching cable recording endpoint selected; app permission and mute state correct

With VB-CABLE, the host sends to CABLE Input and the application receives from CABLE Output. Do not switch the host return endpoint to physical speakers as a workaround: that changes the route and can create feedback.

Use the timing of the failure

  • Silent from the beginning: prioritize selection, permissions, and muted sources.
  • Silent after an output changes: check device availability and the effective route, then reconnect deliberately.
  • Silent after screen lock: investigate background restrictions.
  • Silent after a network interruption: check recovery state and whether new audio returns, rather than only looking at a Connected label.

Collect a report that narrows the problem

Record the silent direction, app versions, Windows output, phone model/OS, and headset model. Include which baseline worked and the exact change that broke it. Copy the phone's last stream report and the matching Windows connection log when available. Review diagnostics before sharing; remove invitations, credentials, private addresses, and private audio.

Sources & version notes

Checked against the documentation below on November 13, 2026. App labels and platform support can change; use matching MicDrop builds and check the current release notes. These are setup guides, not new hardware benchmark results.