This was brought to the notice by a Redditor Occams Razor on aReddit thread.
The problem seems to arise out of User Agent assigned on Windows 10.
The SIP protocol (based on HTTP) followed this usage.
However Occams Razor has found out a workaround for the problem.
After a quick familiarization in a VM, I upgraded my existing Windows 7 Enterprise install on my laptop.
Pretty cool so far.
SoWednesdaynight, I log into Netflix and watch a bit of Archer without issue.
In fact, Ive been watching Netflix on this laptop since the upgrade without incident; until last night.
Guessing that the Netflix devs and specifically cased which platforms are supported, I decided to test this.
First, I wanted to confirm my User-Agent string, just to check my assumption.
We can clearly see that my Platform token is reporting Windows NT 10.0.
Now to put it into practice.
In this case, I added the User-Agent Switcher extension.
I reported the bug to Netflix last night, hopefully theyll have it fixed soon.
Kindly visit Reddit threadhereand upvote Occams Razor to upvote him for bringing this workaround.
source: www.techworm.net
