Microphone Not Working in Windows 11: Input Selection, Permissions, Levels, Drivers, and Hardware

Do not begin by reinstalling drivers. First separate three different failures: Windows does not list the microphone at all; Windows lists it but its own microphone test receives no useful signal; or Windows receives a signal but one application does not. Each result points to a different layer and prevents unrelated fixes from obscuring the original symptom.

Open Settings > System > Sound and find Input. If the intended microphone is listed, select it and open its properties. Microsoft’s current Windows 11 microphone guidance uses this page for device selection, input volume, and the built-in microphone test. If the device is absent from Input, skip app settings for now and move to connection, device-state, and driver checks.

With the intended device selected under Sound > Input, start the microphone test and speak normally. Stop the test and play the recorded sample. If Windows records your voice, the operating system is receiving audio from that input path; a failure limited to Discord, a browser, a game, recording software, or another app is then more likely to involve that application’s selected input or permission state.

If the device is listed but the Windows test records silence or an unusably weak signal, check the microphone or headset hardware mute switch, boom position, connection, and the Windows Input volume control. Increase input volume only as needed while repeating the same test. There is no universal correct percentage or boost value because microphone sensitivity, analog interfaces, USB devices, headsets, webcams, and vendor gain stages differ.

Windows 11 has several microphone permission layers under Settings > Privacy & security > Microphone. Microsoft documents a device-level Microphone access control, Let apps access your microphone for supported app permissions, and a separate Let desktop apps access your microphone control for desktop software. A microphone can therefore work at the Windows sound-test level while an application remains unable to open it.

Enable only the access needed for the application you are intentionally using. Microsoft notes that desktop apps are handled differently from Microsoft Store app entries: desktop applications do not receive individual toggles in the same list, and the desktop-app access setting applies to that class as a whole. Do not broadly disable privacy protections as a troubleshooting shortcut.

When the Windows microphone test is good but one application still hears nothing, keep the investigation inside the application path. Confirm the app is allowed to use the microphone, then open its audio or voice settings and select the same microphone that succeeded in Windows. Applications can retain their own input choice, so a previously used webcam, USB interface, headset, dock, or virtual device can remain selected after the hardware arrangement changes.

Restart the affected application after changing its input if it does not immediately reacquire the device. Then test another microphone-aware application. If several applications can record but one cannot, that isolates the fault strongly toward the failing application or its configuration. If no application can record even though the Windows test succeeds, re-check the Windows microphone privacy controls before escalating to drivers.

A microphone that never appears under Sound > Input has not reached the same point in the Windows audio path as a listed device with a flat meter. For a wired headset or microphone, verify the connector is fully seated and is being used with the port or adapter the device actually requires. For USB audio, reconnect the device and, where practical, test another known-good port without assuming every hub, dock, cable, or adapter is equivalent.

For Bluetooth microphones or headsets, first confirm that Windows actually shows the device as paired and connected, but do not treat that connection label as proof that a usable microphone endpoint exists. Bluetooth profile behavior and vendor controls can differ by device. If the microphone endpoint is absent, use the manufacturer’s supported pairing instructions and Windows Bluetooth troubleshooting rather than forcing an undocumented profile, codec, or sample format.

Microsoft’s current microphone troubleshooting guidance directs Windows 11 users to the recording/input audio troubleshooter and, when Windows is not detecting the microphone, to Device Manager driver recovery. That is a later step, not the first response to an app-only permission problem. Run the input-device troubleshooter from the Sound troubleshooting area when the device state is unclear or Windows cannot produce a working input path.

If Windows does not detect the headset, webcam, or microphone, Microsoft documents uninstalling the affected audio device in Device Manager, restarting so Windows can attempt to reinstall it, scanning for hardware changes when necessary, and then updating the audio driver. Prefer Windows Update or the PC, motherboard, laptop, USB-interface, headset, or microphone manufacturer’s supported Windows 11 package over third-party driver-download sites.

Enumeration only proves that some part of the device path identified itself to Windows. It does not prove that the microphone capsule, boom wiring, analog cable, TRRS adapter, USB converter, wireless link, interface preamp, mute circuitry, or vendor-specific control state is passing usable audio. That is why the Windows microphone test and cross-device checks matter more than the mere presence of a device name.

When practical, test the microphone on another compatible computer or device and test a known-good microphone on the affected Windows 11 PC. Also change one physical link at a time: port, cable, adapter, dongle, or interface where the hardware permits it. If the same microphone fails on multiple compatible hosts, the hardware chain becomes more likely. If several known-good microphones fail only on one PC, the common Windows, port, interface, or driver path deserves more attention.

If the microphone is missing from Sound > Input, investigate connection, pairing, device state, and drivers. If it is present but the Windows microphone test receives no signal, investigate hardware mute, positioning, input volume, the physical chain, and then supported device/driver recovery. If the Windows test works but an application does not, investigate privacy permission and that application’s selected input before touching the driver stack.

After every change, repeat the same Windows test or the same application test so you know which action changed the result. Avoid registry hacks, generic “driver booster” utilities, random driver packages, universal gain values, and destructive Windows reset/reinstall advice. The goal is to identify the failed layer with the smallest reversible change, then escalate only when the evidence points to the next layer.