This problem was first seen in Edge 113.
I have a Windows service that exposes an HTTPS://localhost endpoint for my web application to communicate with. During the installation of the service, I create a localhost certificate bound to the relevant port.
If the browser is running when the service is installed (a typical scenario), the certificate I just created is not accepted by Edge. I receive ERR_CERT_INVALID errors in the console. Logging the user in/out, reloading the page, restarting the service, nothing helps. But, if I restart Edge, things start working.
I believe this has something to do with the Root Certificate Store becoming officially active in Edge 113.
Is there any way that I can get Edge to accept this new certificate without restarting it? Either in my web app, or something my installer can do?
