Black Screen, Perfect Sound: the HDCP Handshake That Blocks Netflix on One Display and Not the Other

The call comes in as a screen problem. "The laptop is fine for everything else, but Netflix is just a black box." Or: the new television plays broadcast fine, and the streaming stick gives a black screen through the sound system. Or, the one we get most in home offices, everything on the desk works perfectly until somebody tries to watch something at lunchtime on the second monitor, and only the film is missing.

In nearly every one of those cases nothing is broken. What has happened is that a copy-protection check between the thing playing the video and the thing displaying it did not complete, and the player responded the only way it is allowed to: by refusing to put the picture out. The audio is not protected in the same way, which is why you can sit there listening to a film you cannot see — and that symptom, sound without picture, is the single most useful clue in the whole business.

This article is about finding which link in the chain failed. It covers the messages Netflix actually puts on screen, why a TV can pass the check on one HDMI socket and fail on the one next to it, what a dock or a splitter does to the whole arrangement, and the awkward fact that some things which used to work — AirPlay among them — were withdrawn rather than broken.

The tell that saves an hour: can you hear it?

Before touching anything, answer one question, because it splits the problem in half and Netflix itself splits its own troubleshooting on exactly this line.

If you can hear the film and not see it, Netflix's own page is direct about where to look: "If you hear sound but don't see video, or if the video goes black while watching, it usually means an issue with your device or a video cable stopped Netflix from showing video." That is the video path — the cable, the adapter, the dock, the port, the display.

If you get neither sound nor picture, you are in a different article. That pattern points at the network, the app, or the account, and none of the cable-swapping below will help. The same goes for a black screen that never gets as far as the Netflix logo, or a spinning loader that never fills: that is buffering or a connection problem, not a protection problem.

The third pattern is worth naming because it is so often misread: the picture is there but soft, blocky or stuck at what looks like DVD quality. That is also a protection-related answer, but a different one, and it is further down this page under the browser you happen to be using.

What is actually happening: a handshake, not a fault

The mechanism has a name, and Netflix publishes a plain-English definition of it. "HDCP stands for High-bandwidth Digital Content Protection," its help page says, and "The purpose of HDCP is to protect digital copyrighted content as it travels from a device to your TV, generally through HDMI or DVI connections." The sentence that matters for troubleshooting is the last one: "HDCP is required to stream Netflix from a device connected to your TV."

Required means required. Every time protected video starts, the player and the display exchange credentials over the cable, and every device in between has to pass that exchange along faithfully — the receiver, the soundbar, the dock, the switch box, the adapter, the extender. If any link cannot take part, the player does not degrade gracefully or warn you in advance. It simply stops sending the picture, and you get a black rectangle.

Two consequences follow, and both are counter-intuitive enough that people waste real time on them. First, the desktop being visible on that monitor proves nothing at all — the check only happens for protected content, so Windows, your spreadsheet, and a video call can all be perfect on a display that will never show a film. Second, because this is negotiated per connection, the same laptop can play happily on its own screen and fail the moment a second display, a dock or a television is in the picture. Neither of those is a sign of a failing machine.

The message on screen, decoded

Netflix uses several different messages for what is broadly the same family of problems, and the wording tells you how narrowly to look. These are the ones we see most, in Netflix's own words.

"HDCP Unauthorized. Content Disabled." is the bluntest of them. Netflix says it "typically points to a hardware problem where your device cannot play protected content," and its advice is a power cycle followed by working through the physical connection. On a streaming box this is the message you are most likely to meet after re-plugging things behind the TV.

Error S7336 appears on computers, with the on-screen text: "Looks like there's an issue with your display. Please make sure your monitor is HDCP compliant and isn't mirrored using AirPlay." Netflix's explanation is narrower than the message sounds — "It usually means the video cable connecting your computer to your display is stopping Netflix from playing" — and the page lists the connection types it supports: HDMI or HDMI Mini, USB-C (also known as Type C), Thunderbolt, and DisplayPort or DisplayPort Mini. There is a trap in the small print worth reading twice if you use an adapter: "If you're using a video cable adapter, both ends of the connection must also be a supported type."

