When trying to start my Sui local network or executing any command on CMD I'm facing a tcp connect error with the Sui network

Everytime I try to start the sui local network a error like this one appears:

C:\Windows\System32>sui start --with-faucet --force-regenesis
2024-12-20T17:54:21.621053Z ERROR mysten_metrics::thread_stall_monitor: Thread stalled for 502ms
2024-12-20T17:54:24.437456Z ERROR mysten_metrics::thread_stall_monitor: Thread stall cleared after 3268ms
thread '2024-12-20T17:54:26.676109Z ERROR telemetry_subscribers: panicked at C:\a\sui\sui\crates\sui\src\sui_commands.rs:914:10:
called `Result::unwrap()` on an `Err` value: Wallet("Networking or low-level protocol error: HTTP error: error trying to connect: tcp connect error: The requested address is not valid in its context. (os error 10049)") panic.file="C:\\a\\sui\\sui\\crates\\sui\\src\\sui_commands.rs" panic.line=914 panic.column=10
main' panicked at C:\a\sui\sui\crates\sui\src\sui_commands.rs:914:10:
called `Result::unwrap()` on an `Err` value: Wallet("Networking or low-level protocol error: HTTP error: error trying to connect: tcp connect error: The requested address is not valid in its context. (os error 10049)")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Also recently realized that when executing the command sui client envs almost the same error appears:

C:\Windows\System32>sui client envs
Networking or low-level protocol error: HTTP error: error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)

Caused by:
    HTTP error: error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)

The first time I executed the sui local network on my pc all worked well without issues but once I turned off the pc the nightmare started, and that was 1 week ago, time have passed, but I’m still stuck, I would be really grateful if somebody could give some guide or support to fix my issue.

Just had the same issue. I was able to solve it by running:

$env:RUST_LOG="off,sui_node=info"; sui start --with-faucet --force-regenesis

in windows powershell.