[isp]

All versions of Windows Server are (for now) unaffected, i.e., Internet Explorer 11 continues to run [1].

There is also "Internet Explorer Mode" in Edge, which uses iexplore.exe under the hood.

Additionally, if somebody were _really_ desperate to launch iexplore.exe itself, then there are unsupported means to do so.

For example, via manually modifying the registry key "NotifyDisableIEOptions" under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Main\

My favourite hack though, which should not be used by anyone ever, is launching via the COM object interface, which bypasses the registry key check [2]. I have personally verified that this works(!)

[1] https://techcommunity.microsoft.com/t5/windows-it-pro-blog/i...

[2] https://twitter.com/aaaddress1/status/1523590203658862592

[Jaruzel]

If one is desperate, there is also the option of the classic Webview control in Visual Studio (or even the old VB6 version) which with little bit of UI added around it, can substitute for the real IE for certain enterprise legacy webapps.

A bit more effort, can also lock the control to only browse to the intended web service, and launch the default browser for any external links.

There's kind of a market for this type of solution in the legacy enterprise app space I think.

[omnibrain]

You can even use a registry key (per Application using the WebView control) to specify the function level/version to emulate.

[Zardoz84]

these WebView on VB6 isn't the IE6 engine ?

[Jaruzel]

No it's a wrapper around the installed version of IE.

As a sibling comment stated, you use the registry to tell the WebView what version of IE you want to emulate (on a per app basis).