New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebView2 Evergreen installer no longer adds the registry key recommended for detection #2019
Comments
After further digging around in the registry I figured out that the runtime is now per-user installed (which is great news for our otherwise user installed app!) and thus the key is available here instead: So now it's just a problem for existing software out there and the documentation. |
Thank @psycholns for the post! @liminzhu made a post about it here: MicrosoftEdge/WebView2Announcements#37. But I agree we should have better permanent documentation about this. I will open an item to update the docs! Let me know if you have any other questions. |
It is necessary to change from checking hard coded registry path to another way. In .NET based framework (In my case, WPF) var clientInstalled = true;
try
{
var version = CoreWebView2Environment.GetAvailableBrowserVersionString();
}
catch (WebView2RuntimeNotFoundException)
{
clientInstalled = false;
} In WIN32 platform,
I haven't tried this way, but it has been mentioned by Distribute a WebView2 app and the WebView2 Runtime. |
I stucked at it in a while. pleaseeeeee update the document |
I just checked it again and I realized that:
Just share my experience |
Description
To verify that the webview2 runtime is installed we check (as recommended in https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution) the registry key at:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}
This has worked so far, but now, if uninstalling the webview2 component and installing it again won't add that key, and therefore our users without the runtime end up in a (manual) install loop.
Verified on 2 machines so far. And looking at our logs it seems to have been an issue since around the 3rd (no errors from installer, but no runtime detected afterwards either).
Version
Runtime: 96.0.1054.53
OS: Win10, 19043
(SDK: 1.0.992.28)
(Framework: WinForms)
Repro Steps
AB#37397652
The text was updated successfully, but these errors were encountered: