Unfortunately it seems that there is currently no way to use Edge in a MS webbrowser control without using third party addons. While the proposed "solution" to add dword:00002ee1 to FEATURE_BROWSER_EMULATION causes the webbrowser to (falsely) report Edge/12.9200_AGENT as USER_AGENT, in fact it still uses the Trident engine to render the web content. So it seems that Microsoft had planned to support Edge in webbrowser control but did not get finished and forgot to take out the corresponding Emulation key. You can verify this by browsing to where the webbrowser control scores between 342 and 347 points (the same as IE11), while Edge scores 397 points.