This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I talked to a netflix technical assistant tonight and he tried to help me with this problem, but was unsuccessful. The error code I receive from Netflix is N8156-6003. He walked me through many different procedures to fix the problem and nothing seems to be working. He even directed me to try tinyurl.com/netflixsl and after the individualizing it goes to opening and stays there. My laptop is on 8 months old and is not used very often, not sure what the issue is, Netflix seems to think it is a problem with microsoft, please help.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hello, Nea5577
After loading the page to watch a video, right click the applet, then click Silverlight.
On the Playback tab ensure that the “Enable download...” option is selected.
On the Application Storage tab, click Delete all to clear any cached files.
David
Microsoft Answers Support Engineer
Visit our Microsoft Answers Feedback Forum and let us know what you think.
Thank you thank you thank you thank you! You rock! This worked for me after I had tried hundreds of other fixes. Finally!
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
I had this issue in conjunction with the .NET v4 framework update (KB2468871 and KB2533523). The resolution for that issue also resolved the issue I was having with Netflix and Sliverlight. The root cause was that the root certificate store had gone bad, either expired or corrupted. This most likely occurred during a system restore that had been performed recently.
I applied the rootsupd.exe patch I downloaded at http://download.microsoft.com/download/A/E/4/AE48995A-8C71-4E97-98A1-77752A4F564E/rootsupd.exe. This resolved both failed KB updates and the issue with Netflix.
Details for the .NET installer failures:
Update for Microsoft .NET Framework 4 on Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2 for x64-based Systems (KB2468871)
Installation status: Failed
Error details: Code 800B010B
Update type: Recommended
Install this update to resolve issues in Microsoft .NET Framework 4. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.
==
Update for Microsoft .NET Framework 4 on Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2 for x64-based Systems (KB2533523)
Installation status: Failed
Error details: Code 800B010B
Update type: Recommended
This update addresses stability, reliability, and performance issues in Microsoft .NET Framework 4. After you install this item, you may have to restart your computer.
Incidentally, as a troubleshooting tip: I determined the cause of this problem by running the .NET installer standalone (outside of Windows Update), which had a link in its error dialog going directly to the actual error in the installer log beyond the 800B010B reported by Windows Update. It is kind of unfortunate that I had to dig that deeply to get at the installer log. Shouldn't Windows Update be sending that home through WER?
This cured the Silverlight 6003 error code for me. Been affecting me for 6 months. Top tip, thank you very much.
Thanks so much. The rootsupd.exe patch worked!
