With the door in 1842 Free,

I open SA, after launch the service manually 'sencha service start', immediately log shows that the port is used, see log below

C: \ Users \ Callias \ bin \ Sencha \ Cmd \ 6.1.2.15> Sencha service start
Wat!
configFile: C: \ Users \ Callias \ bin \ Sencha \ Cmd \ 6.1.2.15 \ sencha.cfg
Sencha Cmd v6.1.2.15
[WRN] FAILED [email protected]: 1842: java.net.BindException: Addr
ess already in use: bind
[WRN] FAILED [email protected]: java.net.BindException: Add
ress already in use: bind
[ERR] Address already in use: bind
If I close my SA and relaunch the service manually 'sencha service start' I do not see more in the log that the port is used

C: \ Users \ Callias \ bin \ Sencha \ Cmd \ 6.1.2.15> Sencha service start
Wat!
configFile: C: \ Users \ Callias \ bin \ Sencha \ Cmd \ 6.1.2.15 \ sencha.cfg
Sencha Cmd v6.1.2.15

I do not know how SA works behind the scenes but I think that's going to occupy the port in 1842,
I also tried CMD alone without SA works perfectly, I created an app using the command 'generated app' and saw that works with 'app watch'