Troubleshooting website display or functionality issues in Edge on Windows 10
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am discouraged that this problem has not been fixed after several months. I am a long-time a Netflix subscriber. Since I upgraded a few months ago to the new Edge Chromium browser, Netflix always returns error code D7353-5101. Refreshing the browser screen always allows Netflix to play normally. Even so, it is a damned nuisance. Netflix support says that Netflix does not support the Edge chromium browser, and recommends using Google Chrome or Firefox browsers. It would seem to me that not supporting a widely used service such as Netflix would be a very big negative that Microsoft would want to fix. Yet... months go by and no fix.
Before anyone asks, I do not use third party AV. Windows has been updated since the problem appeared, and is up-to-date.
Troubleshooting website display or functionality issues in Edge on Windows 10
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.
Update - the 5C release is KB5003214. This has an additional fix for the signing issue that caused the symptom investigated here.
Thanks
Arvind
Thanks to loyall for helping me collect additional logs. We confirmed the presence of another problem related to binary signing that caused the symptom. I'll share an ETA for that patch (also in the form of a Windows update) as soon as it is confirmed.
Thanks
Arvind
I had the same issue, turning off the hardware acceleration worked for me.
Please follow the steps below.
I first reported the Netflix problem back in November of 2020. That was six months ago. I received three different emails from Edge feedback reporting that the problem was fixed. You said a month a go that with my help you discovered that the real problem was related to "binary signing." With due respect, why are we still waiting for a fix?
We found more binaries that were affected by the signing issue - your help debugging it with me was super helpful - it confirmed this analysis. So, sigh, my expectations for a full fix are pinned now to the "5C" release or the optional updates that will ship late May (and will be part of the mandatory security update early June).
Thanks
Arvind