Follow these steps to troubleshoot DRM playback issues in Microsoft Edge on Windows 11 Insider:
- Verify DRM component (Widevine) in Edge
- Open Edge.
- Go to
edge://componentsin the address bar. - Confirm that Widevine Content Decryption Module is present.
- If it is missing or shows an error, this indicates a DRM component problem.
- Check for profile-related DRM issues
The documented DRM issue occurs when
widevinecdm.dllis read from%LOCALAPPDATA%but not loaded intomsedge.exe. It should be read and loaded from the Edge application folder instead. To isolate a profile issue:- Create a new Edge profile (Settings → Profiles → Add profile).
- Try playing the same film in the new profile.
- If it works in the new profile, the original profile is likely blocking Widevine from loading correctly.
- Confirm HEVC/codec licensing if the content uses HEVC
If the film uses HEVC and Edge shows decoder/HEVC-related errors (for example in
edge://gpuoredge://media-internals):- Open PowerShell as Administrator.
- Check for installed HEVC packages:
Get-AppxPackage -AllUsers *HEVC* | Select-Object Name, PackageFullName - If an HEVC package is installed, remove it and any provisioned copy:
Get-AppxPackage *HEVC* | ForEach-Object { Remove-AppxPackage -Package $_.PackageFullName } Get-AppxProvisionedPackage -Online | Where-Object DisplayName -like "*HEVC*" | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName } - Restart the PC.
- Install the official HEVC Video Extensions from Microsoft Store (not from third‑party sources). A non‑Store HEVC extension can have an invalid license and break playback.
- Check if the issue is Insider build–related
Windows 11 Insider builds can introduce media/DRM regressions. If DRM playback works:
- On another non‑Insider device, or
- In a different browser on the same device, then the problem might be specific to the Insider build or Edge on that build.
- Ensure all latest cumulative/preview updates for the Insider channel are installed.
- If the issue started immediately after a specific build and only affects protected content, consider rolling back that build if possible or waiting for a newer Insider build that addresses media issues.
- Test in another browser To confirm it is Edge‑specific, test the same DRM content in another supported browser. If it works there, focus on Edge (profiles, components, codecs) rather than Windows itself.
If after these steps DRM content still fails only on the Insider build, report the issue via the Feedback Hub with details (Edge version, Windows build, site, and any errors from edge://media-internals).
References: