What this section covers
Audio drivers connect applications with input and output hardware. Missing sound can involve the selected output, application settings, a connection or a driver; a microphone problem can also involve permissions. Check the listening or recording path before replacing software. Windows 11 and macOS expose different tools, and an external interface may have its own requirements. The steps below help distinguish those cases without assuming that every audio symptom has the same cause.
How this driver type works
An audio application works through operating-system interfaces to send or receive samples. Driver components connect that work with an audio controller or an external interface. A headset may expose several functions, including playback, recording and buttons.
The selected output determines where playback goes. The selected input determines which microphone or interface receives a recording request. Correct driver installation does not automatically select the device you intend to use in every application.
Many common devices work with operating-system audio components. Other interfaces require a package for particular features. Sample formats, connection profiles and application permissions can matter independently of package versions. An update is not a substitute for checking the active route.
Checking the current configuration in Windows 11
For audio & sound, these steps inspect the current configuration. Information and setting names can differ by build, connection and manufacturer. A missing control is not permission to choose a destructive action.
- Open Settings, then System, then Sound.
- Record the selected output and selected input separately.
- Open the relevant device properties to inspect controls that are actually present.
- In Device Manager, inspect the relevant audio device under Sound, video and game controllers or Audio inputs and outputs.
- Read Properties, Driver without choosing removal or update controls.
Checking the current configuration in macOS
For audio & sound on a Mac, use the controls actually offered for the device. macOS does not provide a Windows-style Device Manager or one universal list of every driver version. Separate accessory software can have different requirements.
- Open System Settings and choose Sound.
- Read the Output and Input lists, and select the item you are investigating for inspection.
- Check the application-specific audio choices separately from the system choices.
- For an external interface, read its entry in System Information and its manufacturer compatibility requirements.
Considering an update safely
Audio & Sound components built into the operating system and separate accessory applications have different update paths. A working configuration may need no immediate package change. Relevant security advisories, compatibility requirements or administrator policies can justify one; do not force obsolete extensions or disable protections to make a package load.
- Record the exact device, operating-system version and the reason for considering a change.
- Check the operating-system update settings for applicable changes; optional packages may be separate from ordinary updates.
- If the manufacturer requires separate software, verify the model, system version and package requirements on its documentation site.
- Prepare backups and a relevant recovery option before changing a package; a restore point is not a personal-file backup and may be unavailable.
- Apply only the documented change, then compare the same function and settings. Stop rather than force a package that does not match.
Common problem: Playback is silent
Mute, volume, an unintended output or a disconnected device can explain silence. The operating system and individual applications can use different routes.
If playback is silent remains unexplained, read the documentation for the exact model and operating-system version before attempting changes with wider effects.
- Check mute and volume in the application and in system sound settings.
- Verify that the selected output is the one you intend to hear.
- Try a familiar recording in another application; compare results before changing a package.
Common problem: A microphone is listed but records nothing
Presence in a device list does not establish that an application has permission or has selected that input. A physical mute switch can also matter.
If a microphone is listed but records nothing remains unexplained, read the documentation for the exact model and operating-system version before attempting changes with wider effects.
- Check the microphone or interface for a mute switch.
- Compare the selected input in system settings and the recording application.
- Review microphone permissions for that application; do not grant access to unrelated applications.
Common problem: An external interface is missing
Power, the data connection and compatibility requirements matter. A charging cable or unsuitable hub can prevent the expected interface from appearing.
If an external interface is missing remains unexplained, read the documentation for the exact model and operating-system version before attempting changes with wider effects.
- Check power and the cable type against the interface instructions.
- If practical, compare a direct compatible connection with the current hub path.
- Stop before installing a package until the exact interface and operating-system version match its documentation.
Common problem: Audio changes when a wireless headset connects
A headset may offer different profiles for playback and microphone use. Application choices and connection capabilities can change the available format.
If audio changes when a wireless headset connects remains unexplained, read the documentation for the exact model and operating-system version before attempting changes with wider effects.
- Record whether the change occurs only when the microphone is used.
- Compare the application input and output selections.
- Read the headset documentation for profile limits instead of assuming that a new driver removes them.
Audio
Check the simple causes too
Built-in class drivers work for many USB audio devices, but not all; onboard codecs often use the computer or motherboard maker's package.
- Muted or wrong default device, an application's own output setting, a privacy setting blocking the microphone, a worn jack or cable, low power on a USB hub, or a fault in the speakers themselves.
Audio: Playback (output); recording runs the other way
- Applicationplays a stream
- Audio enginemixes and resamples
- Audio driverbuilt-in class or vendor
- Codec or DACconverts digital to analogue
- Speakers or headphonesanalogue or USB
Field notes
Audio & Sound driver guide: field notes
Audio: Playback (output); recording runs the other way
- Applicationplays a stream
- Audio enginemixes and resamples
- Audio driverbuilt-in class or vendor
- Codec or DACconverts digital to analogue
- Speakers or headphonesanalogue or USB
Write these down first
- The default playback and recording devices
- Sample rate and bit depth in the device properties
- Enabled enhancements or spatial sound
- Driver name and version, and whether it is a built-in class driver or a vendor one
Clues, not a diagnosis
Might involve the driver: Devices missing from the sound list, silence that began after an update, or crackle that stops when enhancements are switched off.
Check these too: Muted or wrong default device, an application's own output setting, a privacy setting blocking the microphone, a worn jack or cable, low power on a USB hub, or a fault in the speakers themselves.
Where updates usually come from
Built-in class drivers work for many USB audio devices, but not all; onboard codecs often use the computer or motherboard maker's package.
Frequently asked questions
Does a listed output prove it contains speakers?
No. An output can route audio through a display connection, external interface or other endpoint. The destination and selected route determine where sound can be heard. Check the connected equipment and application settings before interpreting the entry as a physical speaker.
Why can one application be silent while another works?
Applications can have separate mute, volume and device choices. Their workloads and formats can also differ. Compare the route and settings in both applications before replacing a package. Working playback elsewhere is useful evidence, but it is not a complete hardware-health test.
Does microphone permission replace input selection?
No. Permission allows access, while input selection identifies the device the application should use. You may need both, and a physical mute can still prevent recording. Inspect only the relevant application permissions rather than enabling microphone access for unrelated software.
Are all audio interfaces covered by system updates?
No. Many common devices use built-in components, but some accessories need separate software for particular features. Read the documentation for the exact interface and operating-system version. System updates do not guarantee that every manufacturer application or accessory feature is updated.
Should I remove the audio device immediately?
No. Removal changes configuration and can interrupt sound or recording. Start with route, permission and connection checks. If a manufacturer procedure requires reinstallation, obtain the appropriate replacement and recovery instructions first; do not remove unfamiliar entries merely to simplify the list.
Keep reading