Error D7361-1254-8004CD22 is the same story told from the display's end. Netflix: "It means a screen or computer monitor you're using doesn't have built-in content protection Netflix needs to work." The single test it gives is the one we would give too — disconnect every external monitor and television and try again, because "If this resolves your issue, it's likely that your external monitor or TV doesn't support HDCP copy protection."

Error M7353 is the odd one out and is worth knowing so you do not spend an afternoon on cables for nothing. Netflix describes it as a data problem — "This error happens when an issue with data stored on your device stops Netflix from playing" — and its steps are a mixture: a full shut-down, clearing the Netflix cookie at netflix.com/clearcookies, turning off browser extensions one at a time, Windows updates, and only then disconnecting secondary displays.

"The connected display is not supported. (10065)" is the one that catches people out completely, because it is not always about hardware. Netflix says it "can happen if you're using an unsupported video output method, or if your Netflix plan doesn't support using a mobile device to watch Netflix on a TV" — and spells out that watching on a TV from a phone or tablet "isn't available with an ad-supported experience or a Mobile plan." If you have recently moved to a cheaper tier, that is a billing answer wearing a hardware error's clothes. Where it is hardware, the instruction is specific: "Make sure your video cable or adapter supports HDCP 2.2."

Every box in the chain has to pass it along

This is where most of these jobs are actually solved, and Netflix's own hardware checklist is the right order to work through. It appears almost word for word on several of its error pages: use an HDMI cable, try reversing the ends of the cable, try a different HDMI port on the TV, try a new cable, and — the step people skip because it means moving furniture — "Bypass any receivers or sound systems in use by connecting your device directly to your TV using an HDMI cable."

That bypass step is the highest-yield thing on the list. An AV receiver or a soundbar sitting between the player and the television is a full participant in the protection check, not a passive pipe, and it is very often the oldest device in the stack. A receiver bought a few years before the television is the classic case: everything works, the picture is fine from the aerial and from the games console, and one streaming app is black.

Reversing the cable ends sounds like superstition and is on Netflix's list anyway. It costs nothing and takes ten seconds, so do it before you buy anything. Trying a different port and a different cable are in the same category of cheap tests — and if the failure follows a particular cable to every port, you have found it.

One more line on Netflix's page is worth quoting because it tells you who owns the problem once the chain is bypassed and it still fails: "Because the steps to change these settings or troubleshoot a video issue are unique for each device, Netflix Customer Service can't assist with following steps for your device." At that point you are looking at the television or display maker's own picture settings and firmware, not at the app.

Not every HDMI socket on the television is the same socket

Here is the detail that resolves a surprising share of these calls, and it is published in plain sight. Netflix's requirements for 4K on a cable box read: "A 2014 or newer 4K Ultra HD TV that is capable of streaming 4K Ultra HD content at 60 Hz, connected to your cable box via an HDMI port that supports HDCP 2.2 or later (usually the HDMI 1 port)."

Read that parenthesis again. On a great many televisions the sockets are not equivalent — one or two of them support the newer protection level and the full bandwidth, and the rest are there for the games console and the DVD player. Manufacturers often mark the good one, sometimes only in the manual, and the labels vary.

Which makes the following sequence one of the most common causes we meet, and it has nothing to do with anything failing. A soundbar arrives, or a new console, and everything gets shuffled one socket along to make room. The streaming stick that lived on HDMI 1 for three years is now on HDMI 3. Broadcast television still works, games still work, and the films go black or quietly stop being 4K. Nobody connects the two events because the shuffle happened a week earlier.

So when you are testing, do not just try "a different port" at random — try the first one, direct, and check the television's manual for which of its inputs is the full-capability one.

The dock, the splitter, the KVM and the capture card

Desks have the same problem as living rooms, with more boxes in the way. A laptop on a dock with two monitors, a switch box sharing one screen between a work machine and a personal one, a splitter feeding a display in another room, a capture card in line for recording — each of those is another link that has to carry the protection check.

The first-party advice above gives you the method, and it is the same one regardless of what the extra box is: take everything out of the middle and go straight from the computer to the one display with a known-good cable. If it plays, add one device back at a time and watch which addition kills it. That is unglamorous and it is faster than reasoning about it, because the alternative is guessing between four boxes.

