SNI's Portrange gets randomly grabbed by Windows Services (e.g. Hyper-V)

[wordfcuk]

I am not sure how problematic this is for people over all, but SNI's Portrange lies in the range of ports that Windows services often grab for their usage (Hyper V loves hugging ports).

I personally have a workaround that works for me, but in general it might be smart to move SNI's portrange.

[JamesDunne]

Which port range are you referring to?

SNI listens on many ports for various services. Take a look at the Console (menu > Show Console) on startup to see what ports SNI listens on and let me know which are conflicting with Hyper V.

If I had to guess, the most problematic ports would be the ones in the dynamic port range which are kept for backwards compatibility with prior solutions, e.g. luabridge service on port 65398.

[wordfcuk]

In my case, it was Port 65398, so yes, the dynamic portrange indeed. I switched mine over to 49151 to escape the conundrum. This may just be a 'me' problem, cause I have a lot of company mandated software installed and I do not know which software grabs which ports to be honest.