ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Widevine cras

  • 8 ردود
  • 4 have this problem
  • 24 views
  • آخر ردّ كتبه cor-el

more options

I can no longer watch any streaming services on my computer. The message "The Widevine plug in has crashed..." It says it is because flash player crashed. I don't know how to fix it.

I can no longer watch any streaming services on my computer. The message "The Widevine plug in has crashed..." It says it is because flash player crashed. I don't know how to fix it.

All Replies (8)

more options

hello ambush,

the best course of action is to roll back to the previous verions of FF, and then disable the auto updating.

find the version at here, seek the usa english folder, then do a custom install and create a special folder for the installation.

http://ftp.mozilla.org/pub/firefox/releases/78.9.0esr/mac/

you will then have 2 FF installations, helping you to preserve your personal data.

more options

See:

We have recently seen quite a few reports about Widevine issues on Mac OS X 10.9.5 . It looks that users get updated to Widevine 4.10.2209.1 and this version isn't compatible with Mac OS X 10.9 and causes crashes.

You can try to reinstall the 4.10.1582.2 version


There has been a bug report created.

  • 1707397 - WidevineCdm plugin crashing on all platforms
more options

Thanks cor-el, that explains what's been happening for me as well. Would you know how to install an older version of Widevine and where to find an older version? Their website and my searches haven't led me anywhere. Hoping you can help

more options

The redirector.gvt1.com link in my above post is a link to download a ZIP archive with Widevine 4.10.1582.2 for Mac.

You can open the chrome:// URI via the location/address bar in a tab to open a builtin JSON file with links for various Widevine version like that redirector link.

The third reddit link shows instructions to install Widevine that I refined for Mac in my second reply in this SUMO thread.

more options

Today at 1:05 PM

SUMOsJR said

   Hi there. Just an update here on the above conversation. 
   It looks like a fix for this is going into a dot release 88.0.1 which is set to release on the 5th. Give that a try once it is live and see if it resolves the issue for you.

Thank you sir. We will pass the word!

more options

The fix that 88.0.1 and 78.10.1 will get is about playing DRM protected content in HD when HDCPv1 is enforced. There is no fix possible for Mac OS X 10.9.5 users because Widevine no longer supports this OS.

See comment 14:

I've seen some folks discussing this bug in the context of Widevine no longer working on MacOS 10.9 due to the CDM not supporting that OS version. To avoid ambiguity, I want to highlight that the MacOS compat issue is a separate issue from this and is tracked in bug 1706393.

The DRM knowledge base article has been updated.

Note: The current version of Google Widevine is no longer compatible with older macOS versions such as OS X 10.9 and 10.10. Only macOS versions 10.11 and above are supported.

Modified by cor-el

more options

·´¯`·...¸>-)))º> ~dbben said

Today at 1:05 PM SUMOsJR said Hi there. Just an update here on the above conversation. It looks like a fix for this is going into a dot release 88.0.1 which is set to release on the 5th. Give that a try once it is live and see if it resolves the issue for you. Thank you sir. We will pass the word!

Does that mean there is some solution coming out through a firefox update? And the 5th of what? Sorry, I'm not that knowledgeable about these things but I'm experiencing this same problem.

more options

There is no fix possible if you run Firefox 78 ESR on Mac OS X 10.9 or 10.10 with Widevine CDM 4.10.2209.1 because the minimum macOS this version supports is OS X 10.11 like I wrote above. If you have a OS version that supports Widevine CDM 4.10.2209.1 and have a problem with playing HD content then this might should fix this. See the release notes.