In our experience the extra box in the middle is the likeliest culprit whenever there is one at all, and the cheaper and older it is, the likelier it gets. Inexpensive splitters, long extenders, adapters that convert between connection families, and anything bought to solve a different problem entirely are where we usually end up. That matches Netflix's adapter warning — both ends of the connection have to be a supported type — and it is why a chain of two adapters almost never works even when each one is fine on its own.

We should say plainly what we do not do here, because the internet is full of it: there are boxes sold specifically to strip protection out of the signal, and we do not fit them or recommend them. The point of this exercise is to find the link that failed and put a working one in its place, which is both legitimate and, nearly always, cheaper.

And one genuine consolation for anyone who has been told they need a new monitor: for an ordinary work-from-home setup, there is a good chance the display is fine and the dock is not. Test before you buy anything.

Mirroring and AirPlay: not broken, withdrawn

A whole category of these calls is not a fault at all, and this is the part almost nobody knows. Screen mirroring and AirPlay used to be a normal way to get a film from a computer or tablet onto a television, and for Netflix it no longer is.

Netflix's own page says it twice, in two places, without hedging: "Airplay and Screen Mirroring are no longer supported by Netflix." For anyone using an iPad as a second display next to a Mac, there is a second sentence with teeth: "Screen Mirroring and Sidecar are no longer supported by Netflix and need to be turned off while Netflix is playing." Not merely unsupported while in use for the film — turned off. On the Android side the wording is softer but lands in the same place: "Apps or features that mirror your Android device's screen to a TV might not be supported by Netflix."

Notice that the S7336 message itself tells you this if you read it closely — "make sure your monitor is HDCP compliant and isn't mirrored using AirPlay" is two separate instructions in one sentence, and people reliably act on the first half only.

If mirroring is how the household has always watched, the answer is not a settings fix. It is to play from something with a direct connection to the television: the app built into the set, or a streaming box on the HDMI 1 socket. Worth knowing before you spend an evening on it, and worth knowing that this can start one day out of nowhere, because an app update is all it takes for a route that was tolerated to stop being tolerated.

Macs: the sleep quirk, and which apps are even allowed

Apple documents a specific and very recognisable version of this on its own HDMI support page, and it is the first thing to try on a Mac before anything else: "If your Mac goes to sleep while a video is playing or paused, you might see an HDCP error. Quit the app that is playing the video, then open the app again."

That is the classic Monday-morning report — it worked on Friday, the lid went down with something paused, and now there is an error. Quitting the app properly, rather than closing the window, clears it.

The same page sets the baseline for everything else: "To play HDCP content on an external display, HDCP playback requires an HDCP compatible display." And it names where protected playback is supported from — "HDCP-encrypted playback from Apple Music, iTunes and QuickTime Player (version 10)", plus Safari on macOS Sierra or later "if the web page is HTML5-enabled and the content is FairPlay Streaming-enabled and delivered using Media Source Extensions or HTTP Live Streaming."

The practical reading of that last clause: on a Mac, which browser you use is part of the equipment. If protected video will not play in one browser on an external display, trying another is a legitimate diagnostic step and not merely superstition.

It plays, but it looks soft — the browser is the cap

Not every one of these problems is a black screen. A common and genuinely confusing complaint is that a film looks noticeably worse on the laptop than on the television, on the same account and the same connection. People upgrade their internet over this, and the internet was never the problem.

The cap is the browser, and Netflix publishes the numbers. On Windows, Edge 118 or later and Chrome 117 or later go up to Ultra HD (2160p), while Firefox 129 or later and Opera 92 or later stop at Full HD (1080p). On a Mac the ranking is almost reversed: Safari 14 or later goes up to Ultra HD, Chrome and Firefox stop at Full HD — and Microsoft Edge on a Mac is listed as going up to HD (720p). That last figure is not a typo, and it explains a lot of "why does this look terrible on my MacBook" calls in one line.

Netflix also spells out the chain rule for quality, which is the same logic as the protection chain: if you are "trying to watch on a TV with a streaming stick and an audio receiver, all three of your devices have to support 4K or HDR in order for you to be able to watch in 4K or HDR." The weakest link sets the ceiling, and the weakest link is usually the one you have not thought about in five years.

