Mic works in Windows.
Nobody hears your call?

Decide which microphone should hear you

Is it the laptop’s built-in microphone, a USB headset, a webcam’s microphone or a Bluetooth headset? Write down that device’s name. Hearing sound through headphones confirms playback, not their microphone input. Close the live meeting before making test recordings and use a harmless phrase in a quiet space; do not record other people or confidential conversation.

Check the headset’s physical mute switch or boom position. If the laptop has a microphone-mute key, use its model manual to identify it; the key, indicator and Fn behavior vary. For a USB microphone, check the connection and compare another direct USB port if available. Dell’s basic microphone checks distinguish connection, mute and selected-input problems.

Test the same input you plan to use in the call

1. Open Start → Settings → System → Sound. Under Input, choose the microphone you identified. A laptop microphone array and a headset microphone may be separate entries.
2. Open that device’s properties. Under the microphone test, select Start test, speak normally for a few seconds, then select Stop test.
3. Choose Play under the recorded sample and listen. If needed, adjust Input volume gradually and repeat the same phrase.

Microsoft documents this Windows 11 test. Labels vary with Windows release and audio hardware. If you cannot hear playback, first confirm that Windows is using an audible output; silence from muted speakers does not establish a failed recording.

Your voice is clear in this device’s sample

That input captured your voice in this test. Keep its exact name for the call settings below.

The device is absent, or the sample is silent

Recheck the connection, mute and Windows access below. Do not treat a successful test of a different microphone as a pass for this one.

Allow the intended app to use the microphone

Open Settings → Privacy & security → Microphone. For an app you trust and intend to use, check Microphone access and Let apps access your microphone, then its individual switch if one is listed. Microsoft shows the Windows 11 permission steps. A browser meeting also needs access for the browser itself.

If access is greyed out, managed or blocked by your organization, ask the device administrator. Do not remove management, change registry policies or disable security software to force a test. Restore any optional permissions you no longer want after the comparison.

Select the tested microphone inside the call app

Open the affected app’s audio/device settings and select the same named microphone that recorded your voice. Check the app’s own mute control. Dell describes independent app input selection; Windows’ default alone may not be the app’s choice.

1. Teams desktop: open Settings and more → Settings → Devices, then select the microphone in the audio settings.
2. If Make a test call is offered, follow its short recording/playback prompts. Microsoft says this test is unavailable in Teams for web; a missing button there is expected.
3. In a meeting, the arrow beside Mic → More audio settings lets you review the input. Recheck after reconnecting a headset or changing audio devices.

These examples follow Microsoft’s Teams microphone guide. Teams for personal use also has desktop Settings → Devices, but features differ by app/account. Use its personal-use device settings guide; do not assume every account has the same test-call options.

For a Bluetooth mic, check charge and whether it is connected to another device, then reconnect and reselect it. Keep the laptop microphone as a separate comparison, not an assumed replacement for the headset test.

Review the permission for the actual meeting site

Windows allowing a browser to use the microphone does not automatically authorize every website. Confirm you are on the intended meeting service before allowing access.

• Chrome: open Settings → Privacy and security → Site settings → Microphone. Check the selected microphone. Review the blocked-site list and change the intended meeting site’s microphone permission to Allow if you want that site to hear you. Google documents the current permission and input controls.
• Edge: visit the meeting site and allow its expected microphone prompt. To review a previous block, open Settings → Privacy, search, and services → Site Permissions → All sites, choose that site and inspect its microphone permission. See Microsoft’s website-permission explanation.

Save anything being drafted in the page, leave the call, then reopen or rejoin it and check the site’s own microphone selection. Do not grant every website microphone access or clear all browser data for this comparison. Work/school Chrome settings may be controlled by an administrator; Google directs managed-browser users to that administrator.

Use the difference to choose the next step

Windows sample works; one app or site still fails

Focus the next check on that app’s selected input, mute, access and meeting controls. A hardware replacement is not established by this result.

The app’s test plays back your voice; one person still cannot hear

Confirm the actual meeting uses that input and you are unmuted. Ask that person to check their playback and, with permission, compare another participant. The test does not certify the whole call connection.

Built-in mic works; a headset does not

Record each input name and connection type. Compare the headset’s mute, connection and compatibility before changing the laptop’s working audio setup.

No microphone captures your voice in Windows

The app-only path has not been established. Record missing devices or warnings and seek model-specific Windows/audio support rather than repeatedly changing meeting permissions.

These comparisons narrow an investigation; they do not identify an internal part. Stop once the intended microphone works reliably in the intended call, and keep a note of the setting that changed it.

Restart safely, then stop before resets

If it persists, save open work and recordings, close the meeting and restart the app or browser. For a normal PC restart, use Start → Power → Restart, then repeat the same local and app tests. Dell’s restart and update guidance also covers checking offered Windows updates. On a managed PC, coordinate updates with IT.

Stop sooner for liquid damage, abnormal heat, a loose/broken socket or a plug that needs force. For persistent failure, contact the laptop/headset manufacturer or arrange a laptop assessment. Bring the model, Windows version, input names, connection type, local sample result, affected app/site and exact warning. For locked settings or a remote/virtual desktop, involve the administrator first. Do not publish a Service Tag, account details or a private voice recording in a troubleshooting screenshot.