A microphone that stops working on Windows 10 tends to reveal itself embarrassingly: you join a call, speak confidently, and learn minutes later that nobody heard a word. The speakers work, the camera works, but your voice goes nowhere. Windows 10 manages microphones through an older dual system — the classic Sound control panel for device state and the modern Settings app for privacy — and a failure in either half silences you completely.
The usual suspects are well known to anyone who has maintained Windows 10 machines: privacy permissions reset by an update, the wrong recording device set as default, the microphone disabled in the Recording tab, or an audio driver that handles playback fine while the capture path stays broken. Hardware failure is possible but sits at the bottom of the probability list.
The order below separates the layers efficiently: device state in the classic panel, privacy in Settings, app-level selection, driver repair, and finally hardware verification.
Why this happens
- Microphone disabled in the Recording tab: The classic Sound panel lets recording devices be disabled independently. A disabled mic never appears in modern Settings, making it invisible to casual checks.
- Privacy permissions reset by an update: Windows 10 updates can revoke microphone access globally or per app. The driver is healthy; Windows is simply refusing to share the mic.
- Wrong default recording device: With multiple inputs — headset, webcam, built-in array — Windows may default to an unplugged or wrong device while the real mic sits idle.
- App-level device or permission wrong: Browsers and conferencing apps have their own mic selectors and permission prompts, independent of Windows settings.
- Audio driver capture path broken: A corrupted or generic audio driver can play sound perfectly while the recording side fails silently.
- Microphone level set to zero or muted: The Recording tab’s level slider and mute checkbox are easy to disturb accidentally and hard to notice afterward.
- Hardware failure: A damaged mic array or loose cable kills input in every OS. Failure after a drop or spill points here.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Enable the mic in the classic Recording tab
The old Sound panel is where device state lives. Start here, not in Settings.
- Right-click the speaker icon and choose Sounds, then open the Recording tab.
- Right-click the empty area and check Show Disabled Devices and Show Disconnected Devices.
- Right-click your microphone, choose Enable, then Set as Default Device. Speak and watch the level bars move.
Fix 2: Check levels and mute state
A working but silent mic is often just turned down to nothing.
- In the Recording tab, double-click the microphone and open the Levels tab.
- Set the level to 80 or above and confirm the speaker icon shows unmuted.
- Test again. If the bars move now, the fix was embarrassingly simple.
Fix 3: Verify Windows 10 privacy permissions
Windows can gate the mic even when the device is perfect. Clear the gate.
- Open Settings, then Privacy, then Microphone.
- Turn on Allow apps to access your microphone.
- Review the per-app list and enable your specific apps. Desktop apps need the Allow desktop apps toggle as well.
Fix 4: Set the right device in your app
With Windows configured, make sure the app is listening to the right input.
- Open the app’s audio or voice settings — not just the system settings.
- Explicitly select your microphone rather than Default communications device.
- In browsers, click the lock icon in the address bar and set the microphone to Allow for the site. If audio output devices also misbehave, the headphone detection guide covers the adjacent output-side troubleshooting.
Fix 5: Reinstall the audio driver
When the device is enabled, permissions are granted, and still nothing records, the driver’s capture path is the suspect.
- In Device Manager, expand Sound, video and game controllers.
- Uninstall the audio device, checking Delete the driver software, then restart.
- Install the audio driver for your exact model from the vendor’s support site — not the generic Windows pick. For the newer OS with its own permission model, see microphone fixes on Windows 11 .
Fix 6: Test with Voice Recorder to isolate
Use the simplest possible app to separate system problems from app problems.
- Open Voice Recorder and record ten seconds of speech.
- A visible waveform means the system path works — the original app was at fault.
- A flat line after all the fixes above means the problem is below the apps: driver or hardware.
Fix 7: Verify the hardware outside Windows
The definitive test removes Windows from the equation entirely.
- Boot a live Linux USB and test the microphone there.
- Working in Linux proves the hardware is fine and the issue is Windows configuration or drivers.
- Dead in Linux too means the mic array or its connection needs service. Microsoft’s Windows support pages document the built-in recording troubleshooter for any remaining software checks.
Fix 8: Run the Recording Audio troubleshooter
Windows 10 includes an automated troubleshooter for recording audio that checks device state, levels, driver problems, and permissions in one pass. It occasionally catches misconfigurations that manual checks miss, such as a device disabled in a way the Sound panel does not show clearly. It costs two minutes and is worth running before hardware tests.
- Open Settings, then Update and Security, then Troubleshoot, then Additional troubleshooters.
- Run the Recording Audio troubleshooter and apply any fixes it recommends.
- Test with Voice Recorder afterward to confirm the system path works.
Closing
Windows 10 microphone failures are almost always found in the gap between the two settings systems: the classic Recording tab says disabled while modern Settings says everything is fine, or privacy silently revokes what the driver happily provides. Check device state, permissions, app selection, and the driver in that order, and confirm with Voice Recorder. The mic that missed the meeting is usually back before the next one — no new hardware required.
