This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 28.999999999999996%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDB%3C/text%3E%3C/svg%3E)
Internet Explorer will go out of support on June 15 2022 (it's been a long ride). I believe the Windows Forms WebBrowser class still uses Trident, the IE rendering engine. Of course there are still apps out there using WebBrowser (I use one every day) with no or minimal maintenance energy. Assuming Trident will still work, does the EOL mean any negative implications for apps that use WebBrowser?
I think updating to WebView2 would be too much of a leap for many such apps.
The webbrowser control will continue to work after June 15, 2022. The biggest impact is there will not be any security updates anymore. I would recommend updating your app to use WebView2.
https://github.com/MicrosoftEdge/WebView2Feedback/issues/474
As I said, WebView2 may be too much of a lift, even assuming I have access to the source. And some legacy apps have no active maintainers or even no easily available source. One example is Wikipedia's AutoWikiBrowser, which has some volunteer maintainers but don't seem to have the bandwidth for such a significant change.
I added an comment on the above answer (which assumes it's "my" app and that I have the bandwidth to update it). But I also found that "the WebBrowser control will continue to work after the IE Desktop Browser end of life in 2022, until about 2029." For some definition of "work", I guess.
https://github.com/MicrosoftEdge/WebView2Feedback/issues/1371