Skip navigation

If you are using Firefox and certain security, HTTPS, or script blocking  extensions, you might not be able to use Netflix and get a “Digital Rights Management (DRM) error” such as N8156-6003, N8156-6013, N8156-6023. Many websites say that the solution to the problem is to delete the file “mspr.hds” located at %ProgramData%\Microsoft\PlayReady, but this does not always work because this isn’t always the underlying problem.

The problem is caused by scripts from microsoft.com required to use Silverlight DRM not loading properly. The fix is simple and does NOT require disabling NoScript or HTTPS Everywhere nor does it require restarting Firefox in Safe Mode just to watch Netflix. Make sure that you’re already allowing scripts to run from “netflix.com” and “nflxext.com” as these are also required for Netflix.

For NoScript, visit microsoft.com, open the NoScript menu, and choose “allow microsoft.com” from the list.

For HTTPS Everywhere, open the Add-ons Manager (usually under the Firefox menu, or under Tools -> Add-ons) and beside HTTPS Everywhere, click “options.” Type “microsoft” in the Search box. Look for “Microsoft (partial)” in the list and click the green check beside it to change it to a red “X” instead.

If you are running other script blocking software or extensions, you should be able to find a way to both unblock scripts from as well as don’t force HTTPS on the domains netflix.com, nflxext.com, and microsoft.com.

Advertisements

11 Comments

  1. This worked perfectly, thanks a lot.

  2. Thank you! This solved this error!

  3. Finally, the solution to my problem instead of Netflix’s bad advice about restarting the browser or deleting the mspr.hds file. Thank you!

  4. Thanks, this helped!

  5. THANK YOU! I tried all the other solves but nothing worked until I found this!

  6. An alternative that might make some mad: Just have an unsecure browser specifically for sites that don’t have advertising or junk. As in, Netflix on Chrome but everything else on a secured Firefox. Yeah, knowing my luck, in 2 years Firefox will probably effectively _be_ Chromium and break NoScript on purpose. 😦

  7. Thank you so much! I deleted the whole msdr thing to no avail and essentially gave up were it not for an insatiable desire for netflix in my life. In short, that one little red x worked 😀

  8. Thanks dude !

  9. This worked! Thanks! 🙂

  10. Thank you!

  11. You also have to allow “s.microsoft.com” in NoScript. This is what was stopping it for me. Many Thanks 🙂


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: