[Problem/Bug]: Registry Key Changes in Recent WebView2 Runtime Versions #5340
Description
What happened?
A customer recently updated to the latest version of the Microsoft WebView2 runtime (version 139.0.3405.86). This update introduced stricter cookie policies, requiring explicit permission for third-party websites to set cookies—especially when those URLs belong to a different domain than the one being visited.
To allow these cookies and ensure proper application functionality, a registry key must be configured:
Runtime version: 139.0.3405.86
Registry Key Location Change:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\WebView2\CookiesAllowedForUrls
Importance
This change is blocking core functionality in our application. Without adding the necessary third-party URLs to the registry, the app fails to launch or operate correctly. Once the URLs are added, everything works as expected.
We’re currently investigating whether this behavior is a result of a deliberate change in the latest WebView2 release?
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
139.0.3405.86
SDK Version
No response
Framework
WPF
Operating System
Windows 11
OS Version
No response
Repro steps
From a Single Page Application (SPA), we attempt to open a popup window that navigates to a URL with a different domain than the parent application. In this popup:
A cookie is set for the new domain.
However, during subsequent redirects within the popup window, the previously set cookie is not sent with the requests.
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
Regression in newer Runtime
Last working version (if regression)
No response