>>Edge does NOT allow activeX controls and does NOT run BHO if I read descriptions correctly.
>
>That is kind of irrelevant. It is not whether activeX to run into edge, but whether edge runs in an activeX control.

Perhaps I'd write "runs as an activeX control" but pretty certain we refer to nearly identical use case
I mentioned "running activeX controls" and BHO as possible ways encapsulate "external" functionality to apply to the loaded HTML in Document.All of IE DOM model. My typical "design" starting early this century was a "DomWorker" object to load either into a container also hosting WebBrowser or an instance of InternetExplorer.Application. One customer wanted that DomWorker functionality as BHO, so there will be maintainance.
Insofar a I mentioned "as in createobject("InternetExplorer.Application"), which I also used sometimes in roboting to better combat memory leaks.", this was necessary, as many in-process HTML-munging objects were prone to gobble up memory like crazy, whereas munging in multiple processes was easier to control memory-wise and the added cross-process marshalling cost was not relevant compared to Internet latency and loading at that neolithic period. BHO was done for customer wanting tighter coupling of "DomWorker" inside the process - premature optimization.
>
>>So IMO it is uncertain if IE11 "stays" installed on W10 after support ends in 2 weeks.

>I think you got the wrong date as well. Its state June 6th 2022. So one more year to go before it is left unsupported.

You are totally correct, my bad.

>I have no reason to think that this would mean the IE runtimes needed for the webbrowser control will be uninstalled as it clearly still is supported for the other versions of Windows 10.
...
>Would this indicate that de-installing IE would leave the runtime DLLs still in there ?

On https://docs.microsoft.com/en-US/lifecycle/faq/internet-explorer-microsoft-edge

Windows 10 Semi Annual Channel Internet Explorer 11
Starting June 15, 2022, the IE11 desktop application will no longer be supported.

can be interpreted both ways. No idea if that should be read as "Exe still there, no icon on desktop" or

loIE = createobject("InternetExplorer.Application")
loIE.Visible = .t.

not working any more. I hope for an installer for dlls and exe...

Better ARM windows currently seems out of favor again, but having WebBrowser - functionality in Xamarin/IL/C# one of the areas tempting me to look both into Webview2 and the simpler WebDriver, the latter offering automation option through similar interfaces (as they all stem from Selenium) in Chrome and FireFox as well. but that is MY target ;-)