Forum Discussion

gogphoto's avatar
gogphoto
Channel Surfer
2 years ago

My Roku Just Updated (12.5.0 • build 4172-CR) and the Update has cause the HDCP issue to resurface

My Roku updated 10/10/23 at 7:37pm, and now I'm getting the HDCP error that wants me to check all my cables when ever I try to start a program or movie in an app (Netflix, Disney+, Apple TV, Prime, etc.) The only thing that's changed is the update, it's not my cables, and this happened on an update last year as well.

Is it possible to walk back the update so that my Roku isn't a useless brick?

 

Model 3941X - Roku Express 4K+

Software Version 12.5.0 • build 4172-CR

Device ID S07P217RS8AP

#HDCPissue #Updatesaregarbage

tv & player features

10 Replies

Replies have been turned off for this discussion
  • ryeguy_24's avatar
    ryeguy_24
    Binge Watcher
    2 years ago

    It also broke my HDMI-CEC. In the same way mentioned from original poster: Roku 10 broke it, then 12 fixed it and now 12.5 brought the bug back.  Maybe it’s connected to the HDCP issue. 

    • HisSvt2's avatar
      HisSvt2
      Roku Guru
      2 years ago

      Had this happen today on my premiere also none of my apps would play content in 4k hdr or Dolby vision had to toggle that new force Dolby vision on off reboot etc and then app started displaying content properly again for now… that setting is in advanced display if anyone hadn’t seen it.

  • gogphoto's avatar
    gogphoto
    Channel Surfer
    2 years ago

    Tracker ID AP-407-541

    GC Version 10.1.517

    Timestamp: 2023-10-11T00:21:32Z

      • gogphoto's avatar
        gogphoto
        Channel Surfer
        2 years ago

        Yeah, that document is completely useless to my situation. I did try swapping cables and even the HDMI port, rebooted the ROKU, cycled the TV, etc. The fact is that the issue started with the Update yesterday, and is software related not hardware related. If there's a document that addresses the update not working properly on slightly older devices, I would be happy to try some fixes from that.

        The last time this happened they ultimately rolled back the update, and that mostly fixed the issue...maybe that will help here?