Windows Update caused reserved port range conflict - unable to start Swarm now

[GoZippy]

For some reason - port 7801 which was working fine for a long time is now in the reserved range. Not sure what added the block range but it is there now. I need to know how to start with alternative port inside of windows - I do not see the selection option within the batch file to launch. Ideas? Also - might be good to move default port to 8850 as this is outside the ranges of known windows reservation blocks now...

[GoZippy]

What I did as a work-around for now
net stop winnat
net start winnat
Then I verified tcp exclusions again with
netsh interface ipv4 show excludedportrange protocol=tcp

...and the aggressive reservation was gone finally and it allowed me to start the UI

[bman654]

edit the launch script to add --port cli argument.

SwarmUI/docs/Command Line Arguments.md

Line 20 in 8c9c416

`--port` | `7801` | Can be used to override the 'Network.Port' server setting.

[mcmonkey4eva]

rather, run the launch script with --port xyz or make your own script that calls the base launch script. Do not edit source files directly except when making PRs.

[GoZippy]

I guess the point was to suggest using a non standard default port now that Windows has taken over all the hypervisor port reservations with wsl and docker desktop implementations... anyhow I managed to stop it all and start over again.

[FurkanGozukara]

this explains why i couldnt launch it like before on runpod until i manually feed port :D

[mcmonkey4eva]

I don't think this user's issue with windows nat reservations is related to server stuff (which, yknow, is generally linux)

[GoZippy]

For home users - especially - running on consumer equipment with the provided install options for WIN - it may be handy to have some thought about the port reservations that hit recently with Windows Update. Windows HTTP.sys reservation conflict
Sometimes Windows’ internal HTTP API (used by IIS or similar services) reserves ports silently. Some recent update caused a massive amount of reservations that conflict with a lot of services I used - but only on Win10 so I think it was done on purpose to push people to upgrade to WIN11+