starting SLSK in Win 10

[gorblimey]

I've just "upgraded" from Win7 to WIn10, and now nothing works.  I have installed the current version but Win10 is practising the Gandalf Move.  What incantations do I need?

[gorblimey]

Hokay...  Build Number: 2024.6.30, Win 10 Home.  I can generate a mob of screenshots, I guess I use the paperclip?

Every time I try to Connect I get "Login failed. Reported failure reason: socket error.  Please change your login settings in the Options tab and try reconnecting."

I've attached a login screenshot.

[gorblimey]

These are all the screenshots I can think of.  Something's bugging me about the Windows firewall settings.  The UDP settings are cloned from the TCP settings, I put them in just in case.  The router settings worked well with slsk157NS13e in Win 7.

[Caveman]

If you upgraded to Win10 from 7 without doing a clean install, it's possibly a bad config between the two versions either in Winsock or Soulseek itself. A few things I would do:

Run PowerShell as Adminsitrator and run these commands:

New-NetFirewallRule -DisplayName "Soulseek" -Program "$env:LOCALAPPDATA\SoulseekQt\SoulseekQt.exe" -Action Allow -Direction Inbound
New-NetFirewallRule -DisplayName "Soulseek Out" -Program "$env:LOCALAPPDATA\SoulseekQt\SoulseekQt.exe" -Action Allow -Direction Outbound

Then, run these. May need to run command prompt as admin and not powershell:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns

Restart machine, if that doesn't work, then reinstall Soulseek. 

[gorblimey]

Thanks for the reply cobber.  The, ah... upgrade...  was forced on me when the old box died.  I did think about getting a current-ish processor, but the amount of work to get Win 7 onto a useful processor is staggering.  So, a new box and Win 10.  A clean install :(  10 is not Microsoft's best effort.  Win2K was.  Desktop AND Server.

I have copied your suggested action to a nice folder, but I'm trying to figure what is bugging me in the firewall setup.  I know it is really simple, or I would have figured the problem hours ago.

[gorblimey]

I put SLSK through Microsoft/SysInternals/TCPView.  We'll ignore that SLSK recognises TCPv6, just wonder where Server Port 33079 comes in.

While I'm here, it seems Win10 does have (or it says it has) Winsock 2.~.  I'll admit right now that I do not understand Socket Theory or Practice.

I'm getting very sad, because SLSK was a very good file-sharing application.

[gorblimey]

Where I am now...  Thanks Caveman.

I figured out my s***-up with Windows Firewall.  The Inbound and Outbound were identical [:-  And I deleted the UDP versions, SLSK doesn't know what UDP is.

DId the Power Shell and CMD as Admin, no joy.  And, did anyone notice that TCPView shows SLSK listening on local ports 64159 and 64160, but Remote Address is 0.0.0.0 with no sign of 33079 Server port.  Windows 10 is very proud of its Sockets 2.0...  I have no idea what a Socket is.

slsk157NS13e looks very tempting ATM, or maybe go further to slsk156c...  which version does slskLSPFix fix?