Winamp prevents my computer from shutting down

[Kamiks0320]

Recently I switched to Bento skin and I think from this moment pc won't turn off w/out me turning off Winamp first. I just receive Windows notification that Winamp is still running and can't turn off pc because of that.

[MrSinatra]

Do u leave the music paused?

Doubtful it's the bento skin.

We'd need an info report to say more.

[Kamiks0320]

No I dont, it doesn't matter if I leave it or not.

[toejam119]

I have the same issue. Whenever I use a modern skin, e.g. Bento Big, Windows is prevented to shut down by Winamp until the app kill timout runs out and Windows forces Winamp to close (1-2 mins?). If I switch to classic skin the problem disappears. I can also shut down Winamp manually (clicking X on top right corner) no problem.

- Windows 7 x64 Home Edition (with newest security updates 2019.01.14)
- Winamp 5.8 beta build 3660 full en us
- Tried uninstalling Winamp and re-installing (fresh) using standard installation, no difference.
- Tried uninstalling 5.8 beta and installing 5.666 full en us, no difference.
- Tried uninstalling Avast antivirus free, no difference.
- Tried starting Winamp in safe-mode, no difference.

- Only difference so far is using Winamp in classic skin.

I started noticing this problem around new years 2018-2019, maybe December or January.

[Sopwith]

Hello WinAmp Community,

I'm just here to both identify this issue to the community, and put a post here for Google to redirect any other poor saps like myself here to save them some time.

My Windows 7 computer is running the latest (5.8.3660) build of WinAmp. I have notice that on shutdown, the system hangs on a phantom "Search Results" window or process. When I have task manager up, no such process exists. But there it is holding up my shutdown. Unless I hit "end now", the window would remain up for about 10-240 seconds, depending on how long I had been running WinAmp, then it would close and the computer would shut down. I did some tinkering and happened to figure out that when I closed WinAmp, the message immediately went away and the computer would shut down. So I'm going to just assert plainly that this is an issue with the current build in Windows 7.

Luckily I can use an AutoHotkey script with an OnExit subroutine that kills the process upon shutdown to avoid this from actually being an issue for me. Still, bad form, WinAmp. Bad form. lol. Again, not sure what it is, no "Search Results" thing exists as a process or description. It's only on shutdown does it come up with a message - and even then, no process matches the description. Anyways. Hope this helps someone.

Example AutoHotkey Script:

OnExit("SearchResults")
return

SearchResults()
{
Process, Close, winamp.exe
}
return

[Sopwith]

Sorry, one adjustment to the script here... The DllCall basically tells the Win7 kernel that, on shutdown, end this script first when you start your process-exiting. This is important because on my machine WinAmp was holding everything up - and without the script ending, it doesn't trigger my OnExit command, so WinAmp doesn't close...

#Persistent
DllCall("kernel32.dll\SetProcessShutdownParameters", UInt, 0x4FF, UInt, 0)
OnExit("ShutdownWinAmp")
return

ShutdownWinAmp()
{
Process, Close, winamp.exe
}
return

(Once again: this is a script for AutoHotkey. Download, install, make this an .AHK file, and run it on start-up {make a shortcut in your Start>Programs>Startup folder})

And there was much rejoicing.

[toejam119]

Originally Posted by Sopwith

Sorry, one adjustment to the script here... The DllCall basically tells the Win7 kernel that, on shutdown, end this script first when you start your process-exiting. This is important because on my machine WinAmp was holding everything up - and without the script ending, it doesn't trigger my OnExit command, so WinAmp doesn't close...



(Once again: this is a script for AutoHotkey. Download, install, make this an .AHK file, and run it on start-up {make a shortcut in your Start>Programs>Startup folder})

And there was much rejoicing.

Does this close Winamp normally or force kill it? Because if you force kill it, it won't save the changes made during that session.

[Sopwith]

Pretty sure it's a force-kill. I don't really make changes during my sessions. You should logically be saving your work or close the app normally (to effect a save) before hitting the shutdown button. My method is admittedly brute-force. The root of this problem is that the program doesn't seem to want to normal-close on shutdown.

[SubSonix]

Just adding that I have the same problem.

It doesn't do it at every shut down though, just randomly.

Windows 10

[Number_1]

http://forums.winamp.com/showthread.php?t=353513

problem is not new - It does exist since many years. See link

[MrSinatra]

http://forums.winamp.com/showthread.php?t=454223

[Flinck]

Figured out one solution to fix problem of Winamp 5.8 preventing Windows 10 (Home-version 64-bit) shutdown.

The problem lies within the official 5.8 beta release:

- If you have 5.8 installed, you must install Winamp 5.666 over the existing installation of 5.8.
After that, install 5.8 again over the 5.666. This will fix problem with 5.8s problem.

- Or if you have no Winamp installed currently, install 5.666 first before installing 5.8.

This solution has worked both for my PC and laptop. Hope anybody else finds this solution working for them.

Winamp 5.666 is still available for download at http://forums.winamp.com/showthread.php?t=373755

[oldboy]

Thanks Flinck!

This worked a charm for me. It's been bugging me for over a year. I've been hitting Pause to get around it, but was still a nuisance.

All is good.

[Wineroz]

I also had this issue after going to Windows 10 - and this fix seems to be working for now



But prior to that as a remedy I was using for the longest time a simple BAT file

code:
shutdown /r /f /t 0

X:\Y\Z

dir

The X stands for any non drive you do not utilize for any system purposes have, Y is some folder that you have do not intend to deleted ever and Z is also a folder that is suppose to be there every time but a one that it is unlikely that you will enter during your normal work-flow. And that is because if the system is to be immediately reset or closed, then first it needs to have the >>/t<< parameter and specify it with a number of second as 0. Secondly it has to start spinning all the HDD's by accessing some folder on them. But if that folder was already accessed by the operating system sometime after its current session have started, then this will not be enough, as that folder is somehow stored in memory- and so the path must go one step deeper. And if not- then the spinning of HDD's will start long after OS will show the closing screen, apparently at the very end of the resetting / closure . [This of course is of no importance if the user only has SSDs]


This BAT may still come in handy in regard to Winamp after some Windows 10 update when things go south - plus I also have some other software that blocks closure of the OS in the same way as Winamp deos

[MagikGimp]

This problem is back with the new release and the installing this version over that one trick doesn't work as far as I can make out. Didn't want to start a new thread as I'd have to reference to this one anyway!

[NJK]

Originally Posted by MagikGimp

This problem is back with the new release and the installing this version over that one trick doesn't work as far as I can make out. Didn't want to start a new thread as I'd have to reference to this one anyway!

--> http://forums.winamp.com/showthread.php?t=458828

[Toneplay]

I just completely deleted Winamp from my Windows 11 machine and reinstalled 5.9.1 Build 10029. I installed no plugins.

First I selected Big Bento skin, then started playing, then tried to shut down my machine. It failed.

On restarting, I tried the regular Bento skin, and started playing, then tried to shut down. It failed.

I then switched to Classic skin and started playing and tried to shut down, and it succeeded.

This is without any additional plugins installed.