Evergreen Webview2 Jun 2026

catch (WebView2RuntimeNotFoundException)

Total control over the exact rendering engine version, ensuring no unexpected UI breaking changes.

When you release an app that uses WebView2, you must distribute the WebView2 Runtime to your client machines, choosing between two official distribution models: the and the Fixed Version distribution mode . evergreen webview2

If you have ever maintained a CEF (Chromium Embedded Framework) or Electron app, you know the pain of the "massive bundle." Let’s compare the developer experience.

In the , the WebView2 runtime is not packaged inside your application installer. Instead, your application points to a shared instance of the runtime installed on the client machine. In the , the WebView2 runtime is not

Given that the Evergreen runtime is updated automatically, it is crucial to regularly test your application against the preview builds of Microsoft Edge (Beta, Dev, and Canary channels). These channels allow you to test your WebView2 app against upcoming features and platform changes before they are released into the production Evergreen runtime, ensuring a smooth user experience.

When you use Evergreen WebView2, your application uses a small DLL. When the app starts, the Loader looks for the WebView2 Runtime on the user's machine. These channels allow you to test your WebView2

bundled with your application. Instead, it is installed once on a client machine and shared across all applications that use it (such as Microsoft Teams or Outlook). Microsoft manages the updates for this runtime automatically, similar to how the Microsoft Edge browser is updated. Microsoft Learn Key Benefits Security & Compliance