I have some programs running on start-up like Everything. UAC prompts every time the Windows starts. How can I set a program to make sure that no intervening prompt would appear during start-up?
Task scheduler is an ok solution for something that runs on startup. But the most flexible way to do this is to use the Microsoft Application Compatibility Toolkit. It enables you to directly disable UAC for any application you decide to trust. The compatibility fix you need to select is RunAsInvoker.
To disable UAC prompts for one application only you have to use the Microsoft Application Compatibility Toolkit:
You have to run, as administrator, the correct "Compatibility Administrator" program. There are two of them, one for 32bit applications and one for 64bit applications.
- On the left hand tree menu, on the bottom is "Custom Databases", and under it "New Database(1) [Untitled_1]"
- Right click on the "New Database(1) [Untitled_1]"; select Create New, and Application Fix.
- Enter the name and other details for the application you want to alter behavior on and then browse to it and select it.
- Click Next until you are in the Compatibility Fixes screen.
- On the Compatibility Fixes screen, find the item RunAsInvoker, and check it.
- Click Next and then Finish.
- Select File and Save As.
- Save the file as [filename].SDB in a directory you can type easily on the command line.
- Open a Command Prompt as administrator.
Run the command: sdbinst [drive]:\[path]\[filename].sdb & pause (For example I was fixing the UAC for Clover and the command I typed was:
sdbinst "C:\Program Files (x86)\Clover\Clover.SDB" & pause
You should get a new window that says:
Installation of [name] complete.
Press any key to continue . . .
And that worked for me... Good Luck! - Sy
Task scheduler is your friend (Basic Task - Start Program at Log On - check Highest privileges).
Don't forget to remove (or move) your current startup icon or registry entry afterwards.
I was getting UAC prompts for CPU-Z and Malwarebytes, even though I had configured them to run as administrator, and in own memory space etc.
I had to go to administrative tools, local security policy, security options, user account control: behaviour of the the elevation prompt for administrators in admin approval mode. In that you get a few options for behaviour, selecting the elevate without prompting got rid of annoying warnings and system hasn't been compromised to date.
I'm running Windows 7 Enterprise 64 bit.
A third party program you might want to take a look at is called UAC Trust Shortcut 1.0
Basically you just download the program and enter in the .exe location and a name for the file and the icon will be placed on your desktop. The service will run in the background to allow easy access to any of your account restricted links.
The download can be found here: http://www.itknowledge24.com/
I had that problem with one app. At startup popup a window to permit it to run, I used many answers but the solution was to click on Unblock in Properties.
Was looking for a method of opening a third party security program as Administrator on system startup, (several of its features require it be started in Admin mode for the features to function as configured).
Here's the process worked through to arrive at the desired result:
- Changed the application launch properties to 'Run as Administrator': FAIL #1
- Created a desktop shortcut with Admin privileges and added it to the 'Startup' group. While the application opened, it did not open in Administrator mode: FAIL #2
- User Task Scheduler to open it on system start (using the method provided by the winaero blog) but as the application prompted a UAC question, it wouldn't load: FAIL #3
- Lost an hour of life downloading, installing and working through 'Microsoft Application Compatibility Toolkit': FAIL #4
- Won't class this as a failure, but looked at UAC Trust, found it didn't address the question posed here.
At this point, somewhat invested in the, '15 minute job' now morphed into, 'Day 2' status. Felt the needed components were at hand but was blind to them.
Reassessed the parameters of the problem and employing the Kalashnikov engineering rule #1 (whether the mechanism is clean or dirty, it should work) reconsidered each known element, not looking for what was missing, but for what parameters could be altered without shifting the desired goal, the 'automatic start of a 3rd party app in Admin mode'.
Returned to the Task Scheduler, reworking task switching the Trigger from on system startup to on log on and on the next login, the application started, in Admin mode. Huzzah! Success!
Kudos to winaero for providing the comprehensive visual and written documentation. If I weren't technically oriented, I would have tried their Tweaker. It's what I'll use on the Windows 10 systems.
If you right click on the application executable, click properties then on the compatibility tab select "Run as Administrator" then click apply, you should no longer get the warning box.