Microphone not working in Windows 11? Find where input stops

Start with the exact failure

“The mic is broken” can mean Windows cannot see the device, the input meter never moves, Windows records silence, one app cannot use it, other people hear the wrong microphone, or the signal is faint or distorted. Those are different branches.

Write down the microphone, connection type, Windows build, affected app, and what changed around the first failure. Note whether it began after reconnecting a dock, pairing a headset, switching accounts, installing an update, or changing privacy settings. Timing helps you test, but it does not prove cause.

Check the physical path first

Look for a hardware mute switch or button on the microphone, headset, inline cable control, keyboard, laptop, or webcam. Check whether its light means muted or active. If the device has a physical shutter, privacy cover, or detachable boom, put it in the normal recording position.

For a wired microphone, reseat both ends once. If it uses a 3.5 mm plug, confirm the computer jack supports that connector type; headphone-only and combined headset jacks are not interchangeable. For USB, connect directly to the computer for the comparison instead of through a dock or unpowered hub. Do not force a plug or use a damaged, hot, loose, or corroded connector.

For Bluetooth, confirm the device is charged, powered on, and connected to this PC rather than a phone or another computer. If you use a wireless receiver, treat the receiver and headset as one path and check both.

See whether Windows lists the intended input

Open Settings > System > Sound. Under Input, look for the exact microphone. Select it instead of assuming the current default is correct. A laptop may expose its built-in array, a webcam microphone, a headset, a dock, and a monitor input at the same time.

• The microphone is missing: keep the investigation on connection, pairing, the port, the receiver, hardware detection, or the driver.
• It appears but is not selected: select it and repeat the Windows test.
• It appears twice: record both names and test one at a time. Do not remove either entry on sight.
• The wrong device moves: Windows is hearing a different microphone. Fix the selected input before changing drivers.

Use the built-in Windows microphone test

Microsoft’s current Windows 11 flow is Settings > System > Sound > Input, choose the device, open its properties, and select Start test. Speak one short neutral sentence at your normal distance. Select Stop test, then Play to hear the result.

Keep the test brief. If the recording is clear, the microphone, connection, Windows detection, and base capture path all worked during that test. Move to permissions and the app. If there is silence, return to device selection and input volume. If it is faint or distorted, test placement, distance, input volume, cable, port, and one clean alternate device path before reinstalling anything.

Check input volume without chasing maximum level

In the selected microphone’s properties, inspect Input volume. Raise it in small steps while repeating the same sentence at the same distance. Maximum volume is not automatically better; it can add clipping, background noise, or feedback.

If your microphone or interface has a physical gain control, change one control at a time. Save the Windows percentage and hardware position that produced the clearest test. Do not enable every enhancement or boost at once because you will not know which change mattered.

If Windows records you but one app does not

The problem is now above the base Windows input path. Open Settings > Privacy & security > Microphone. Microsoft says Microphone access must be on, and Let apps access your microphone must be on for Microsoft Store apps that need it. Enable only the app you intend to use.

Desktop apps use a separate Let desktop apps access your microphone control. Windows may not offer an individual toggle for every desktop app. If a work or school policy controls the setting, do not bypass it; ask the device owner or IT team.

Then open the app’s own audio settings and choose the same microphone that passed the Windows test. Browsers, meeting apps, games, recording tools, and voice chat clients may keep their own input selection. Check in-app mute, push-to-talk, channel permissions, site permissions, and the active account or profile.

Compare one second app

Use a trusted app already on the computer, such as Sound Recorder, or the service’s built-in test call. Keep the recording private and delete it when you no longer need it.

• Windows test and second app work: the original app, browser site, account, or profile remains the likely scope.
• Windows test works but every app fails: review the Windows privacy controls, desktop-app access, organization policy, and security software logs.
• Windows test fails too: move back to selection, connection, detection, level, and driver state.

If the microphone is missing, compare the connection

For USB, try one known-good direct port on the computer. For a detachable cable, use a known-good compatible cable only if the manufacturer supports it. For Bluetooth, open Settings > Bluetooth & devices and save whether the device shows Connected. Do not repeatedly remove and re-pair it until you have recorded the current state.

If practical, test the microphone on another authorized computer, or test a known-good microphone on this computer. Change one thing at a time:

• Problem follows the microphone: keep its cable, receiver, power, firmware, and hardware in scope.
• Problem follows one port or dock: keep that connection path in scope.
• Every microphone is missing on one PC: widen to Windows audio input, policy, chipset, USB, Bluetooth, or driver state.
• The microphone appears only after reconnecting: save that intermittent behavior rather than calling it permanently fixed.

Check Device Manager before changing a driver

Open Device Manager and look under Audio inputs and outputs, Sound, video and game controllers, Bluetooth, and Universal Serial Bus controllers as appropriate. Save the exact device name, status, warning symbol, and error code. Do not remove unrelated audio devices.

Microsoft’s microphone troubleshooting flow includes uninstalling the audio device driver and scanning for hardware changes when simpler checks fail. That step can interrupt speakers, headsets, docks, or business audio. Before using it, download any model-specific driver you may need from the computer or device manufacturer, keep the PC on power, and create a restore point when appropriate.

After one controlled driver action, restart if instructed and repeat the same Windows microphone test. A device returning in Device Manager is not the outcome; the intended microphone must be listed, selected, and able to record.

Use Bluetooth LE Audio settings only when the hardware supports them

Microsoft documents optional Bluetooth LE Audio quality controls for Windows 11 version 24H2 or later on PCs with integrated LE Audio support and a compatible accessory. That capability is not available on every Windows 11 computer and it is not a universal microphone fix.

If the setting is absent, do not force a registry change or install a random Bluetooth package. Use the PC manufacturer’s compatibility and driver guidance. If the microphone works but call quality changes between apps, save the connection mode and app behavior before changing audio-quality options.

Do not confuse input and output problems

A microphone sends audio into the computer. Speakers and headphones send audio out. You can have a working microphone with no playback, or working speakers with a silent microphone. Use our Windows 11 no-sound guide for output trouble.

A webcam can also expose its own microphone. If Windows cannot see the camera, use the webcam detection guide; if the camera works but its microphone does not, keep the input test separate.

Build a useful evidence card

• Windows edition, version, and full build from winver
• microphone model, connection type, and physical mute state
• whether it appears under Sound > Input and Device Manager
• selected input and Input volume
• Windows Start/Stop/Play test result
• privacy controls and whether the app is Store or desktop software
• original app and second-app comparison
• alternate port, cable, dock, receiver, microphone, or PC result
• driver provider, version, warning, and any exact error code
• recent update, pairing, dock, policy, or app change

Where OmniMend fits

OmniMend 2.0.2 for Windows can help keep the Windows build, device state, recent changes, and before-and-after results together while you work through the input path. It does not listen to private conversations, grant an app microphone permission, bypass company policy, repair a damaged cable, or prove that one update caused the failure.

Review what OmniMend can and cannot inspect, use the help center, or browse the evidence-first guide library. Keep recordings, passwords, account names, meeting links, private file paths, and unredacted logs out of anything you share.