Audio hardware on a Windows PC ranges from the integrated codec soldered to your motherboard to dedicated sound cards, USB audio interfaces, and external digital-to-analog converters. Most laptops and desktops use an onboard codec paired with a software audio stack, so the driver you actually need is frequently the version your PC or motherboard maker customized for that exact model. Vendor-tuned packages often enable jack sensing, speaker calibration, microphone noise suppression, and surround processing that a generic Microsoft-supplied driver leaves inactive. That is why we recommend confirming the manufacturer of your specific device before downloading anything.
For onboard audio, the underlying codec is commonly made by a component vendor, but the packaged installer is usually distributed through your system builder. If you own a prebuilt desktop or a laptop, start at that brand's support site and search by model or serial number, because those OEM packages are validated against your firmware and power management. If you assembled the machine yourself, the motherboard vendor's support page is the correct source for the audio package that matches your board.
Dedicated audio devices vary. A discrete sound card or professional interface may have a model-specific Windows driver, control application, or firmware tool, while a class-compliant USB device may need none of them for basic operation. Mixer routing, low-latency recording paths, buffer controls, and user-installable firmware exist only where the exact model documentation lists them.
Below you will find broad, authentic audio driver families and product lines grouped by vendor. Many entries are integrated or OEM audio solutions that do not ship as a standalone universal download; for those, the safest path is to obtain the OEM-customized package from your computer or motherboard manufacturer. We generally do not point you to bundled installers or ad-heavy mirrors, and we do not list version numbers here because the correct build depends on your hardware revision and Windows edition.
To find the source, go to your PC or motherboard maker's support site, enter your exact model or serial number, and download only what applies to your system. The Windows 10/11 labels below are discovery aids, not a promise that every model, generation, architecture, or package supports both releases; the exact product or system download page controls.
An audio driver is the translation layer between Windows and the codec chip that turns digital audio into the analog signal your speakers and headphones need, and back again for microphones. It tells Windows what sample rates and bit depths the hardware supports, which physical jacks exist, and how the internal mixer routes each stream. Without it, Windows falls back to a basic class driver that can play and record sound but cannot see the extras a specific chip offers.
On top of that base layer, most vendor packages add a digital signal processing stage. This is where speaker equalization, bass management, microphone noise reduction, and virtual surround live. Laptop makers tune these settings to the specific speakers and enclosure of a chassis, which is why an OEM build often sounds noticeably different from a generic one on the same silicon. The driver also manages power states so the codec sleeps when idle and wakes cleanly when audio starts.
Some professional-device packages provide a dedicated low-latency path and adjustable buffers for supported recording applications; other devices are class-compliant or expose different controls. Check the model's Windows documentation before assuming a recording driver, software mixer, or firmware updater exists.
Expanded guide insight
The practical audio & sound context
Audio failures are often a break in the chain between Windows, the audio controller, the codec, and the selected output. Start with the endpoint and settings before changing a driver.
Check the selected output device first.
Treat HDMI audio as part of the graphics stack.
Use Windows Update for matched audio components.
Take care: If a problem began just after an update, use Roll Back Driver before trying a new package.
Fast checks for common audio & sound problems
What you see
Likely area to check
Safe first move
Sound stops after an update
A working component was replaced or mismatched
Use Roll Back Driver, then restart
Speaker icon shows a red X
Windows has no healthy audio endpoint
Check Device Manager, then scan for hardware changes
Sound is distorted or tinny
Enhancements or format settings are interfering
Disable enhancements and test the default format
Start with the lowest-risk check that matches what you see, then return to the detailed sections below if it does not resolve the issue.
Identify your exact device first
Open Device Manager and expand "Sound, video and game controllers" to read the exact device name, such as a Realtek or Intel entry.
In Windows Sound settings, note whether your default output is a speaker, a headset, an HDMI display, or a USB interface, since each is driven by different software.
A device listed under HDMI or DisplayPort output is served by the graphics driver, not the onboard codec.
USB headsets and interfaces appear under "Audio inputs and outputs" and often also under USB controllers when plugged in.
Check whether a vendor control panel (for example a MaxxAudio or Sound Blaster app) is installed, which signals an OEM or discrete package rather than the plain class driver.
On a laptop or prebuilt, use the service tag, serial number, or exact model to filter the maker's page, then confirm the returned package lists your hardware and Windows release.
Audio bundled in a Surface driver and firmware package
Scan the list first, then open the family that matches your hardware for the full reference.
Reference coverage summarizes the Windows releases discussed in this catalog; it is not certified compatibility. Confirm the exact device or PC model, hardware revision, current Windows release, and current package requirements on the publisher source before making a change.
This is a widely used onboard audio codec family for consumer motherboards and laptops, driving analog jacks and internal speakers on supported systems. It reports itself under "Sound, video and game controllers" and may pair with a vendor control panel for jack retasking and equalization. Because system builders tune audio for their own speakers and firmware, laptop and prebuilt owners should check the customized package from their computer maker rather than assume a generic package is compatible.
How you recognize it
Shows in Device Manager as "Realtek(R) Audio" or "Realtek High Definition Audio"
Analog jacks on the motherboard rear panel and front-panel header
Often paired with a Realtek Audio Console app
Onboard codec used by many PCs; laptop and prebuilt owners should check the OEM-customized package from their computer maker.
Realtek USB Audio covers the codec inside many USB headsets, speaker bars, and small audio dongles that connect over a USB port rather than an analog jack. Windows can usually run these devices with its built-in class driver the moment they are plugged in, so the Realtek package mainly matters when a device exposes extra controls. Expect these to appear under "Audio inputs and outputs" and under USB when connected.
How you recognize it
Appears when a USB headset or dongle is plugged in
Listed under "Audio inputs and outputs"
May also enumerate under USB controllers
Common in USB headsets and audio dongles; some devices use the class-compliant driver built into Windows.
Intel Smart Sound Technology is an on-die audio DSP built into many recent Intel laptop and tablet platforms, handling tasks such as voice wake, microphone processing, and power-efficient playback. Unlike a plain codec, it needs a matched controller driver and firmware, and a mismatch is a frequent cause of missing audio after a Windows upgrade. The validated build usually comes from the laptop or tablet maker rather than as a universal Intel download.
How you recognize it
Listed as an Intel Smart Sound Technology controller in Device Manager
Common on thin-and-light Intel laptops and 2-in-1s
Often accompanied by a separate audio codec entry
Audio DSP found on many Intel platforms; the validated package is typically distributed by your PC maker.
This component carries sound over HDMI and DisplayPort connections that run from Intel integrated graphics, so audio reaches a monitor or TV that has its own speakers. It installs as part of the Intel graphics driver rather than the onboard codec, which is why a missing display-audio device is really a graphics-driver problem. It only appears as an output when a display capable of audio is connected.
How you recognize it
Shows as "Intel(R) Display Audio" under sound controllers
Only active when an HDMI or DisplayPort display with audio is attached
Bundled with the Intel graphics package
Handles audio over HDMI and DisplayPort from Intel integrated graphics.
AMD High Definition Audio delivers sound down the digital display outputs of Radeon graphics and Ryzen integrated graphics, feeding the speakers built into a monitor or television. It rides inside the AMD graphics driver package, so you manage and update it by updating the display driver, not the motherboard audio. The output only shows up while a compatible display is plugged in.
How you recognize it
Listed as "AMD High Definition Audio Device"
Appears only with an HDMI or DisplayPort display connected
Installed by the Radeon or Ryzen graphics driver
Bundled with AMD graphics driver packages for audio over digital display outputs.
NVIDIA High Definition Audio carries sound over HDMI and DisplayPort from a GeForce or NVIDIA workstation GPU to a display with speakers. NVIDIA graphics installers can include this component, but custom installation choices and package variations mean it may not be installed with every display-driver installation. It is maintained through the applicable NVIDIA graphics package rather than as a general-purpose standalone audio download. Like other display-audio devices, it normally appears as a selectable output when a suitable monitor or TV is attached.
How you recognize it
Shows as "NVIDIA High Definition Audio"
Associated with a display connected to the NVIDIA GPU
Available as a component of applicable NVIDIA graphics packages
Carries audio over NVIDIA GPU HDMI and DisplayPort outputs when the package component is installed.
Sound Blaster spans many internal PCIe and external USB generations. Driver, application, effect, and Windows availability differ by exact product; use Creative's product page rather than assuming every model has the same control software or package layout.
How you recognize it
May enumerate with a Sound Blaster model name
Connection and software differ among PCIe and USB models
Match the exact Sound Blaster model and Windows release.
Sound BlasterX and AE names cover different Creative products and generations. Connection type, headphone controls, effects, application, and Windows support must be taken from the exact product page; the family name does not establish a shared complete package.
How you recognize it
Read the exact Sound BlasterX or AE model
Connection and control application vary by product
Match the exact Sound BlasterX or AE model, application, and Windows release.
Scarlett spans several USB interface generations. Focusrite's current Windows driver release notes list particular supported devices and operating systems; control-software generation and available routing differ by model. Follow the exact Scarlett setup instructions, including connection timing, rather than assuming one driver/app sequence for the whole family.
How you recognize it
External USB interface with generation-specific model name
Recording-driver and control-software support must be confirmed in the device list
Match the Scarlett generation to Focusrite's supported-device list and setup instructions.
Clarett and Vocaster are distinct Focusrite families with different hardware and control workflows. Focusrite's release notes enumerate supported devices; they do not establish that every Clarett or Vocaster has the same firmware updater, control app, connection order, or Windows support.
How you recognize it
Read the complete Clarett or Vocaster model and connection type
Confirm the model in Focusrite's supported-device list
Clarett and Vocaster software, firmware, and Windows support are model-specific.
This covers Logitech's USB headsets, speakerphones, and speaker sets that connect over USB and present themselves as audio endpoints. The great majority are class-compliant, so Windows drives them without a download, and Logitech's companion software is optional polish rather than a requirement. Reach for that software only when you want an equalizer, sidetone, or lighting control on a specific model.
How you recognize it
USB headset, speakerphone, or speaker set
Works as a plug-and-play audio device
Optional Logitech app adds equalizer or sidetone
Many devices are class-compliant; companion software adds equalizer and lighting controls.
Dell packages onboard audio as an OEM bundle that combines the underlying codec driver with tuning software such as Waves MaxxAudio, matched to the speakers and enclosure of each Dell model. Because that tuning is model-specific, the correct build is the one Dell lists against your machine, not a generic codec download. Find it by going to Dell's support site and entering your service tag or model.
How you recognize it
Often includes a Waves MaxxAudio control panel
Matched to a Dell service tag
Underlying codec entry appears in Device Manager
OEM audio for Dell systems; download the package matched to your service tag.
HP delivers onboard audio as an OEM package pairing the codec driver with HP's own tuning and companion apps for its laptops and desktops. The tuning assumes the speakers and firmware of a particular HP product, so a mismatched generic driver often loses features like speaker optimization. Identify the right build by searching HP's support site with your product name or serial number.
How you recognize it
Matched to an HP product or serial number
May install an HP audio companion app
Codec entry visible under sound controllers
OEM audio for HP systems; search by product or serial number for the correct build.
Lenovo's OEM audio packages bundle the codec driver with tuning validated against the acoustics of a specific ThinkPad, IdeaPad, or Legion chassis. Lenovo organizes downloads by machine type, so the best path is to look up your exact machine type on Lenovo's support site and take the audio package listed there. A generic driver may play sound but can leave the model's speaker tuning inactive.
How you recognize it
Selected by Lenovo machine type
Common across ThinkPad, IdeaPad, and Legion lines
Codec entry appears in Device Manager
OEM audio for Lenovo systems; obtain the package validated for your machine type.
ASUS ships audio in two contexts: onboard codec packages for its motherboards and tuned OEM builds for its laptops. Motherboard owners should take the audio package listed on the support page for their exact board model and revision, since the same codec is configured differently across boards. Laptop owners should use the audio build ASUS validated for that laptop, which carries the chassis-specific tuning.
How you recognize it
Motherboard packages listed per board model
Laptop builds tuned for a specific ASUS model
Underlying codec visible under sound controllers
Motherboard owners should download the audio package listed for their exact board model.
Surface devices manage audio through Microsoft's own driver and firmware packages rather than a separate third-party codec download, keeping the codec, speakers, and microphones tuned as one unit. Updates typically arrive through Windows Update or a consolidated Surface driver package for a given model. Because everything is integrated, the recommended route is simply to keep the device current through those official channels.
How you recognize it
Audio bundled in a Surface driver and firmware package
Delivered largely through Windows Update
No separate third-party codec installer expected
Surface audio arrives through Surface driver and firmware packages and Windows Update.
Device Driver Guide does not host, mirror, or alter driver files. The official-source citations below are maintained separately from this reference material and never point to third-party mirrors.
Where the correct package usually comes from
For onboard audio the correct source depends on how you got the machine. If you own a laptop or a prebuilt desktop, the package your computer maker validated for that model is usually the right one, because it carries the speaker tuning and firmware assumptions for that chassis. Go to that brand's support site and search by model or serial number. If you built the desktop yourself, the audio package lives on your motherboard model's support page under its own board revision.
Discrete sound cards and professional interfaces may use a driver, control application, and firmware tool published by the device maker; simple USB headsets may instead use the Windows USB audio class driver. Use the exact model's download page and install only the components it lists, because software and firmware availability differs by generation.
The class driver already inside Windows is a legitimate recovery option. It may restore basic playback and recording so you can get sound back quickly, and for a simple USB headset it may be all you ever need. Reach for a vendor package when you want jack sensing, tuning, or low latency.
Official sources and citations
These links serve two different purposes. A manufacturer support selector helps you find an exact model, but does not prove that a package or feature exists for every product in a family. Claim-specific documents explain the cited technology, requirement, lifecycle, or bounded package example. In either case, check the publisher domain, exact model and hardware revision, operating-system release, supported-products list, and package notes before making a change.
Microsoft Lifecycle: Lifecycle documentation for Windows 10 Home and Pro; separately governed editions and servicing channels can have different dates.
Microsoft Surface: Use this publisher-maintained page to match the exact Microsoft Surface model and operating-system release before selecting a package.
Realtek: Use this publisher-maintained page to match the exact Realtek model and operating-system release before selecting a package.
Device Driver Guide is an independent reference, not a repair or technical-support service. It does not host or mirror installers and receives no payment for these links. A named-model package example applies only to the systems and operating systems on that publisher page; it is not a recommendation to install the package across a family. Report a moved or incorrect link through the correction form.
Audio & Sound reference tables
Where the audio driver should come from
Device
Best source
What you gain
What the generic driver misses
Onboard codec on a laptop or prebuilt
PC or laptop maker support site
Speaker tuning matched to the chassis
Jack sensing and model-specific tuning
Onboard codec on a self-built desktop
Motherboard model support page
Correct jack layout for the board
Front-panel retasking and console app
Discrete sound card
The card maker's full package
Mixer, effects, and headphone gain
The control panel entirely
USB recording interface
The interface maker's driver
Low-latency path and input gain
The low-latency recording path
USB headset or speakerphone
Windows built-in class driver
Basic playback and mic the moment it plugs in
Only an optional equalizer or sidetone
Monitor or TV speakers over HDMI
The graphics driver
Sound down the display cable
Nothing here belongs to the audio codec
Which source is right depends on whether the device is onboard, external, or a display output.
Symptom to likely cause to first safe step
Symptom
Likely cause
First safe step
No sound after a Windows feature update
Tuned driver swapped for a generic one
Reinstall the OEM or maker package, then reboot
Front headphone jack ignored
Jack sensing off or header unseated
Enable jack sensing in the vendor console
Crackling or popping playback
Too many enhancements or a small buffer
Turn off audio enhancements, then raise the buffer
Microphone very quiet
Low input level or heavy noise suppression
Raise the input level, ease the suppression
Vendor control panel will not open
Driver and app are different generations
Reinstall the full package, not a driver-only file
No sound over HDMI
Display audio needs the graphics driver
Update the GPU driver, then pick the display output
Common audio complaints matched to what usually causes them and the least risky thing to try first.
Onboard codec vs discrete card vs USB interface
Trait
Onboard codec
Discrete card
USB interface
Where it lives
Soldered to the board
PCIe slot inside the case
External box on a USB cable
Typical driver source
PC or motherboard maker
The card maker
The interface maker
Class driver fallback
Basic playback only
Basic playback only
Often works class-compliant
Best fit
Everyday listening
Gaming effects and headphone drive
Recording and low latency
Latency for recording
High
Moderate
Low over the maker's path
How the three common audio paths differ for a typical Windows user.
When updating helps, and when it does not
Audio drivers do not need frequent updates the way graphics drivers do. If sound works, jacks are detected, and the microphone is clean, there is little reason to change anything. A stable audio stack that you leave alone will usually keep working across months of use, and each reinstall carries a small risk of resetting your tuning or breaking a control panel.
Update when you have a concrete symptom: a jack that stopped being detected, crackling that appeared after a Windows feature update, a microphone that went silent, or a new recording interface that needs its own driver. Feature updates to Windows are the most common trigger, because they sometimes swap your tuned driver for a generic one and quietly drop the extras.
When changing an audio driver, compare Windows Update with the exact OEM or device-maker support page. Either path may be appropriate for a listed model; optional tuning and applications must be verified from the package contents rather than assumed.
Before you install anything
Note your exact device name from Device Manager and, for a laptop or prebuilt, your model or serial number.
Create a restore point or at least confirm you can reach the maker's support site again if the install goes wrong.
If the maker's instructions call for removing an earlier audio package or control application, follow that sequence; do not assume every in-place update requires an uninstall.
Close any recording or conferencing software so no application is holding the device open during the install.
For a USB interface or headset, follow the model's setup instructions about when to connect it; connection timing differs among installers.
How to update audio & sound drivers
1
Confirm the audio device and its maker
Open Device Manager, expand 'Sound, video and game controllers', and note the exact device name. For onboard audio on a laptop or prebuilt PC, plan to download from the computer maker rather than the codec vendor.
2
Choose the right source
For integrated audio, use the exact PC or motherboard support page. For a discrete card or USB interface, use the device maker's exact-model page and install only the driver, application, or firmware component it lists for your Windows release.
3
Follow the maker's replacement sequence
Do not automatically remove a working driver. If the exact package instructions require uninstalling an earlier version, follow them and note whether Device Manager offers driver removal.
4
Follow the device's connection timing
Run only the applicable installer and connect, disconnect, or restart the external device when its model-specific instructions say to do so.
5
Set the default device and sample rate
Open Windows Sound settings, choose the correct output and input devices, and in the device properties confirm a sample rate your hardware supports (for example 48000 Hz). Recording interfaces set this in their own control panel.
6
Reboot and verify
Restart the PC, then play test audio and check the microphone level. Confirm the vendor control panel loads if your device includes one.
Confirm the install actually worked
Play a test sound and confirm it comes from the intended output device rather than an HDMI display or the wrong speaker.
Speak into the microphone in Sound settings and watch the input level meter respond.
Plug a headset into the front-panel or side jack and confirm Windows detects the change if your hardware supports jack sensing.
Open the vendor control panel, if your device has one, and confirm it launches and matches the driver generation.
Check Device Manager shows the audio device without a yellow warning icon.
Undoing a bad audio & sound install
If sound breaks after an update, start in Device Manager: open the audio device, go to the Driver tab, and use "Roll Back Driver" if the option is available. That returns you to the previous version without hunting for a file, and it is the cleanest first move.
If rollback is grayed out, uninstall the device with the option to remove its driver software, then reboot. Windows will load its built-in class driver, which at minimum may restore basic playback so you are not stuck in silence. From there you can reinstall the known-good OEM or device-maker package.
For a USB interface or headset, unplug it, uninstall its software, reboot, then reconnect and reinstall so the device enumerates fresh under the driver you actually want.
A Windows feature update can silently replace a tuned OEM driver with a generic one, dropping jack sensing and speaker tuning.
Installing a driver-only file when the control panel is a separate app leaves the two mismatched and the panel unable to open.
Enabling multiple audio enhancements at once can cause crackling or distortion that looks like a hardware fault.
Running two audio control panels from different vendors at the same time can produce conflicting mixer behavior.
Choosing a sample rate the hardware does not support can mute the device entirely until you set a valid rate.
Leaving USB power management on can let Windows suspend an interface mid-session and cause dropouts.
Mistakes to avoid with audio & sound
Downloading a generic codec driver for a laptop instead of the maker's build, which drops the model's speaker tuning.
Installing a driver-only file when the control panel is a separate app, leaving the panel unable to open.
Stacking several audio enhancements at once, which causes crackling that looks like a failing speaker.
Setting a sample rate the hardware does not support, which mutes the device until a valid rate is chosen.
Running two vendor audio panels together, which produces conflicting mixer behavior.
Leaving USB selective suspend on for an interface, so Windows suspends it mid-session and audio drops out.
Blaming the audio codec for silent HDMI output when the graphics driver actually owns that path.
Connecting the interface before installing its driver, so it enumerates under the wrong software.
Situations readers arrive with
I updated to a new Windows build and now my laptop speakers sound thin and flat.
A feature update often replaces the tuned OEM audio driver with a generic one, which drops the speaker tuning. Go to your laptop maker's support site, enter your model or serial number, and reinstall the audio package they list. Reboot, then confirm the vendor console loads before judging the sound again.
I plugged headphones into the front jack of my desktop and nothing switched over.
First open the vendor audio console and confirm jack sensing is enabled and the port is assigned to headphones. If the console shows the jack as empty, the front-panel header may be unseated on the motherboard. Reseat that header, then retest the jack.
My new USB recording interface has audible delay when I monitor myself singing.
Install the interface maker's own driver and control application before opening your recording software. In your recording app, select the maker's dedicated driver rather than the generic Windows one, then lower the buffer size gradually until the delay is gone but playback stays clean. Direct hardware monitoring on the interface avoids the delay entirely if it is offered.
The audio control panel that came with my PC suddenly refuses to open.
This usually means the driver and the control app fell out of step, often after a partial update. Reinstall the complete audio package from your PC maker's support site rather than a driver-only file, since the two pieces must match generations. Reboot afterward and open the panel again.
I connected my PC to my TV over HDMI but there is a picture and no sound.
Audio over HDMI is carried by the graphics driver, not the onboard codec, so start there. Update your Intel, AMD, or NVIDIA display driver, then in Windows Sound settings pick the TV as the default playback device. Make sure the TV input is not muted on its own remote.
Symptom-by-symptom troubleshooting
No sound after a Windows feature update
Windows may have replaced your audio driver with a generic one. Reinstall the OEM or device-maker package, then reboot. If the device shows a yellow warning in Device Manager, uninstall it and rescan for hardware changes.
Front-panel headphone jack is not detected
Enable jack sensing in the vendor audio control panel, confirm the front-panel connector is seated on the motherboard header, and verify the jack retasking settings assign the port to headphones.
Microphone works but is extremely quiet
In Sound settings, open the input device properties, raise the level, and disable aggressive noise suppression if speech sounds thin. On laptops, an OEM audio package often exposes a dedicated microphone boost.
Crackling, popping, or dropouts during playback
Lower audio enhancements, and for USB interfaces increase the buffer size in the maker's control panel. Disable exclusive-mode applications and check for a USB power-saving setting that suspends the device.
No audio over HDMI or DisplayPort
HDMI and DisplayPort audio is provided by the graphics driver. Install the current GPU driver from Intel, AMD, or NVIDIA, then select the display as the default playback device.
USB audio interface has high latency in recording software
Select the maker's device-specific recording driver inside your application, then reduce the buffer size gradually until playback remains stable.
Vendor audio control panel will not open
Confirm that the application supports the exact device, driver branch, and Windows release. Use the maker's documented repair or reinstall sequence; the app may be a separate download rather than part of a full package.
Only one channel plays or balance is off
Reset the left/right balance in the device properties, confirm a stereo output format, and test with a different cable or port to rule out a hardware fault.
Frequently asked questions
Should I download onboard audio from the codec vendor or my PC maker?
For a laptop or prebuilt desktop, start with the exact system support page; for a self-built PC, use the exact motherboard page. Install only a package that lists the model, hardware, and Windows release.
Is the audio driver built into Windows good enough?
A Windows class driver can provide basic playback or recording for compatible hardware. Optional jack detection, tuning, and control applications vary by system, so check the exact OEM package contents rather than treating any package as a full-function guarantee.
Why does my USB headset work without installing anything?
A USB headset that implements a supported USB audio class can use Windows class support. Equalizer, sidetone, lighting, and companion-app availability are separate model-specific features.
Do I need a driver for a recording interface, or is it plug and play?
It depends on the exact interface, generation, Windows release, and workflow. Check the maker's supported-device list for a device-specific recording driver, control app, mixer, or firmware tool, and follow that model's connection sequence. Do not assume all interfaces expose all four.
Where does HDMI audio come from?
Audio over HDMI or DisplayPort is handled by the graphics driver, not the onboard audio codec. Keep your Intel, AMD, or NVIDIA display driver current and select the display as your output device.
Will a discrete sound card and my onboard audio conflict?
They can coexist, but you should set the intended output as the Windows default. If you no longer use onboard audio, some users disable it in firmware to avoid confusion.
How do I roll back a bad audio update?
In Device Manager, open the audio device properties, go to the Driver tab, and choose 'Roll Back Driver' if it is available. Otherwise uninstall the current driver and reinstall the known-good package from your PC or device maker's support site.
Terms used on this page
Codec
The chip that converts between digital audio and the analog signal on your jacks; on most PCs it is soldered to the motherboard.
Jack sensing
The hardware's ability to detect when something is plugged into a port and reassign it, for example switching output to headphones.
ASIO
Audio Stream Input/Output (ASIO), a low-latency driver protocol used by recording software for direct access to compatible audio hardware.
Sample rate
How many times per second audio is measured, such as 48000 Hz; the device and Windows must agree on a supported value.
Buffer size
How much audio is held before it is played or recorded; smaller buffers lower latency but raise the risk of dropouts.
Class driver
A generic driver built into Windows that gives basic sound without vendor tuning or a control panel.
Device Driver Guide stores a local consent preference to remember your choice. Replit Project Analytics may measure visits and selected site interactions. These local choices do not turn hosting analytics on or off. Custom events exclude form entries and other free-form content. No advertising scripts are active. Read the Cookie Policy.
