Allow app to make changes

[wdadli1]

Every time I start Winamp 5.8, I get the UAC question about allowing the app to make changes to my device. Is there any way to stop this from happening? I tried giving full permission to Everyone (one of the solutions I found), but that didn't do the trick.

[DJ-Garybaldy]

Best advice I can give you is Switch OFF UAC

[musicf8]

Telling people to turn off UAC is very bad advice as it opens your system up more to security risks, essentially allowing any and all programs to make system changes w/o restriction.

@wdadli1, do you have any plugins that might affect it? Have you tried to see if the problem persists with a clean install of 5.666?

[DJ-Garybaldy]

Had UAC switched off for a couple of years now and I've never had an issue...

[musicf8]

Just because you haven't had an issue doesn't mean it isn't a security risk (same with things like never applying security patches or never changing the default pw on devices).

By turning off UAC you're giving all program admin rights which opens your computer up to system changes, primarily malware. While you may be cautious or know where programs come from, things happen.

Anyway, if one program is causing constant UAC prompts for no reason, it's usually a very old program (pre-vista), very badly created program (developer issue), a program made to change system settings (e.g. misc windows 10 tweakers), or something else is causing the program to force uac prompts, which is why I wonder if a plug-in might be a cause. I never get UAC prompts on my winamp (5.666) outside of installing plug-ins

[rtx4090]

Turning off UAC is indeed a very bad idea. Instead, do a clean uninstall. Then do a minimal install of 5.666 with only the required components. Should solve the issue.

[SudenKapala]

Originally Posted by wdadli1

Every time I start Winamp 5.8, I get the UAC question about allowing the app to make changes to my device. Is there any way to stop this from happening? I tried giving full permission to Everyone (one of the solutions I found), but that didn't do the trick.

Any luck yet?

I had something similar recently, when installing other versions. But only just after a new install.

Did you try starting Amp (once) as an Admin? That did the trick for me; I reckon because it then could go through the post-install setup phase without hindrance. You probably tried this, but I wanted to be sure.