Black Screen With Working Audio: The Video Decoder That Never Loaded
Audio plays and the picture stays black on Windows. Which video codecs cause it, how HEVC and 10-bit files fail, and what to install instead.
MKV, MP4, AVI. Identifies what is inside the file.
Separates the container into video, audio and subtitle tracks.
Turns a compressed track into frames or samples.
Draws frames, outputs audio and paints subtitles.
Sound running normally over a black frame is the mirror image of a silent video, and it localises the fault just as precisely. The file opened, the splitter separated the tracks, and the audio branch decoded to the end. The video branch produced nothing that the renderer could draw.
Which video formats actually cause this
Most black-frame reports involve one of three things. HEVC, also called H.265, is the leading cause on current machines: it is standard in phone recordings and in modern rips, and several Windows installations have no decoder for it until an extension is added. H.264 almost never fails on its own, because support is old and universal, so a black H.264 file usually turns out to be a 10-bit encode rather than an ordinary one.
The third group is the legacy set. XviD, DivX and MPEG-4 Part 2 files from the early 2000s need a decoder that current Windows does not ship, having no reason to. Those files are the reason codec packs existed, and they are still the files most likely to arrive with nothing on the system able to read them.
Bit depth is the quiet one
A 10-bit encode stores ten bits per colour channel instead of eight. It is common in anime releases and in high quality rips, and it changes the pixel format the decoder has to hand onward. Hardware decoders built before 10-bit was widespread simply refuse the stream. Software decoders accept it and cost more processor time.
The symptom is distinctive: the file plays on a recent machine, shows nothing on an older one, and nobody involved changed any setting. Disabling hardware acceleration in the player is the test. If the picture appears once decoding moves to the processor, the format was never the problem and the graphics chip was.
Reading the filter chain
The useful panel is the player’s own. MPC-HC lists the active filter chain under File and then Properties, and the entry to look for is the video decoder. Three readings are possible and each points somewhere different.
A named video codec with no decoder attached means the format is unsupported, and something has to be installed. A decoder that is loaded and running with the frame still black means the fault is in the renderer, not the decoder, and installing another codec will change nothing. A chain that stops before the video track appears at all means the splitter never separated it, which is a container problem rather than a codec one, and is more likely on MKV than on MP4.
Fixing it once
For a viewer, a player with internal decoding ends the problem: VLC and mpv both carry libavcodec and will draw HEVC, 10-bit and the whole legacy set without consulting Windows. Nothing is installed system-wide and nothing can conflict.
For a machine that has to keep using DirectShow, LAV Video covers every format listed above from a single install. It replaces what a codec pack bundled across a dozen components, and because it is one component, no second decoder is left arguing with it over who handles H.264.
Two moves make things worse and both are common. Installing a second pack alongside an existing one creates exactly the merit-value competition that produces green frames and intermittent failures. And installing a pack built for Windows XP on Windows 10 or 11 puts filters written for a different video pipeline in front of one that already worked.
When the renderer is the culprit
Renderer faults look identical from the outside and need a different fix. Remote desktop sessions cannot use hardware renderers at all, so a file that plays at the machine and shows black over RDP was never a codec issue. A graphics driver that is very old, or that failed to load after an update, takes the renderer down while leaving decoding intact. And players configured for a renderer the hardware does not support fall through to nothing rather than to a default.
The check is to switch the player to its most basic video renderer and try again. If the picture appears, the decoder was working the whole time and the fix belongs in the driver or the player settings.
Common questions
What does a green or pink picture mean instead of a black one?
Coloured artefacts mean a decoder is running and getting the pixel format wrong, which is a different fault from a decoder that is absent. It usually points at two decoders competing for the same format, or at hardware acceleration failing on a driver that reports support it does not have. Turning acceleration off is the fastest way to confirm which.
Why do HEVC files fail more often than H.264 ones?
H.264 support has been in Windows for many years and in every graphics driver made since. HEVC arrived later, was licensed differently, and on several Windows versions requires an extension that is not present by default. A file that plays everywhere except one machine is often an HEVC file meeting a machine that never got that extension.
Does a black picture mean the file is damaged?
Rarely. A truncated download usually plays and then stops at the point where the data ends, and a corrupt header usually prevents the file opening at all. Sound that runs to the end with no picture at any point is a decoder problem, because a damaged video track would fail partway rather than uniformly.
What is 10-bit video and why does it break older setups?
It stores each colour channel in ten bits instead of eight, which raises quality and changes the pixel format the decoder outputs. Hardware decoders built before it was common reject it, and software decoders handle it fine but more slowly. It is the most common reason a file plays on a new machine and shows nothing on an older one.
Can the video renderer rather than the decoder be at fault?
Yes, and the tell is that the panel shows the decoder running. Renderers fail on remote desktop sessions, on machines with a broken or very old graphics driver, and when a player is set to a renderer the hardware does not support. Switching the player to a basic renderer confirms it in one step.
Published