M7701-1003 Netflix not working

Browser Support
1

Windows Laptop/PC
Brave Version 1.77.97 Chromium: 135.0.7049.84 (Official Build) (64-bit)

Trying to watch Netflix on my Brave Browser and I’m receiving the error code page Pardon the Interruption… Error Code: M7701-1003

netflix error
netflix error1920×1016 144 KB

Widevine error
Widevine error376×204 26.8 KB

  • Cleared history and cookies completely
  • Widevine is enabled (I have tried disabling, relaunching browser, enabling, relaunching browser)
  • Enabled All Cookies
  • brave://components/ shows Update Error with Widevine (see screenshot)
  • Reinstalled Brave from the website without uninstalling first

This is the first time I’ve received this error and after searching all of this discussion, each thread appears to get closed because the issue is never resolved. The only ones that are resolved are the ones that Widevine is enabled on.

I’m no developer but it’s clear its a Widevine issue.

Please help.

2

@bohemyththe sounds like you’re having a known issue where permissions on the folders containing your components is being changed. This can happen if someone has opened their browser using Run as administrator or can be a random bug that happens in automatic updates and all.

Best bet would be to try to follow the instructions as you see at https://github.com/brave/brave-browser/issues/38609#issuecomment-2195847971

Or different approach and explanation by a user https://github.com/brave/brave-browser/issues/38609#issuecomment-2196093284

3

I tried the two links but it didn’t make a change so after sifting through the mumbo jumbo that everyday joes have no way of deciphering, I remembered TakeOwnership that I used to use in the past.

It can be found here: https://www.majorgeeks.com/files/details/take_full_ownership_of_files_folders_registry_hack.html

Simply run it and it adds TakeOwnership to the context menu.

You right-click all Brave folder locations
C:\Users*user*\AppData\Local\BraveSoftware
C:\Program Files\BraveSoftware

and “Take Ownership”.

Fixes the issue as soon as it’s finished running.

No need for the 10 step process that you linked in your reply

1 Like
4

Yeah, I know those steps are a bit confusing. I think the steps providing by @clifton as provided is a bit helpful with some of the screenshots, but still can be tough for people. It would be nice if a simpler fix could be built in or if they can ever just prevent this from occurring in the first place.

I think @Mattches has been working on coming up with a simplified guide for people in an official article. Tagging him in so he can be aware of your tool and can decide if it’s something good to recommend.

At least is good to know you got it resolved. Thanks for sharing the update.