I'm trying to run the Netflix Modern app on my PC running Windows 8.1. To be clear, this is the app that you can install in the Modern interface using the Microsoft Store. I'm not trying to run Netflix in a web browser. Note that it does work in a browser, it's important to me to get the Modern app working because this PC is for a home theater.
Every time I open the app, it gets stuck at the loading screen with the Netflix logo and the dots moving in a circle below it. Sometimes it crashes after sitting at that screen for several minutes, but not every time. There's no error message or any other diagnostic information that I've been able to find.
My system is fully up to date. Here's what I've already tried:
- Installed all system updates
- Uninstall and reinstalled Netflix
- Ran (and passed) network diagnostics
- Turned off Windows Firewall
- Ran WSReset.exe as an administrator
- Booted up after disabling all startup items
So far, nothing has fixed it. Netflix support has been absolutely no help.
Does anyone have any ideas on how I can fix this?
I found an error message in Event Viewer, under Custom Views / Administrative Events:
Faulting application name: Netflix.exe, version: 220.127.116.11, time stamp: 0x53e95fca Faulting module name: twinapi.appcore.dll, version: 6.3.9600.16384, time stamp: 0x5215d806 Exception code: 0xc000027b Fault offset: 0x0000000000056960 Faulting process id: 0x1614 Faulting application start time: 0x01d049ad8cab0f33 Faulting application path: C:\Program Files\WindowsApps\4DF9E0F8.Netflix_18.104.22.168_x64__mcm4njqhnhss8\Netflix.exe Faulting module path: C:\Windows\System32\twinapi.appcore.dll Report Id: d6e3fd1f-b5a0-11e4-82ea-001bdc0f3779 Faulting package full name: 4DF9E0F8.Netflix_22.214.171.124_x64__mcm4njqhnhss8 Faulting package-relative application ID: App
Unfortunately I don't know what this means.
A lot of sites suggested that fixing permissions of certain key directories and registry entries can fix this kind of issue. I checked the permissions on all of them and they are correct, which I expected. I certainly haven't gone dicking around with Windows' default permissions on this system, so that doesn't seem to be the cause.
Tried executing 'sfc /snannow' as an administrator, no dice.