[gui error report] Error: Initializing daemon...

[4verage]

• Desktop: 0.41.2
• OS: win32 10.0.22631 x64
• Electron: 34.2.0
• Chrome: 132.0.6834.196

Error: Initializing daemon...
Kubo version: 0.33.2
Repo version: 16
System version: amd64/windows
Golang version: go1.23.6
PeerID: 12D3KooWDYPKDWbAGJqyuftqi36JR9PiNP3kPesaoL8cV6WXhG5s
2025-02-14T09:58:28.732-0500	ERROR	core	core/builder.go:158	constructing the node: could not build arguments for function "github.com/ipfs/kubo/core/node".PeerWith.func1 (github.com/ipfs/[email protected]/core/node/peering.go:30): failed to build *peering.PeeringService: could not build arguments for function "github.com/ipfs/kubo/core/node".Peering (github.com/ipfs/[email protected]/core/node/peering.go:14): failed to build host.Host: received non-nil error from function "github.com/ipfs/kubo/core/node/libp2p".Host (github.com/ipfs/[email protected]/core/node/libp2p/host.go:41): failed to listen on any addresses: [listen tcp4 0.0.0.0:4001: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted. listen tcp6 [::]:4001: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted. listen udp4 0.0.0.0:4001: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted. listen udp6 [::]:4001: bind: Only one usage of each socket address (protocol/network address/port) is norm

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We are triaging issues on weekly basis and aim to give initial feedback within a few business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.tech if you just need general support.