GamingClassify the failure
Open Settings, System, Sound, then Input. If the device is absent, start with connection and hardware discovery. If it is listed but the meter does not respond, inspect mute, gain, and device properties. If Start test records correctly, Windows detects it and the remaining issue belongs to the app selection or permission.
Use the device's actual name. Headsets, interfaces, monitors, and webcams can add similarly named inputs.
Prove the physical path
Connect a USB microphone directly to a known-good computer port and allow discovery to finish. Avoid an unpowered hub during diagnosis. Reseat detachable cables and test a known-good compatible cable if available.
For XLR, Windows detects the interface, not the analog microphone. Confirm the interface is powered, the correct channel is selected, gain is raised, mute is clear, and phantom power is used only when the microphone requires it.
Select and test the input
Microsoft directs Windows 11 users to Settings, System, Sound, Input. Select the microphone, open its properties, choose Start test, speak normally, stop, and play the recording. Adjust Input volume only after confirming the right device.
A moving meter with a silent or distorted playback can indicate routing or level problems. A flat meter with the device listed points earlier in the path.
Allow microphone access
Open Settings, Privacy & security, Microphone. Turn on Microphone access and Let apps access your microphone. For traditional desktop programs, also turn on Let desktop apps access your microphone.
Desktop apps may not have individual switches. After changing access, restart the affected app and reselect the microphone. Browser-based chat may also require site permission.
Refresh discovery carefully
Disconnect and reconnect the device, restart Windows, and apply current Windows and device-vendor updates. Device Manager can show whether hardware is disabled or reporting a problem; use vendor instructions for any dedicated driver or control software.
Do not treat a generic driver reinstall as the first move when a cable or permission test has not been done. A second known-good computer can separate device failure from the Windows host.
Choose the next branch
Absent on multiple computers with known-good cable and power suggests the device or cable needs service. Present but flat suggests hardware controls, interface channel, or level. A successful Windows recording with a failed app test means select the same named input and check that app's permission.
If the app is Discord on macOS, its XLR-interface limitation is separate and irrelevant to this Windows diagnosis.
Windows may switch defaults when a controller, webcam, monitor, dock, or headset reconnects. After the microphone works, open the target game or chat app and choose the same named endpoint. A successful Windows Start test proves capture, but it does not guarantee each application follows the current system default.
Preserve evidence before removing drivers or vendor software: note the device name, port, Device Manager status, and whether the meter moves. If a restart fixes discovery only temporarily, test power and cable stability and consult the manufacturer's support path. Repeated disappearance is more informative than a single successful reconnect.
When testing a headset through a 3.5 mm jack, distinguish a combined headset socket from separate headphone and microphone sockets. The required plug or splitter must match the computer and headset wiring. Hearing playback proves only the headphone conductors; it does not prove the microphone conductor has the correct connection.