Starting Edge as a process immediately fires exited event
Hi! Recently I have encountered a rather annoying bug on Windows 11 IoT LTSC where I launch an edge as a process from my .net 9.0 C# code. I need to track Edge and if it exits for some reason I have to relaunch it. I'm tracking whether it has exited by subscribing to the Process.Exited event, but on the beforementioned operating system this event immediately fires even though the Edge itself visibly does not close and stays functional without any problem. This results in infinite edge processes getting launched, since every new instance also exits. Interestingly this issue does not occur when tested with other browsers nor it occurs on Windows 11 Pro, everything works completely fine in these two scenarios. I'm guessing IoT version has some kind of different power plan to reduce battery drainage and CPU usage if possible. My other assumption is that the msedge.exe available with default windows is just a parent process on the IoT version, and it just starts the actual processes needed to present the content of my web app. It'd be great if you could check this and come back to me. Thank you! Kind regards, Gallusz.
