Protected Video Black Screen With Sound? HDCP Handshake, Protection Version & Display-Chain Diagnosis Guide

Key Takeaways
Protected video plays black with sound while the desktop and games look normal usually points to the content-protection handshake, not a broken graphics card. This guide explains the four decision points — content, browser decryption, HDCP version, and the display chain — then walks through eight diagnostic steps to find which link fails.
What This Problem Is — and What It Is Not
Picture the scene: you sit down to watch a film on a streaming service. The title loads, the sound starts, the subtitles appear — and the video area itself is completely black. Or instead of a picture you get a content-protection message such as "HDCP Unauthorized. Content Disabled." You switch to a game, and the game looks perfect. You open the desktop, and every icon, window, and wallpaper is exactly as it should be. You play a local video file, and it plays normally. Only the protected stream is black.
That is the problem this guide covers, and it is worth defining precisely, because several lookalike problems need completely different handling. Four conditions must all be true before the steps below apply:
- The problem appears only with protected streaming video — for example, copyrighted films and series on services such as Netflix or Disney+.
- The video area stays black, or a content-protection error message appears, while the sound keeps playing normally.
- The desktop, games, the browser in general, local video files, and other unprotected video all look normal on the same computer, the same cable, and the same display.
- The black screen is persistent. It stays black until you change the content, change a setting, or change something in the display chain. It does not clear by itself after a second or two.
The word "persistent" matters. A picture that goes black for a second or two and then comes back by itself, while the game and the sound carry on, is a brief renegotiation — a different problem, with a different diagnosis. This guide is about the black screen that does not recover on its own. The contrast between protected and unprotected content is the single most useful piece of evidence in the whole diagnosis, and it should be established before anything else is changed. If the same computer, cable, and display can show a game perfectly and then go black the moment a protected stream starts, the display output itself is working. Something in the protection path is not.
This guide also assumes a direct connection: the graphics card is connected to the display or television by a single cable, with no receiver, amplifier, capture card, splitter, or switch in between. If the picture is normal when connected directly and only goes black when a receiver or amplifier is added to the chain, that is a different problem — the extra device in the middle is part of the diagnosis. If the picture only goes black when a capture card is in the chain, that is different again, because a capture card is designed not to accept an encrypted input. And if the picture looks perfectly normal to your eyes and only turns black in a screenshot or a shared screen, the direction is reversed: the screen you are looking at is fine, and the capture layer cannot read the protected path. None of those is this guide.
Why does the content contrast matter so much? Because protected video travels a separate path from everything else on the screen. The desktop, games, and ordinary video do not need to complete a content-protection handshake before they appear. Protected video does. When the handshake fails, the picture is withheld while the sound — which travels a different route — keeps playing. That is why "sound but no picture, only on protected video" is not a contradiction, and not a sign of a dying graphics card. It is the signature of a protection-layer failure, and the diagnosis that follows is about finding which link in that layer is failing.
A note on language used in this guide: the four decision points, the eight steps, and the six misconceptions are the whole structure. Every section below refers back to them, and the numbers stay the same throughout — four decision points, eight steps, six misconceptions — so that a result at any step can be traced back to the decision point it tests.
The Four Decision Points
Whether protected video plays or goes black is decided by four decision points working together. None of them acts alone, and a failure at any one of them can produce the same black screen. Understanding all four before touching anything is what keeps the diagnosis from going in circles — and from replacing hardware that was never the problem.
Decision Point One: The Content Layer — Protected or Unprotected
Protected content — copyrighted films and series on streaming platforms — travels a separate protection path. Before it is shown, a handshake has to be completed between the playback device and the display. Unprotected content — the desktop, games, local video files, and ordinary web video — does not travel that path and does not need that handshake.
This is why "the desktop is normal, the protected stream is black" is useful evidence rather than a puzzle. Change the content, and the result changes. That points at the protection layer, not at the display output layer. A graphics card that could not produce a picture would fail on games and the desktop too. A display with a faulty panel would fail on everything. When only protected content fails, the output layer has already passed its test, and the investigation should stay on the protection path.
The practical consequence is simple: every test in this guide needs a control. The control is unprotected content on the same machine, cable, and display. If the control has a picture and the protected stream does not, the problem is in the protection layer, and the next steps narrow down which part of it. If the control is black too, leave this guide and follow a general no-signal or black-screen diagnosis instead, because the problem is no longer specific to protected content.
Decision Point Two: The Browser and DRM Layer — Widevine CDM
A browser playing a protected stream relies on a content decryption module — in most browsers, Widevine CDM — to obtain the licence that unlocks the stream. If that layer has a problem, the symptom is usually an error code rather than a black screen. An outdated module, a protected-content setting that has been turned off, or a licence that cannot be obtained can produce errors in the range of Netflix M7701-1003 and similar codes.
An error code and a black screen are two different signals, and they should not be mixed together. An error code leans towards the browser and DRM layer. A black screen with sound leans towards the display-chain handshake layer. Treating an M7701-1003 type error as a handshake failure would send the diagnosis down the wrong path — swapping cables and display ports for a problem that lives in the browser. Treating a black screen as a browser problem would waste time updating modules when the display chain is the part that cannot complete its handshake.
The browser layer also includes the choice of playback vehicle: a different browser, or the streaming service's own dedicated app, can behave differently from the browser you started with. That difference is itself diagnostic. If the same title plays in one browser or app and goes black in another, the display chain has just been shown to work, and the problem sits in the first browser or app. If every vehicle goes black on the same title, the problem sits further down the chain.
Decision Point Three: The HDCP Version Chain — 1.4 or 2.2
HDCP, the content-protection protocol used between the playback device and the display, exists in different versions. Protected 4K streaming generally requires HDCP 2.2 or newer along the whole chain. A chain that only supports HDCP 1.4 may still play protected video at 1080p, but at 4K it may drop to a lower quality or refuse to play at all. The exact behaviour varies by platform, and platform behaviour changes over time, so the platform's own message on screen is the authority for what it requires at that moment — this guide describes the general requirement, not a fixed promise about any one service.
The version chain follows a weakest-link rule. The graphics card, the cable path, any device in the middle, and the display's input port each contribute their own supported version, and the whole chain can only use the oldest version among them. Any one link that only supports an older version holds the entire chain back to that older version. That is why "1080p works, 4K does not" is a diagnostic result, not a bandwidth complaint. Bandwidth trouble looks different: it shows up as intermittent black flashes, or as a picture that only stabilises after settings are lowered. A clean refusal at 4K with a clean picture at 1080p points at the version chain.
This also explains why a setup can work for months and then stop working on a new title. A service may start offering a title in 4K with a stricter protection requirement, or a display's firmware or a driver update may change which version is negotiated. Nothing has broken. The chain that was good enough for 1080p is no longer good enough for the new requirement, and the symptom appears exactly at the point where the requirement changed.
Decision Point Four: The Display Chain — Direct or Through Devices, Which Port, Which Cable
The display itself is part of the chain, and its input ports are not necessarily equal. On the same display, one HDMI port may support HDCP 2.2 while another only supports HDCP 1.4. Moving the cable from one port to another can therefore change the result completely, even though nothing else has changed. This is one of the most commonly missed causes of protected-video black screens, because it is natural to assume that every port on one display behaves the same way. They do not always.
Every device in the middle of the chain — a dock, a switch, a splitter, an adapter, a receiver — adds another authentication step. Any one of them can be slow to authenticate, or can fail to support the version the stream requires, and the whole chain breaks at that point. That is why the direct-connection test in the steps below is so decisive: removing every middle device and connecting the graphics card straight to the display with a single cable either restores the picture, which points at one of the removed devices, or leaves it black, which clears them all at once.
The cable itself needs care in how it is judged. A cable that "works" — in the sense that it carries a desktop picture — is not necessarily a cable that supports the HDCP version the stream requires. HDMI version labels such as HDMI 2.1 or HDMI 2.0 describe transmission capability. They do not prove HDCP capability for every device or every path. "The cable works" and "the cable is compliant" are two different claims, and only the second one matters for protected video. A cable that is too long, damaged, or built to an older specification can also authenticate slowly or unreliably, which is why the cable test in the steps below uses a shorter cable with a certification mark rather than simply a more expensive one.
Taken together, the four decision points give the diagnosis its shape. The content layer tells you whether the problem is in the protection path at all. The browser and DRM layer tells you whether the licence and decryption side is working. The HDCP version chain tells you whether the whole chain is new enough for the resolution being requested. And the display chain tells you whether every physical link — port, cable, and middle device — can complete its part of the handshake. Each of the eight steps below tests one of these points, in an order that clears the cheapest and most informative tests first.
The Eight Diagnostic Steps
Work through these steps in order, and change only one thing at a time. If you change the resolution, the browser, the cable, and the display port all at once, and the picture comes back, you will not know which change did it — and you will not know which one to fix if the problem returns. One variable at a time, and the same protected title retested after each change.
Step 1: Define the Problem
Write down which platform and which title are affected, whether you are using a browser or the service's dedicated app, whether the symptom is a black screen or an error message, whether the sound keeps playing, and whether it happens every time you play protected content. Copy the error message word for word if one appears: a message mentioning HDCP leans towards the display chain, while a Widevine or M7701 type error code leans towards the browser and DRM layer. This note is also what you will bring with you if the diagnosis ends at the stop line in Step 8, so make it while the details are fresh. A vague memory of "it went black" is much less useful than a note that says which title, which browser, which message, and whether the sound continued.
Step 2: The Content Comparison
On the same computer, the same cable, and the same display, play a piece of unprotected content — a local video file, the desktop, or a game. If the unprotected content has a picture and the protected content is black, the problem points at the protection layer, and you should continue with the steps below. If both kinds of content are black, leave this guide: the problem is not specific to protected content, and a general no-signal or black-screen diagnosis is the right path instead. This comparison is the single most important test in the guide. It takes a minute, it costs nothing, and it prevents the most common mistake in this whole area — treating a general display failure as a protection failure, or the other way round. A game that plays well and protected video that goes black is itself a clue: the clue is the contrast.
Step 3: The Resolution Comparison
Lower the protected content to 1080p, turn HDR off, and set the refresh rate to 60Hz, then try the same title again. 1080p SDR at 60Hz is a conservative test mode, and it helps separate a version-chain problem from other kinds of failure. If 1080p works and 4K does not, the result points at the HDCP version chain — Decision Point Three. The chain can support the older version but not the newer one, and the resolution at which it stops working marks the boundary. If 1080p is black too, the problem is not only about the 4K requirement, and you should continue downwards. Record the result either way: "1080p works, 4K does not" and "1080p is black too" lead to different conclusions, and both are useful if the machine later needs in-store inspection.
Step 4: The Browser and App Comparison
Try the same title in a different browser, or in the streaming service's dedicated app. Check that the Widevine Content Decryption Module is up to date — in Chrome-based browsers this is done through the browser's components page, where the Widevine Content Decryption Module can be checked and updated — and check that the browser's protected-content setting is switched on. If the title plays after changing the browser or app, the problem points at the browser and DRM layer, and the display chain has just been shown to work. If it stays black in every browser and app you try, the browser layer is cleared, and the problem sits further down the chain. Remember the distinction from Decision Point Two: an error code such as M7701-1003 belongs to this layer and should be handled here, not written off as a handshake failure. A black screen with sound belongs further down.
Step 5: The Direct-Connection Test
Bypass every device in the middle — dock, switch, splitter, adapter, receiver or amplifier — and connect the graphics card straight to the display with a single cable, then play the same protected title again. If the picture returns after the direct connection, one of the bypassed devices is the suspect, and you can add them back one at a time to find which one breaks it. If the picture is still black on a direct connection, every middle device is cleared at once, and the problem is in the direct chain itself: the graphics card, the cable, the port, or the display. This test is decisive precisely because it removes so much at once. It is also the test that most often gets skipped, because unplugging a dock or a receiver feels like more trouble than changing a setting — but a setting change cannot clear a middle device, and only this test can.
Step 6: The Port Comparison
Change to a different HDMI or DisplayPort input on the display and try again — and change only the port, not the cable at the same time. If the picture returns on the new port, the original port's HDCP support is the suspect: different ports on the same display can support different HDCP versions, and the port you started on may only support the older one. If the picture stays black on every port, the ports are cleared as a group, and the problem lies elsewhere in the chain. The discipline of changing one thing at a time matters most here, because changing the port and the cable together and seeing a picture tells you nothing about which of the two was at fault — and the next time the problem appears, you will not know which one to check first.
Step 7: Driver HDCP Status and the Cable Comparison
For NVIDIA users, open NVIDIA Control Panel, go to Display, and select View HDCP Status, which shows the HDCP status the driver sees and which display it applies to. This is a driver-level view of the handshake, and it is specific to NVIDIA — there is no general Windows command that reports HDCP authentication status, so users of other graphics hardware should not go looking for an equivalent built-in readout. Record what the status shows, then swap in a different cable: one with a certification mark, and a shorter one if possible. Retest the same protected title. A cable change is a comparison test, not a repair in itself — the real repair direction is finding which link in the chain has too old a version or a failed authentication, and the cable is only one candidate among several. Note also that a normal-looking driver status does not by itself clear the display chain. If the status looks normal and the content is still black, record the status result and continue; the status is one piece of evidence, not a verdict. And if the status shows a problem, that result should be recorded too, because it narrows the search considerably.
Step 8: The Stop Line
If you have worked through all eight steps and the protected content is still black or still showing an error, or if the same display behaves the same way on a different computer, stop. Bring the machine in with your notes: which platform, which title, which browser or app, the error message word for word, which steps you tried and what happened at each one, the result of the 1080p comparison, the result of the direct-connection test, and the driver HDCP status. In-store inspection is charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. Guessing further — swapping more cables, reinstalling drivers repeatedly, or changing display settings at random — risks changing things that were never part of the problem, and makes the eventual diagnosis harder rather than easier.
A Quick Comparison: The Four Decision Points at a Glance
| Decision point | What it controls | How to test it | What a pass looks like |
|---|---|---|---|
| Content layer — protected or unprotected | Whether the protection path is involved at all | Play unprotected content on the same machine, cable, and display | Unprotected content has a picture; only protected content is black |
| Browser and DRM layer — Widevine CDM | Whether the licence and decryption side works | Try another browser or the service app; check the Widevine module and the protected-content setting | The same title plays in a different browser or app |
| HDCP version chain — 1.4 or 2.2 | Whether the whole chain is new enough for the resolution requested | Drop to 1080p SDR 60Hz and retest the same title | 1080p plays; the boundary between working and failing is visible |
| Display chain — ports, cable, middle devices | Whether every physical link can complete its handshake | Connect directly with one cable; try another display port; check driver HDCP status and swap the cable | The picture returns on a direct connection or a different port |
Boundaries: Problems That Look Similar but Are Not This One
A diagnosis is only as good as its boundaries. Several nearby problems share a black screen, a stream, or a cable, but each belongs to a different guide, and the steps above will not fix them:
- The picture goes black for a second or two and comes back by itself, while the game and the sound carry on. That is a brief renegotiation, not a persistent failure.
- The picture is normal on a direct connection to the television and only goes black when a receiver or amplifier is added in the middle. The extra device is the story there, not the direct chain.
- The picture goes black when a capture card is in the chain, or recording fails. A capture card is designed not to accept an encrypted input, and that is a different diagnosis from a general display-chain handshake.
- The picture looks perfectly normal to your eyes and only turns black in a screenshot or a shared screen. The direction is reversed: the display you are looking at is fine, and the capture layer cannot read the protected path.
- Video stutters, shows a green screen, or drops frames, while the application itself has not crashed. That is a decoding pipeline problem, not a protection handshake problem.
- The desktop, games, and unprotected content are all black too. That is not specific to protected content, and a general no-signal or black-screen diagnosis is the right path.
- The browser reports an error code such as M7701-1003, saying protected content is not enabled. That belongs to the browser and DRM layer, and it is handled in Step 4 of this guide — it should not be described as a handshake failure.
- Mirroring or casting protected content to another screen goes black. Casting has its own separate protection limits, and it is not the subject of this guide.
The principle is to isolate one thing at a time. A symptom that appears only on protected content, only at 4K, only through one port, or only through one browser is evidence — and the evidence points in different directions depending on when it appears. The eight steps are arranged so that each result narrows the field, and the note you keep as you go is what turns a frustrating black screen into a diagnosis someone else can continue.
Six Common Misconceptions
Misconception 1: "Protected video is black, so the graphics card or the display must be broken."
Both the desktop and games look normal, which already proves the display output layer is working. A faulty graphics card or a faulty display produces missing pictures, corrupted pictures, or crashes across everything — not a clean picture on games and a black screen only on protected video. The problem is in the protection handshake layer, not in the computing or the panel. Replacing the card or the display on this evidence alone would be replacing hardware that has already passed its test.
Misconception 2: "The cable works, so the cable must be compliant."
A cable that carries a picture and a cable that supports the HDCP version a stream requires are two different things. HDMI version labels describe transmission capability; they do not prove HDCP capability for every device or every path. A cable can show the desktop perfectly and still be the link that cannot complete the handshake at the version the stream needs. That is why the cable is tested by comparison in Step 7 — with a shorter, certified cable — rather than assumed good because the desktop looks fine.
Misconception 3: "1080p works and 4K does not, so the bandwidth must be too low."
Bandwidth trouble shows up as intermittent black flashes, or as a picture that only stabilises after settings are lowered. A clean refusal at 4K with a clean picture at 1080p leans towards the HDCP version chain being too old for the 4K requirement. The weakest link in the chain — the card, the cable path, a middle device, or the display port — can only support the older version, and the whole chain drops to that level. The resolution at which playback stops is the clue, not the speed of the connection.
Misconception 4: "Turning off or getting around HDCP would fix it."
HDCP is a content-protection mechanism, not an ordinary user setting to be switched off at will. Getting around the authentication is not a repair, and this guide does not teach or hint at any way of doing so. A setup that cannot complete the handshake needs the failing link found and addressed — a different port, a compliant cable, a middle device removed, or a version mismatch resolved — not the protection itself removed. Any approach that starts from disabling the protection is starting from the wrong end of the problem.
Misconception 5: "A more expensive cable will definitely fix it."
What matters in a cable is its specification and certification, not its price. An expensive cable built to an insufficient specification will fail in exactly the same way as a cheap one, and a fairly priced certified cable can be the right one. Swapping the cable is only one comparison test inside the eight steps, and it should be judged by the result of the retest — did the same title play? — not by what the cable cost. Price is not evidence, and treating it as evidence is how a simple diagnosis turns into a series of unnecessary purchases.
Misconception 6: "Reinstalling the driver will fix it."
A driver reinstall is sometimes the answer to a driver problem, but a protected-video black screen with a normal desktop is not, on its own, a driver problem. Driver resets that cause black screens are usually accompanied by a game ending or by system records of the reset. Before reinstalling anything, the content comparison and the direct-connection test should come first: they are quick, they cost nothing, and they can clear or condemn the protection layer in minutes. Reinstalling a driver blindly, without those comparisons, changes a working layer on a guess, and can leave the real fault — a port, a cable, or a middle device — untouched.
When to Stop and Bring the Machine In
Protected-video black screens are narrowed down by the eight steps above — often at Step 2, where the content comparison proves the problem is in the protection layer, or at Step 3 or Step 5, where the resolution comparison or the direct-connection test names the failing link. If you have worked through all eight steps, changed one variable at a time, and the protected content is still black or still showing an error, the remaining possibilities are beyond what settings and cable swaps alone can settle, and further guessing risks changing settings that were never part of the problem.
Bring the machine in with the notes from Step 1 and the results of each step you tried. In-store inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. There is no home-visit service; inspection is carried out in the shop.
One last point about expectations: a diagnosis that ends at the stop line is not a failed diagnosis. A note that says "1080p works, 4K does not; direct connection still black; driver HDCP status recorded; every browser tried" is a precise description of where the fault lives, and it is exactly what an in-store inspection needs to start from the right place instead of from the beginning.
FAQ
Q1: Protected video is black but games and the desktop look normal. Does that mean my graphics card or display is broken?
No. If the desktop and games look normal, the display output layer is working. A faulty graphics card or display would fail across everything, not only on protected video. The contrast itself is the evidence: the problem is in the protection handshake layer, not in the computing or the panel, and the eight steps in this guide narrow down which link in that layer is failing.
Q2: My cable carries a picture fine, so it must be compliant. Is that right?
No. Carrying a picture and supporting the HDCP version a stream requires are two different things. HDMI version labels describe transmission capability; they do not prove HDCP capability for every device or every path. A cable can show the desktop perfectly and still be the link that cannot complete the handshake at the version the stream needs. Test it by comparison with a shorter, certified cable, as in Step 7.
Q3: 1080p plays but 4K goes black. Is my bandwidth too low?
Probably not. Bandwidth trouble usually shows up as intermittent black flashes, or as a picture that only stabilises after settings are lowered. A clean refusal at 4K with a clean picture at 1080p leans towards the HDCP version chain: the weakest link in the chain can only support the older version, so the whole chain drops to that level. The resolution at which playback stops is the clue.
Q4: Would turning off or getting around HDCP fix the black screen?
No, and it is not a repair. HDCP is a content-protection mechanism, not an ordinary user setting to be switched off at will. Getting around the authentication is not a fix, and this guide does not teach or hint at any way of doing so. The failing link needs to be found and addressed — a different port, a compliant cable, a middle device removed, or a version mismatch resolved — not the protection itself removed.
Q5: Will buying a more expensive cable definitely fix it?
No. What matters is the cable's specification and certification, not its price. An expensive cable built to an insufficient specification will fail in exactly the same way as a cheap one. Swapping the cable is only one comparison test inside the eight steps, and it should be judged by whether the same title plays after the swap, not by what the cable cost.
Q6: Should I just reinstall the graphics driver?
Not before the comparisons. A protected-video black screen with a normal desktop is not, on its own, a driver problem, and driver resets that cause black screens are usually accompanied by a game ending or by system records of the reset. Do the content comparison in Step 2 and the direct-connection test in Step 5 first — they are quick, cost nothing, and can clear or condemn the protection layer in minutes.
Q7: How do I tell a black screen apart from an error code?
Try the same title in a different browser or in the service's dedicated app, and check the Widevine module and the protected-content setting. If it plays in another browser or app, the problem is in the browser and DRM layer, and the display chain has been shown to work. An error code such as M7701-1003 also points to the browser layer. A black screen with sound that survives every browser and app points further down, at the display chain.
Q8: What is the direct-connection test, and why does it matter?
It means bypassing every middle device — dock, switch, splitter, adapter, receiver or amplifier — and connecting the graphics card straight to the display with a single cable, then playing the same protected title. If the picture returns, one of the bypassed devices is the suspect. If it stays black, every middle device is cleared at once, and the problem is in the direct chain itself. No setting change can clear a middle device, so only this test can.
Q9: Can different HDMI ports on the same display really behave differently?
Yes. On the same display, one HDMI port may support HDCP 2.2 while another only supports HDCP 1.4, so moving the cable to another port can change the result completely. Change only the port, not the cable at the same time, and retest the same title. If the picture returns on the new port, the original port's HDCP support is the suspect.
Q10: When should I stop trying settings and bring the machine in for inspection?
Stop when you have worked through all eight steps, changing one variable at a time, and the protected content is still black or still showing an error — or when the same display behaves the same way on a different computer. Bring your notes: which platform and title, which browser or app, the error message word for word, which steps you tried and their results, the 1080p comparison, the direct-connection result, and the driver HDCP status. In-store inspection is at Room 1209, Dali Plaza, Shek Mun, charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. You can call 2186 8010 or WhatsApp 6558 6806.