Thanks so much Brink, that worked!!! However, for one of my programs this trick does not work. It also did not work when I tried to open it with UAC Trust which is a program that pretty much does the whole task scheduler function for you. I guess it must be the program (EASEUS Todo Backup).
THanks again for your help
Thanks for the tutorial.
Is this method something that could be used to circumvent the security of
UAC by malicious software? I thought the point of UAC was to require action from the user (clicking allow) to gain administrator privilege.
Hello Lunes, and welcome to Seven Forums.
If malware was to infect the file that you used to run in the elevated task action settings, then yes it could. It would indeed be best to use UAC and to click on allow/yes before letting anything run elevated on the computer.
However, people wanted a way to do this, so I tried to provide a way to do so with as little reduction in security as possible so they wouldn't just turn UAC off completely.
Thanks Brink. I may have worded my question incorrectly. Rather than malware running my shortcut that was configured to bypass UAC prompt, would it be able to create a task in the scheduler, and create a shortcut for it? As in, could malware duplicate the entire process described in the tutorial for whatever application it wanted, and bypass UAC? This is more of a hypothetical question about me wondering how UAC works than questioning whether one should make a shortcut for certain programs.
The reason I found this thread/forum is because I installed Win7 on a machine, and am getting about 5 popups every time Windows starts asking if it's ok to run some apps (like Intel display manager, and synaptics touchpad utility). I'm not 100% sure it's UAC causing the prompts (there is no screen darken, but it does darken in other situations), but I do want to find a way to allow these apps to run without prompting.
It would be very highly unlikely for malware to do that.
It sounds like those are startup programs that are prompting you to allow them to run as administrator at startup. This tutorial is perfect to use to run them at startup as a task instead to allow them to run elevated at startup without prompting in administrator accounts, and remove them from the startup programs list afterwards.
I created the task in the Administrator account, creating it in Standard wasn't working. A Network account window kept occurring, and entering in the regular password for windows wasn't working either.
After creating the task and the short cut it won't run. Instead a command prompt window flashes on screen for a second and that's it.
Hello Jerome,
This will not work in a standard user account. It will only work in an administrator account.
There is no other way around this?
Quote