The following diagram shows the spectrum of apps, from maximum reach, to maximum power: To access all the powerful capabilities of a native platform, use a native app. As a Web developer, you can reuse most of your code across different platforms. This decision hinges on the tradeoff between reach and power: Hybrid app approachĭevelopers must often decide between building a web app or a native app. To start building a WebView2 app, see Get started with WebView2. With WebView2, you can embed web code in different parts of your native app, or build all of the native app within a single WebView2 instance. The WebView2 control uses Microsoft Edge as the rendering engine to display the web content in native apps. You can also try ending the errant process from the Task Manager, breaking it out of the error loop.The Microsoft Edge WebView2 control allows you to embed web technologies (HTML, CSS, and JavaScript) in your native apps. If you see the runtime creating problems on your computer, report the issue to Microsoft and restart your computer. Normally, the processes making up the runtime will not display a resource usage higher than 100 MB of RAM and barely a fraction of CPU. The Edge WebView2 engine is designed to render HTML and CSS elements without taking up too many system resources. And it’s here to stay, considering the increasing number of apps adopting the hybrid approach. What Should You Do About the Microsoft Edge WebView2 Runtime?įirst, know that the WebView2 runtime is not a virus but a legitimate component of Windows released by Microsoft. And after all that effort, it might just come back due to some random app installing it. Accessing its setup requires locating its directory, which in turn requires that you type the exact version number of your Edge WebView2 runtime. You can technically still force an uninstall through the Command Prompt, though it’s a tricky method.

Edge webview2