What this driver does
The HDMI display audio driver handles the sound that travels down a display cable rather than through the motherboard's analogue jacks. Both HDMI and DisplayPort are designed to carry multichannel audio embedded in the same link that carries video, so a single cable to a television, monitor, or audio-video receiver delivers both the picture and the soundtrack. This driver is what makes that embedded audio path visible to Windows as a usable output. Crucially, this driver lives inside the graphics driver package, not the motherboard audio stack. The display controller on the GPU is what packetises the audio and interleaves it into the HDMI or DisplayPort data islands between video frames, so the sound is generated and timed by the graphics silicon. That is why updating or reinstalling the graphics driver almost always replaces the HDMI audio component at the same time, and why a GPU driver fault can silence the display audio endpoint. To Windows the result is one or more additional audio endpoints, listed with the name of the connected display or receiver rather than a codec. Each connected sink that reports audio capability in its EDID appears as its own endpoint, which is how you can send sound to a TV on one output while a monitor on another output stays silent. The endpoint carries the same volume and default-device behaviour as any other Windows output. The sink's own capabilities, read from its EDID audio data block, decide what the driver can offer. A basic monitor may accept only stereo, while an AV receiver advertises multichannel and compressed bitstream formats such as Dolby or DTS. The driver negotiates a format both ends support, and when a bitstream passthrough option is enabled it forwards the compressed stream untouched for the receiver to decode.
Why updating matters
The single most frequent HDMI audio complaint is the endpoint simply vanishing, and stale driver state is a leading cause. When the graphics driver is out of step with Windows, or a display's EDID audio block is misread, the display audio endpoint disappears from the sound list and the TV falls silent. Refreshing the GPU package, which carries this driver, restores the enumeration and the endpoint reappears. Because the display audio driver is bundled with the graphics driver, it inherits both the fixes and the regressions of GPU releases. A new graphics build can repair a bitstream-passthrough bug that garbled Dolby output, or it can accidentally break audio on one HDMI port until the next revision. Keeping the pairing current, and knowing how to roll back, is how you stay on the good side of that trade. Feature support also moves forward through updates. Newer formats, higher channel counts, and correct handling of AV-receiver handshakes over HDMI arrive in driver revisions, so an older build may refuse a format your receiver clearly supports. Where multichannel or lossless passthrough matters, the driver version genuinely determines what you can send. The measured approach is to update the graphics package when HDMI audio is missing, silent, or refusing a format, verify sound on the affected display, and roll back if a new build breaks a port that previously worked. Certified graphics packages come through Windows Update, and the freshest builds live on the support page for your exact PC or graphics card model. This HDMI audio reference hosts no graphics package files and links to no vendor pages.
Signs a driver may be failing
- The connected TV or receiver disappears from the Windows sound output list even though the picture is fine
- Sound plays through the PC's own speakers instead of the HDMI display because the wrong endpoint is default
- The HDMI audio endpoint is greyed out and marked Not plugged in despite a working video signal on the cable
- Multichannel or Dolby bitstream passthrough to an AV receiver fails and falls back to stereo or silence
- Audio and video drift out of sync on the display because the embedded audio timing is not tracking the frames
- The endpoint reappears only after reinstalling the graphics driver, since HDMI audio ships inside the GPU package
How it fits into the OS stack
Drivers operate in the background, serving as translators. Here is where the HDMI display audio driver sits between your apps and the hardware.
Distribution comparison
Before you start
"Only install drivers from your operating system's update tool or the manufacturer's official support page."
Where this driver comes from
Drivers for HDMI display audio driver typically reach your PC through one of three routes: shipped natively with the Windows operating system, delivered dynamically through system updates, or published directly by the hardware manufacturer for your specific model.
To ensure system stability, always allow your OS to handle baseline generic drivers. If you are experiencing performance issues or require advanced control panels, identify the exact model of your hardware and consult the device manufacturer's dedicated support resources.
Fixing installation problems
Set the HDMI display as the default output
Open Settings, System, Sound, and pick the connected display or receiver from the output list. Windows often leaves the PC speakers as default after a display is connected, so simply selecting the HDMI endpoint restores sound to the TV.
Show and re-enable hidden endpoints
In the Sound control panel Playback tab, right-click and enable Show Disabled Devices and Show Disconnected Devices. A greyed-out HDMI endpoint can be re-enabled here, which revives an output Windows had marked Not plugged in.
Re-scan the display audio device
In Device Manager expand Sound, video and game controllers, find the display audio controller, and choose Scan for hardware changes after unplugging and replugging the cable. This forces Windows to re-read the sink's EDID audio block and rebuild the endpoint.
Reinstall the graphics driver package
Because display audio lives inside the GPU driver, uninstall the display adapter with the delete-software option and reboot. Windows reloads the graphics stack and its bundled HDMI audio component together, which restores a vanished endpoint most reliably.
Match the audio format to the sink
In the HDMI endpoint's Properties, on the Advanced tab, set a format the display supports, and on the Supported Formats or Spatial sound tab enable or disable bitstream passthrough to match your receiver. A format the sink rejects produces silence.
How to uninstall or rollback
Step 1
Step 2
Step 3
Step 4
Step 5
Safety Warning
How audio rides the display link
HDMI and DisplayPort were designed from the start to carry sound as well as picture. Between the active video regions of each frame there are blanking intervals, and the display controller inserts audio into those gaps as data islands, small packets that interleave the sample stream with the video without disturbing it. The result is that one cable delivers a complete audiovisual signal to a television, monitor, or receiver. Because this packetising happens in the GPU's display controller, the audio is generated and timed by the graphics silicon rather than the motherboard codec. The driver that manages it is therefore part of the graphics package, and it presents the embedded path to Windows as an ordinary sound endpoint named after the connected display. Everything the endpoint can do is bounded by what the display controller and the cable's bandwidth allow. This architecture explains several everyday behaviours. A GPU driver update replaces the audio path, a graphics fault can silence it, and a cable that carries video perfectly can still lose audio if the data islands are corrupted. Understanding that the sound lives inside the video link is the key to troubleshooting why HDMI audio behaves differently from the analogue jacks on the case.
Endpoint enumeration and EDID audio capability
Each display or receiver you connect advertises what audio it can accept in a display-identification audio block, the same descriptive structure that carries its video timings. The display audio driver reads this block and creates a Windows endpoint only if the sink reports audio capability, which is why a speaker-less monitor produces no endpoint at all while a television or receiver does. The endpoint takes the sink's name so you can tell several outputs apart. The identification data also declares the formats the sink supports, from basic two-channel stereo up to multichannel layouts and compressed bitstreams. The driver negotiates a format both the GPU and the sink accept, defaulting to stereo when it cannot confirm anything richer. This negotiation is why an AV receiver can offer surround while a simple monitor offers only stereo through the very same driver. When that data read fails, because of a marginal cable, a passive adapter, or a docking station that rewrites the block, the endpoint either does not appear or shows as Not plugged in. Replugging the cable and scanning for hardware changes rebuilds the endpoint from a clean read, which is the standard fix for an HDMI audio output that Windows has lost track of.
Multichannel output and bitstream passthrough
There are two ways to send surround sound over HDMI, and they behave differently. In the first, the PC decodes the audio and sends the individual channels as uncompressed samples, letting Windows and the driver mix and process them; this is simple and always works where the sink accepts multichannel. In the second, bitstream passthrough, the PC forwards the compressed Dolby or DTS stream untouched for the AV receiver to decode itself. Passthrough is powerful because it lets a capable receiver apply its own decoding and post-processing, but it is fussier. The format must be enabled on the endpoint, the receiver's input must be configured to accept it, and the driver build must support the negotiation. If any link in that chain is wrong, the receiver receives a stream it cannot interpret and the result is silence rather than a graceful fallback. Choosing between them depends on your gear. For a television with built-in speakers, uncompressed multichannel or plain stereo is the reliable path. For a home-cinema receiver, passthrough unlocks the full surround formats, provided both the driver version and the receiver agree on what to send. When passthrough fails, testing with it disabled quickly confirms whether the fault is the format negotiation or something else.
Troubleshooting lost or silent HDMI audio
Silent HDMI audio splits into two questions: is the endpoint present, and is it selected. First check Settings, System, Sound; if the display is listed but not chosen, simply selecting it as the default output restores sound, because Windows frequently keeps the PC speakers as default after a display is connected. This routing step solves a large share of complaints before any driver work. If the endpoint is missing or greyed out, the problem is enumeration. Enable Show Disabled and Disconnected Devices to reveal a hidden endpoint, then force a fresh EDID read by replugging the cable and scanning for hardware changes. A marginal or non-certified cable that carries video but loses the audio data islands is a common cause, so swapping to a known-good cable is a fast test. When the endpoint still will not return, the fault sits in the graphics package that contains the display audio driver. Reinstalling the graphics driver replaces the audio component and rebuilds the endpoint, while rolling the graphics driver back reverses a regression from a recent GPU update. Because this audio path has no standalone package, every deeper fix runs through the graphics driver rather than a separate audio installer.
Where this driver comes from
The HDMI display audio driver reaches your PC by the same three routes as the graphics driver that carries it, because the two are never separated. The first route is the driver Windows ships with. A fresh Windows install includes inbox graphics drivers whose bundled display audio component can drive a connected TV or receiver at a basic level, so HDMI sound often works before any vendor package is present. The second route is Windows Update. Once online, Windows matches the GPU's hardware identifiers and offers a WHQL-certified graphics package, and that package contains a tested display audio component. Installing the certified graphics build therefore maintains HDMI audio automatically, which makes Windows Update the safest everyday source, at the usual cost of trailing the newest format and handshake fixes. The third route is the hardware maker publishing a graphics driver for a specific model. Your PC or graphics card manufacturer validates the package, including its display audio component, against one exact configuration and posts it on that model's support page; this is where the freshest multichannel and receiver-handshake support appears. Because there is no standalone HDMI audio installer, you always obtain this path through the model's graphics driver. This site describes all three routes in words only, hosts no driver files, and links to no vendor download pages, so identify your exact model and take any manual package from the maker's own support page.