Windows always asking to run application (ie: Winamp)

[ovin08]

I just installed winamp and i really hate it when i have to select Yes to "Do you want to allow this program to make changes to your computer" when running winamp.

I've set the exe to run as administrator for all users. I even tried running it in compatibility mode for XP (because you dont have this issue in XP, wishful thinking).
I even set the persmissions to full access for SYSTEM/Administrator/Users in the security tab.
Im also an admin on this computer.
I know im not the only one that is pissed of when windows constantly asks you to run an application if you already selected to run it as admin.

It would be great if you could select an option to have windows store the program on some "safe" list where it wont ask you this crap anymore.

Any help would be great

 

[Capella]

As far as I know, it cannot be done....Its just clicking on a button lol. You can turn off UAC if it really annoys you. Go to start menu and type in uac. It is the first one that appears. You can also configure it so that it doesn't dim your screen.
hope this helps!

 

[rigelt]

some problem here - resolved

I had the same problem you described: every time I launched Winamp UAC would prompt me.
The cause was simple. I moved Winamp configuration files from a previous installation to my new Windows 7 Winamp environment. Some statements in those config files caused Winamp and some plugins to behave bogus.
To reset your windows installation for testing purposes > just move the folder %appdata%\winamp to a different location on your comp. Now restart Winamp and go through the configuration dialog. From now on you shouldn't be prompted with UAC anymore.
Of course you want to access your old media library with the whole playcount and favorites history! Shutdown Winamp and locate \Winamp\Plugins\ml\ in your old %appdata%\winamp. That \ml subfolder holds your entire media library. Now copy the \ml subfolder to the newly created %appdata%\winamp - that's it.
Good Luck.

 

[kazimir82]

Late reply to an old post, but I came accross this and thought I'd just post another (bebtter, imho) solution.

The problem is caused by Winamp's Settings folder having default security restrictions. Here's how to fix that:

• Start > Run (or press Winkey+R) and run this: %appdata%
  You can also open any windows explorer window and enter %appdata% in the address/location bar.
  
  
• In the appdata folder, there's a Winamp folder. Right click on that, choose Properties, click the Security tab.
  
  
• In the top list (Groups or user names), see if there's something called "Everyone". If there isn't, click Edit, Add, enter "Everyone" (without quotes) in the bottom white field and OK.
  
  
• Now select Everyone in the top list, and in the bottom list (Permissions for Everyone) check the first 'Allow' box (for "Full control"). All the others should be checked as well, and all Deny boxes should be UNchecked. Click OK, and OK again.

Winamp should now start without irritating DO YOU WANT TO ALLOW THIS PROGRAM etc popup!

 

[gloanx]

What worked for me is reinstalling winamp using run as administrator.

You can right click on the winamp setup exe file and select run as administrator to execute the file.

Or maybe under compatibility tab, check run as administrator check box.

 

[coolnezz]

I know this is really old but just want to say this method worked for me.
Installed the latest version of Winamp and UAC started popping up.
Re-ran .exe installer as Administrator and no more UAC pop ups.
Thanks for this info.

What worked for me is reinstalling winamp using run as administrator.

You can right click on the winamp setup exe file and select run as administrator to execute the file.

Or maybe under compatibility tab, check run as administrator check box.

 

[cytherian]

I became frustrated to no end with this issue. There is a smattering of posts about this problem, over on the WinAmp forum and various others, with mixed results. Some people found advice given worked while others didn't.

The culprit appears to be the file "winamp.ini". This is located over in C:\Users\[username]\AppData\Roaming\Winamp. Within this file is a variable "config_extlist=". Trailing after that is a list of various supported file types. Some suggestions said to remove "NSA" and save. I tried that and it didn't work. I figured I'd just delete all of the values for that variable and let WinAmp rebuild it. When I did this, it WORKED.

After I ran WinAmp successfully without any UAC prompt, I went back to the winamp.ini file and found that this variable didn't auto-update. Yet, my file associations for WinAmp worked fine. Not sure what purpose it serves, but it doesn't seem to be critical at least for normal use.

 

[MourningStar]

... Some people found advice given worked while others didn't.
.... When I did this, it WORKED. ...

glad it worked for you, did not work for me -

 

[MourningStar]

... Some people found advice given worked while others didn't.
.... When I did this, it WORKED. ...

glad it worked for you, did not work for me -

what did work for me is via the tutorial link posted below. And if it works for me, probably the world's numero uno 'puter putz, it will work for anyone :

http://www.sevenforums.com/tutorials/11949-elevated-program-shortcut-without-uac-prompt-create.html

 

[cytherian]

Sorry, I was away over the holiday.

I later discovered that what I did "broke" Winamp for media other than MP3. So, it's not good to manually edit that variable.

Basically when you first run Winamp after installing it (running as Administrator), be sure to go over to the properties for supported File associations, then manually uncheck several of the file types you know you'll not use (like "NSA"), then save. It will cause that config variable to be rebuilt. I found that when this took place, WinAmp started working fine without any UAC prompts.

 

[Mark Phelps]

I've been using WinAMP for years -- and never had it prompt for permissions, Maybe that's because I did not set it to run as Administrator.

 

[cytherian]

I suspect it was an issue with some updates that were introduced later. So, if you had installed earlier, it wouldn't be a problem.