SLSK not closing properly

[vancouv...@gmail.com]

As of very recently I have the Soulseek is not closing properly (Windows 7 64-bit).  Going to Task Manager and trying to end the process, doesn't work.  I've never known TM to not shut down a program.  So I'm not sure if it's something to do with SLSK or my computer.  Does anyone know how you can check to see what the problem is?  Maybe once I figure that out I can find a solution.  Which if anyone has, please let me know.

Thanks.

[vancouv...@gmail.com]

I thought the problem was solved but unfortunately that isn't the case.  However now with utorrent experiencing the same issue, my guess is that this is a Windows problem. 

[paul....@gmail.com]

Actually, I'm having the same problem and have to shut down/restart (Windows 7 Ultimate, 64-bit) to get rid of soulseek. Otherwise, it just hangs there with a 'Not Responding' message in the title bar and the 'hourglass' just spinning away. Reinstalling soulseek doesn't solve the problem and I don't have a problem with my bittorrent client (qBittorrent) either.

[vancouv...@gmail.com]

So it must be a Windows issue then.  We're using the same version and having the same problem.  Everything was fine prior to the last update.  Maybe rolling back Windows to before the updates, even though they were labelled as "important", and installing them will work?

[tbsn]

Windows Update problem, fix hasn't been rolled out to automatic updates yet but is available here:

https://support.microsoft.com/en-us/help/4345459/stop-error-0xd1-after-a-race-condition-occurs-in-windows-7-service-pac

[paul....@gmail.com]

Thanks! That's brilliant - if it works. However, when I went to the Microsoft catalog (https://www.catalog.update.microsoft.com/Search.aspx?q=KB4345459) I found two downloads for this issue (KB345549) and the descriptions for both are identical. The only way to tell them apart is that the one at the top of the list is 37.7MB and the one at the bottom is 23.9MB. Which one do I choose?

Also, in my own attempt to fix this issue I found that there were issues with the latest update to .NET 4.7.2 which caused COM problems (https://developercommunity.visualstudio.com/content/problem/291884/july-2018-cumlative-security-and-quality-update-kb.html). I have got as far as uninstalling both the update itself and the cumulative rollup. Did you do anything about this? Do I need to re-install these before applying the fix above?

Thanks again for your help, any further help will be very much appreciated.

Paul

[vancouv...@gmail.com]

I'd like to know the answer to that question as well.  However I'm going to, once again, upgrade to Windows 10.  See how that goes.

[vancouv...@gmail.com]

I see the update mentioned, .NET 4.7.2, how did it go with the uninstall? Also what was the rollup that you removed? I have four that came after the aforementioned update.

[tbsn]

There are versions for x64 and x86. I just installed it on top of the regular updates. Problem solved.

[vancouv...@gmail.com]

Wow I feel silly now for not looking at that more closely.  Thank you.

[paul....@gmail.com]

Dammit! I Iooked and looked and looked and still didn't see that there were x86 and x64 versions. Thank you once again, I feel pretty silly too. I'll let everone know what happens.

[paul....@gmail.com]

The uninstall went without incident but now Windows Update wants me to reinstall them. They are:

• 2018-07 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 7 and Server 2008 R2 for x64 (KB4340556)

• Microsoft .NET Framework 4.7.2 for Windows 7 for x64 (KB4054530)

I haven't seen any other updates so I don't know anything about the four more that you mentioned. I'll post what happens when I do the reinstall, thanks for all your comments.

[vancouv...@gmail.com]

In having to reinstall Windows on my PC, I decided to make the upgrade to Windows 10.  Now I don't know where things are so I can't find the names of the rollups that came after the .NET update.

[RandomTox]

Build 2017.2.25 doesn't close now under MacOS 10.13.6.  Have to force quit the app every time which is really annoying.

Any newer build on the horizon that gets around this?  Thanks.

[jpro...@gmail.com]

What I found works is to firstly disconnect from the server within slsk then to quit the program. This somehow seems to release whatever resources it was using and will then close properly.

[mattdag...@gmail.com]

Thank you for addressing this. I had been noticing messages for several days now when I started my client telling me that "x port is already being used by another client" and was baffled. I never thought to check the task manager to see if other instances of soulseek were still running until a couple of days ago, and sure enough, the soulseek process still showed in task manager, and couldn't be forced stopped. Like others have mentioned, the only way to clear it out is to reboot the computer. I was afraid this was going to be something affecting only me, since I couldn't find anyone mentioning it elsewhere on the web. Also, thank you to the commenter who linked the Windows hotfix. You guys are a very resourceful bunch. *hat tip

[planet...@gmail.com]

That update fixed the problem for me on Win7, thanks!