liopleus Thanks for replying.
As I've stated, I did run a port scan via cmd through this command 'netstat -ano | findstr 48010'
there wasn't any process hanging that port.
Actually what I've found is that open-stream, in my case, gets that port busy then reports back that there's another process bound to it.
I was able to fix this by a little workaround, by running open-stream, scan the port via cmd, then I killed the process with this command..
taskkill /f /pid
then start hosting again, all of that must be done without closing open-stream
that's strange it looks like the app was shooting itself in the foot for some odd reasons.