Local Send and port 53317

max milans 10 Reputation points
2026-09-27T09:24:01.06+00:00

Hi, I just install buil 26340.9577 and Localsend say me :
" SocketException: Failed to create server socket (OS Error: Tentativo di accesso al socket con modalità non consentite dalle rispettive autorizzazioni di

accesso.

, errno = 10013), address = 0.0.0.0, port = 53317"

So I changed the port to one under 10000, I used 9300 (I read this in an old blog) and Localsend server turns on without errors ! There is some problems with ports in this win version ? I have many istance of Localsend in other dispositives ( Smartphone, Tablet, Notebook) and so I must change le port to all of them !

How can I fix ?

Windows Insider program | Apps on Insider preview
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. max milans 10 Reputation points
    2026-10-24T17:58:53.9766667+00:00

    I have fixed It with the help of another user in windows insider forum.
    Was Windows that blocked some ports interval (also 5300 to 5400) after new update.
    I relese that ports and so all goes well.

    Windows next start those ports was free.

    And all goes well.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Lucus-V 14,420 Reputation points Microsoft External Staff Moderator
    2026-09-29T18:53:47.28+00:00

    Hi max milans,

    Thank you for posting in the Microsoft Community.

    I noticed that you're currently running a Windows Insider build (26340.9577). Since Insider builds can sometimes introduce changes to networking, security, or port management that are not present in stable releases, I'd like to better understand whether the Insider build may be related to what you're experiencing.

    Could you let us know if LocalSend was working normally before you installed this Insider build?

    If possible, have you tried reverting to the previous Windows build to see whether port 53317 becomes available again and LocalSend starts normally without changing its configuration? This would help determine whether the issue is specific to the current Insider build or if another factor is involved.

    Also, if you have not already done so, please let us know whether any firewall, security software, or network-related settings were changed around the time the issue began.

    I look forward to your update.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.