Windows - Runner is not alive - Incorrect daemon port on run command

[AnthonyLELUYER]

Describe the bug
The Gauge executable on Windows will not find the correct port the daemon is launched on.

To Reproduce

1. Install the archive version of Gauge
2. Run the gauge daemon command in a Powershell terminal (gauge.exe daemon 57615)
3. Open a new Powershell terminal
4. Run the gauge command (gauge.exe .\specs\my_spec.spec)
5. See error

Logs

  Error Message: error reading from server: read tcp 127.0.0.1:63581->127.0.0.1:63580: wsarecv: An existing connection was forcibly closed by the remote host.
  Stacktrace:


  Error Message: Runner is not Alive
  Stacktrace:

Error occurred while waiting for runner process to finish.
Error : exit status 1
Successfully generated html-report to => C:\Users\REDACTEDUSER\Downloads\functional-test-framework\reports\html-report\index.html

Failed to kill Runner: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:63580: connectex: No connection could be made because the target machine actively refused it."

Expected behavior
The Gauge executable should find the daemon port, or let us specify it in the command or with environment variable.
I tried to set GAUGE_API_PORT with this command $env:GAUGE_API_PORT = 57615 but it's ignored by the Gauge run command.

Versions:

Gauge version: 1.4.3
Commit Hash: f98dd40

Plugins
-------
html-report (4.2.0)
python (0.4.0)
screenshot (0.1.0)

• OS [e.g. MacOS 10.15.6 (19G2021) please be specific ]: Windows 10 Enterprise 21H2 - 19044.3208
• Runner info (Please specify the correct version of Java/Node/Python/Dotnet/Ruby): Python 3.10.10
• IDE info (If using VS Code or Intellij IDEA): None

Additional context
I can't install it with npm, chocolatey nor windows installer as I don't have admin rights on this machine.