This n8156-6013 error has been going on since at least June 9. I called Netflix and they blamed Microsoft with errors in Silverlight 4. Their suggestion to the millions of people who stream netflix is to revert to Silverlight 3 and turn off the auto-update for Silverlight.
Certainly after 1.5 months there should be a fix.
Does anyone know when this will be fixed? TIAMonday, August 23, 2010 2:48 PM
Thank you. Apparently an error with Win x 64 only.
From the blog:
"Renaming mspr.hds worked for me. I found it in C:\ProgramData\Microsoft\PlayReady"
It baffles me why nobody has fixed this (netflix, microsoft, whatever) so far and netflix officially tells you to run the Silverlight 3 version.Wednesday, August 25, 2010 1:43 PM
I have fixed most of these problems on vista/7go to this site to read the full fix.http://www.cooltechspotblog.com/2010/10/netflix-fix-v21.html
I have fixed most of these problems on vista/7
go to this site to read the full fix.
I think you will find it the easiest fix out there.Friday, October 01, 2010 6:20 PM
This problem is NOT limited to x64 versions.
I get this occasionally in XP x86.
The renaming of mspr.hds works fine as a fix in XP as well.
Path in XP is
C:\Documents and Settings\All Users\Application Data\Microsoft\PlayReady
Just rename the mspr.hds file to whatever you want then reload the netflix instant player so that it is forced to reconstruct a mspr.hds file.
I never have to restart anything, just reload the player but you may have to restart or re-log-in if it still doesn't work.
Wednesday, December 15, 2010 8:26 AM
For me, deleting the MSPR.hds file just wasn't enough - I needed to go one step further. There is a hidden PlayReady Cache which appears to store historic DRM keys and data...
Launch the Windows Command Prompt as admin (go to Start, search for "cmd", right-click and Run as administrator) and enter the following:
rmdir /S Cache
You'll be presented with a Y/N prompt: hit Y and press return. Windows will delete the hidden Cache folder and all its content, which for me was enough to get Netflix up and running again.
N.B. Usual disclaimers apply, there's no guarantee this'll work for you or that it won't have an adverse effect on any other DRM protected content on your PC, so try at your own risk.Wednesday, September 14, 2011 10:42 AM