How to fix Netflix error n8156-6013 on Windows Vista/7 x64

I have several ways to watch Netflix, mostly via dedicated media streamers as WD TV Live Plus but the Netflix interface in Windows Media Center for Windows 7 is second to none. I started to miss it and today I wanted to play with it again. However, I had a nasty surprise: While I was perfectly able to browse Netflix queue / categories, I couldn’t play any movie. Instead, the following error message was displayed in Netflix for Windows Media Center:

“An Internet or home network connection problem is preventing playback. Please check your Internet connection and try again.” with an error code n8156-6013.

You’ll be surprised to know the problem is not your home network connection and neither the Internet. Somewhere between Microsoft and Netflix, the DRM system broke with the release of Silverlight 4. Weirdly enough, the issue only happens on 64-bit Windows Vista and Windows 7 versions. How to fix it?

A simple way that won’t require messing up with Windows internal files is to just uninstall Silverlight 4 and install instead Silverlight 3 which will work fine. In order to do that, go to Control Panel->Programs->Uninstall a Program and remove all Microsoft Silverlight occurrences. After you don’t have any Silverlight packages installed, you can proceed installing Silverlight 3. After that, Netflix should work fine without n8156-6013 errors.

Now, there is something very important. You should turn the automatic Windows Updates off, otherwise Windows will update Silverlight to version 4 and your troubles will begin again. Also, whenever you are prompted to update, un-select Silverlight 4 from the list, at least until there is an official word that Microsoft fixed this mess.

Alternative solution: If you prefer to have Silverlight 4 on your system, just navigate to this folder: “C:\ProgramData\Microsoft\PlayReady” and delete the file called “mspr.hds” (DRM related, of course).Be sure any Internet browser and Windows Media Center are closed though before you attempt deleting this file. If you want to preserve the file, just rename it to “mspr.old” or something similar.

If you have a MAC, the same trick with installing Silverlight 3 will work. Alternatively, the “mspr.hds” is located in “HD > Library > Application Support > Microsoft > PlayReady > mspr.hds”

Related posts:

Tags: , ,

  • Derek

    Just wanted to say a big THANKS! I deleted the ‘mspr.hds’ and it everything works again!… What a pain in the @SS

  • InTheMidst01

    thank you, this fixed help by just deleting the “mspr.hds” file

  • Weslee

    Genius! THANK YOU! :)
    BTW – I kept getting error code N8009 and this fix worked like a charm. Thanks again!

  • Josh

    I got Vista 32bit, and I don’t have a “mspr.hds” file…Anything else I can check???

  • Denton

    Thank You for this! I spent a few hours trying to use WTF version 2.1!

  • Priscila

    Thanks a lot!!! I had almost the same problem, the error code was N8156-3119, after reading your information I thought it could probably be the same situation. I was trying to find the Silverlight 3 but nowhere else I could find it, all of the options would lead me to install the version 4, and I was pretty sure it was a silver light problem and my internet or network connection. Only your information gave the real Silverlight 3. Now everything is working well! Thanks a lot again!

  • grant

    Thanks abunch. I simple uninstalled silverlight v4 with Revo uninstaller and reinstalled with version 3 link you gave above. Now no more DRM issues. what an irritation. called up Netflix and they said you need to call your computer dealer and update your firmware. uhhh, right. You’d think at the risk of losing customers they would provide a bit more help than “go figure it out yourself”

    again, thanks much
    ps, I run win xp system

  • Jacob

    Thanks Sooo Much,I’ve been trying to figure out where to find the folder for days and you’re the first person to give a comprehensive example for Windows Vista!

  • Bloink

    Again, thanks so much! This problem popped up for my windows 7 system after installing Frontpage, and a LOT of window updates ensued. Happy that your old post is still helpful today.

  • http://pulse.yahoo.com/_CMIADPGNO7S3SRK4IKTX6GQPSQ Anonymous

    Run IE in adminsrator mode and the DRM problem goes away.

  • http://pulse.yahoo.com/_CMIADPGNO7S3SRK4IKTX6GQPSQ Anonymous

    Run IE in adminsrator mode and the DRM problem goes away.

  • http://pulse.yahoo.com/_FEGS3TL5ZK7J2EW2JBCQGMOKEY John

    Netflix do not want to use version 3, they will insist that you upgrade and that will be to version 4. So the removal of the mspr.hds file in Library > Application Support > Microsoft > PlayReady > mspr.hds”, was the fix for me. I did however rename the file just to be sure that it would work.
    Thank you so much for this fix. That saved my day.

  • Anonymous

    i spent 3 hrs with microsoft today cleaning up my windows vista and trying to load Netflix.. this is my second week trying this… now they say will call back tuesday and not get it fixed..now saying a internet log on issues and keeps losing connections… that is so funny due to I can buy a show or movie from amazon and watch it and have no issues… I also can watch and youtube video as well… I know it has to be Netflex.. but when I call them and can get someone to help with out talking about themselves or yawning the whole time.. they say its not there problem… please any one help…

  • 55xiong

    Synchronize your computer time and day with the internet time. It worked for mine. Netflix was able to stream without doing anything else. I’m using window 7 64 bit and sliverlight 4.

  • http://egregores.blogspot.com Apuleius Platonicus

    I have been struggling with an almost identical problem. I am using Windows 7 64 bit, and all of a sudden in the last couple days I was no longer able to play Amazon streaming videos. I was getting “error 6103″, which is a Silverlight error. I had uninstalled and reinstalled Silverlight a number of times (to no avail), but it did not occur to me to downgrade to Silverlight 3. But as soon as I did (using your link) it worked immediately!! Thanks!!