Also on that page, for anyone still running an older machine: "Computers with Windows 8 or 8.1 might still work, but Netflix will only play in Standard Definition (SD) video quality." If a picture looks soft on an old laptop and nothing you change helps, that may simply be the answer.

The one time it really was Windows

Because this comes up whenever an update has just installed itself, it is worth stating what Microsoft has and has not acknowledged, with the dates attached.

There was a genuine Windows fault in this area. Microsoft's release-health pages record an issue titled "Problems playing protected content in some BluRay/DVD/Digital TV applications", opened on September 19, 2025 and marked resolved on October 28, 2025 with update KB5067036. The description is exactly the symptom set this article is about: "Applications using Enhanced Video Renderer with HDCP enforcement or Digital Rights Management (DRM) for digital audio might experience copyright protection errors, frequent playback interruptions, freezing or black screens."

But read the next sentence before pinning anything on Windows, because Microsoft is explicit: "This issue does not impact streaming services." So if the thing going black is Netflix or another streaming app, that bug was never your problem. If the thing going black is a disc-playback or digital-TV application on the PC, it may well have been — and the fix has shipped, so a machine that is properly up to date already has it.

The other genuinely Windows-side step is the graphics driver, and Netflix puts it on its own list: "You may need to update your computer's video driver, or install a video driver supported by Windows 10," noting that AMD and NVIDIA are the most common makers of the software that does it. Netflix's page is showing its age in that wording, but the advice holds — and if an update did not help, its suggestion is to uninstall the driver and reinstall it rather than to keep updating.

The order to do it in, if you only have ten minutes

Putting the verified steps together, this is the sequence we work through, and it is deliberately arranged so that the cheap tests come before the ones that involve moving furniture or spending money.

One: confirm you can hear it. Sound plus no picture is the video path; nothing at all is a different problem. Two: on a computer, disconnect every external display and play on the built-in screen. If that works, the machine is fine and the answer is outside it. Three: go direct — player straight into the television with one cable, no receiver, no soundbar, no splitter, no dock — and use the first HDMI socket, checking the manual for which input is the full-capability one. Four: reverse the cable ends, then try a different cable. Five: if it now plays, add one device back at a time until it breaks, and you have your culprit. Six: restart properly rather than sleeping — Netflix asks for a full power-off and "Leave your device off for 15 seconds", and for a streaming box or television, unplugging from power for at least a minute. Seven: get the app, the operating system and the graphics driver current. Eight: if you are mirroring or using AirPlay, stop, and play from a device with its own direct connection.

If all eight are done and one display still refuses protected video while everything else on it is perfect, you have most likely found a display or an in-line device that cannot do it at all. That is a purchasing decision rather than a repair, and it is worth confirming carefully before making it.

If it is one film and not all of them

Worth ruling out early, because it saves the whole exercise. If everything else plays and one particular title is black, the problem is probably not in your house at all.

Netflix builds this into its own troubleshooting — check whether other shows and films work first, and if they do, report the specific title rather than rebuilding your setup. Its instructions are to open Viewing Activity in your account in a browser, find the title, and click Report a Problem, after which, in Netflix's words, "Our content teams will work on fixing the issue as quickly as possible."

Same logic across apps: if one service is black and the others are fine on the same equipment, suspect that app or that title before suspecting the cable. If every protected video from every service is black on one display, suspect the display and the chain.

Where we come in

Most of this you can work through yourself in an afternoon, and we would rather you did than paid anybody — including us — to reverse a cable. Where we tend to be genuinely useful is the multi-box case: a work-from-home desk with a dock, two monitors and a switch box, where the answer is a specific link in a chain of five and the trial-and-error is tedious; a living-room stack with a receiver and a soundbar that needs re-ordering; or a small business with a display in a waiting room or meeting room that has to play something reliably at nine in the morning.

We do not sell displays, docks, cables or streaming boxes, so if the honest answer is that one twelve-dollar cable or one repositioned plug fixes it, that is the answer you will get. And if the answer really is that a device in the middle cannot do protected video, we will tell you which one, so you replace the thing that is actually the problem rather than the biggest thing in the room.