HDCP error - unable to display

I also had it happen with the previous TV...

Try another hdmi cable or use component cables.

The only way to get it back, is to do a hard reset on the Uverse box...

Net time it happens try just pulling the hdmi plug out of the receiver (or tv) and plugging it back in.  Or turning the receiver off and back on (not pull its plug).

And I have a hard time blaming the cable, when 99.9% of the time, the cable is "fine", meaning I'm watching my Uverse to my hearts content, and suddenly, on next power cycle, the cables not fine? And for some reason, resetting the STB fixes the cable?? Call me a skeptic, but I think not.

And I have a hard time blaming the cable...

Fine, but troubleshooting these kinds of things you have to start some where.  Replacing the cable with component cables is a trivial exercise to see if the problem is even remotely related to the tv cable connection.

Another trivial test would be to plug the hdmi into another of the tv's hdmi ports.

You could also just replace the receiver.  Take a couple of days to get a another one.

There's no sense speculating/theorizing here if you don't do some tests to try to eliminate some of the variables that might have some effect on the problem.

HDCP stands for HD Copy protection, and is a part of the HDMI standard. It is impossible for you to get that error if you use component cables.

As for the actual cause of the issue, its possible its a faulty STB, its also possible its a faulty HDMI cable, it could also be that you are passing the signal though an xbox one's pass though port (It's not actually a pass though as there's some processing going on), it could be you have something like a capture card connected. Could be a faulty TV too.

There's many things that can result in your system not being HDCP compliant, they're all going to be equipment issues though, from the sounds of things though, its either the HDMI cable or the receiver at fault.

@IT_Moose -

HDCP stands for HD Copy protection, and is a part of the HDMI standard...

I know that but the OP seems unwilling to do anything about troublshooting or working around the problem.  I initially suggested just try to replace the hdmi cable or component cables just try to eliminate the HDCP problem.  I also suggested replacing the receiver but s/he seems to have a lot of "inertia".  Anyway I give up.

First, I do apologize for the "attitude" showing, especially to those who genuinely want to help. I must admit, my post was more of a rant, and an effort to see if there are other who have had similar experiences. I see the answer is a resounding "yes". I am an electronics tech with 30+ years of troubleshooting experience, so I do know a thing or two about electronics. I also have a pretty good idea of exactly what is causing the problem, either an overly "paranoid" implementation of HDCP that is going to "assume", with no changes in setup, that I am trying to record (IE steal in the words of the content providers) their precious content. Or, it's just a crappy implementation of the HDCP in the STB. I have 1/2 a dozen other HDCP enabled, HDMI connected devices on this and other TV's, and the ATT box is the ONLY one that ever has this issue. I have swapped out cables and inputs till the cows come home, and it makes no difference. I don't blame ATT for HDCP, but I do blame their STB for not playing nice with other HDCP enabled devices. I also blame the providers, and the politicians, who foisted the DCMA on us years ago, paving the way for this crap. I do appreciate the input of those trying to help, and I do apologize for not starting off my post with 🙂

I like the simple, clean look of one small cable running to my wall-hanging TV, something I won't get with component. If properly implemented, I wouldn't mind the HDCP, I have no nefarious plan to "steal" (IE time shift) the providers content, so it would be transparent to me if it worked as designed. As it is, I have to spend 5+ minutes waiting for the STB to reset, with service I pay very handsomely for. I realize I have a choice, I don't have to pay ATT, but then who would I rant about 🙂 I really do like my Uverse, which makes this issue all the more maddening. 'nuff said

Tom

Honestly, from everything you've mentioned, I think its the STB at fault, I would still suggest if possible using component cables instead, those wont have the HDCP issue, which I can say with 100% certainty, and if they do, then you know without a doubt its the STB at fault, and you should call in to get it replaced

FWIW, nearly every time I've had issues with HDCP it was either the cable or the DISPLAY device.  Once it was a faulty receiver and once it was an old dvd player.

If you've got your cable going from the STB directly to the display, I would suspect the cable, then the display, then the STB and eliminate in that order. 

Hth,

-weq

Sorry, but I disagree. The fact that changing the display device, or the cable, may sometimes remedy the situation, is not proof that either of those items was the cause, when you consider that ALL other HDMI enabled devices I use NEVER exhibit the problem, even when using the same cable, same input, on the same display device. The only constant in this equation is the Uverse STB. In a situation like this, it just goes to prove my point of an overly paranoid or poorly implemented HDCP in the Uverse STB.

I realize I wasn't really searching for a culprit when I made my original post, I'm pretty sure I know where the problem lies, I was really just wanting to express my frustration, and also get an idea of how many others have had the same problem. I also thought it might be significant that it seems to do it more often when the DVR is near capacity, but perhaps that's just been coincidence.

Tom