How to test your microphone after a sound driver change
Check whether a sound driver change altered your microphone, input level, format, or recording quality, then isolate the cause before changing settings.
Your microphone sounded different after a driver update, or the input you used before has disappeared. A driver change can reset the default input or alter how sound reaches apps, so first check what the browser receives before adjusting settings.
The Microphone Test shows the input level, waveform, selected device, sample rate, channels, and latency. You can also make a short recording and play it back to check for low volume, distortion, or dropouts.
Inspect the microphone input
- Open the Microphone Test and press Start microphone. Allow microphone access when your browser asks.
- Choose the microphone you want to inspect from the device list. If the driver update added or renamed inputs, test each likely option separately.
- Speak at a steady distance and volume for a few seconds. Watch the signal meter, its loudest level in dB, the waveform, and whether the status changes to Sound detected.
- Press Record 5 seconds, speak a full sentence, then play the recording. Listen for a clear voice, unexpected hiss, distortion, or cutouts.
- Note the device name, sample rate, channels, and latency shown in the details. Compare them with what you expected or with another available microphone.
For a useful comparison, keep the microphone in the same position and speak at the same volume. Change only one setting between tests, then repeat the short recording.
What the result means
The meter moves and the recording sounds normal
The browser is receiving usable audio from that input. If a meeting or recording app still sounds wrong, it may have selected a different microphone or kept its own input settings from before the driver change. Check the input selector inside that app.
The meter moves, but the recording is quiet or distorted
The microphone is sending audio, but the level or processing may have changed. A low level can point to the wrong input or reduced input volume. Distortion can happen when the input is too loud, or when an enhancement is processing the sound badly.
The meter stays still
The browser is not receiving sound from the selected input. Check that you chose the right device, that it is not muted, and that browser and system permissions allow microphone access. If no microphone appears in the list, check whether the operating system detects it.
The device details changed
A different device name, sample rate, or channel count can mean the driver now exposes a different input mode or device. A changed value alone does not prove a fault. Listen to the recording and check whether the actual behavior is worse.
The test reports a microphone error
If it says no microphone was found, the browser cannot see an input it can use. If it says the microphone is being used by another app, close other calling or recording software and test again. The driver may be working while access is blocked elsewhere.
How to fix it
- Confirm the selected input. On Windows 11, open Settings › System › Sound and choose the intended device under Input. On macOS, open System Settings › Sound › Input and select the microphone. Then choose the same device in the app where the problem occurs.
- Check mute and input level. Look for a mute switch on the microphone or headset. In Windows 11, go to Settings › System › Sound › Input, select the device, and check its input volume. On macOS, use the input volume controls under System Settings › Sound › Input, if they are available for that device.
- Allow microphone access. In Windows 11, open Settings › Privacy & security › Microphone and turn on microphone access and access for desktop apps. On macOS, open System Settings › Privacy & Security › Microphone and allow your browser or affected app. Also check the microphone permission beside the browser address bar, then reload the test page.
- Close other apps using the microphone. Quit video call, voice chat, and recording apps, then test again. An app may keep the input busy or apply its own processing even when its window is not open.
- Review audio processing and format. In Windows 11, open Settings › System › Sound › Input, select the microphone, and check available audio enhancements and format options. If the problem began after the driver change, test with enhancements off and return to a standard format offered by Windows. Change one option at a time. macOS exposes fewer input format controls, so test the microphone in another app before changing anything else.
- Check the driver if the input is still missing or unstable. In Windows, open Device Manager, expand Sound, video and game controllers, and inspect the relevant device. If the issue began immediately after an update, check the device's driver properties for a rollback option, or install a compatible driver from Windows Update or the computer or microphone maker. Restart and repeat the browser test. On a Mac, install available macOS updates and follow the microphone maker's instructions if it requires separate software.
When the microphone may be faulty
Test the microphone on another computer or phone if possible. If it fails there too, reconnect the cable, try another port, or remove and pair the Bluetooth device again. A microphone that remains silent or cuts out when its cable moves may have a hardware fault. For a built-in laptop microphone, contact the manufacturer or a repair shop if it fails across multiple apps and after system troubleshooting.
What the test can and cannot tell you
The sample rate describes how often the input is measured each second, and the channel count tells you whether the input is mono or stereo. Neither value alone tells you whether a voice recording will sound good. The microphone's position, room noise, input level, and processing matter too. Latency is a timing measurement, not a direct quality rating.
The test runs in your browser, and the short recording stays on your device. Use it to check the input signal, then confirm the same microphone and settings in the app where you noticed the problem.
