Windows 10: How to set up elevated process to run at user logon?

Let me explain my dilemma. We have this custom-made executable that interfaces with our hardware in the shop that needs to run as soon as someone logs in to this workstation. The way it was programmed, it needs to run elevated:






So I'm trying to automate the process of running it as soon as Windows user enters the password and logs in. (It causes problems when some employees forget to run this file upon login, which is easy to do.)There are two user accounts set up on this machine:Admin (Administrator) with a passwordDc (Standard user) with a passwordThe account in question that I need to automate the login for is Dc.So I went to Task Scheduler, ran it as Admin account and set up a task to run with Admin (highest) privileges:





do it at logon only, for the Dc account:





to run our elevated file:





with these conditions:





and these settings:





So I OKed the task and rebooted computer. I then logged in under Dc account, and nothing happened.I then started the Task Scheduler, and checked the task history. This is what it showed:







The question I have, is why does it say "because user Admin was not logged on" when I clearly indicated "Specific user: Dc" in the screenshot above?

:)

 

Adding new user to Windows 10 settings and start button not working

Hi,

thanks for the prompt reply,

I am running the programs you suggested but i have to admit that i have been through this process at least three times before i posted the original query.

the machine had a single user when running 8.1, after the upgrade to W10 the additional user was set up as a standard user but it had no rights to do anything. even when i elevated the user to Administrator it still couldn't seem to run anything. when i
opened control panel it could't select small icons, it ended up each time with large icons.

you suggested running the latest updates but i can't find anywhere how to access the update mechanism within windows 10.

the suggestions you recommended were run previously on the following setups.

1. Original user created the additional user using the User account icon, elevated to Administrator.

2. Additional account deleted as it didn't work correctly.

3. Additional account created via settings in the original account, elevated to Administrator.

4. Additional account deleted as it didn't work correctly.

5. Additional account created via CMD prompt and Net User "NAME" /ADD elevated to Administrator

6.Additional account deleted as it didn't work correctly.

as the original user account works correctly could this problem be a permissions issue with the new account when it is created?

 

How set a program to run at start up in Windows 10?

The Startup folder is still there in Windows 10. To access it, press WinKey + R, and type
shell:startup

This opens the Startup folder, located at:

C:\Users\{username}\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

in short:

%appdata%\Microsoft\Windows\Start Menu\Programs\Startup

 

Wild guess.....

In order for the user DC to run that .exe with Admin privileges, it may be trying to run the .exe "As Administrator", similar to right clicking a .exe and choosing Run As Administrator. Since Administrator is not logged on, there are no inherited privileges yet. I'm probably not saying all this quite right, but it may be a timing issue getting the privileges from an internal account (Admin) that has not fully initialized.

Like I said....wild guess.

 

First screenshot you have it set to admin and only run when user logged on ie admin tick box below it run wether logged in or not

 

Good catch. Maybe change the group in the first screenshot to Administrators

 

Guys, appreciate it.

This Task Scheduler... I tell you. How do people use it?

So if I change it on the first page to:







It boots up and gives me this error in the task history:

But if I uncheck to "Do not store password", it then asked my password for Admin, which I provide to OK the task:







It then boots up and gives me this error:

Well, one would assume that error 2147943726 is 41 times worse than error 2147943767. Corrent.

*Smile

 

@ahmd

Since you're trying to make a program/app run automatically for any specific user when they log on, maybe a different approach. Instead of going the job schedule entry way, why not set an autorun entry in the start menu folder for each user you want, or for all users. Create a shortcut to the .exe in the same folder as the .exe, giving it Run as Administrator priviledges. Then follow the steps in Option #2 in this tutorial here on Tenforums.

Add, Delete, Enable, or Disable Startup Items in Windows 10

Give the tutorial a look and see if this may work for you.

TC

 

A standard user can't run elevated task at log-on.

You'll have to either make the user part of Administrators group or give them a button to press after they log-on.

 

That's part of his issue. They don't always remember to push the button.

 

Indeed - but the solution is the same. Either re-write the code so it doesn't require elevation or make them Administrator. Or dock their pay if they don't press the button - that would learn 'em.

If a standard user could run anything at all through task scheduler it would defeat the point of having a standard user.

There is no legitimate workaround for this.

 

That's why I suggested the Start Folder using Shawn's tut. It wouldn't be the user running it then, it would be Explorer. It's not uncommon for other vendors to place startup entries there in order to run with privilege. I'm only offering an alternative way of trying it to see if it fits his needs and his organizations policies, while maintaining control. A standard user (un-priviledged) would not be able to alter the entry in the Start Folder. And no button to push.

These two lines from the tutorial tell me only an Admin could add/delete/modify these entries, and the standard user would have no input or choice....it would just run.


NOTE: You must be signed in as an administrator to be able to do this step.
A) In File Explorer, navigate to the step 4 below.

 

Well, I just tested it to be sure (you could have tested it yourself before positing it as a solution I guess but never mind).

It would have been cute but it doesn't actually work - it works on an administrator account and not on a standard account.

So, no - there is no getting around Windows security that way. As per MS security you can't run elevated process under a standard account at startup and this method is no different.

Even hacky things like this fileless-uac-bypass-using-eventvwr-exe-and-registry-hijacking require a Admin account to work.

 

Thanks for testing in your environment. Just to clarify.....I did NOT post this as a solution. Only a suggestion to try. The OP hasn't even had a chance to read these posts yet. It may give him an idea of how to proceed, thinking of alternatives, other approaches.

That's why I suggested the Start Folder using Shawn's tut.

I'm only offering an alternative way of trying it to see if it fits his needs


Please give the OP the opportunity to respond before declaring it unworkable. Your first comment was totally unnecessary.

 

Don't get the hump. It was a good enough idea. I tried it as it as I was interested to see if you'd found a workaround. It just so happens the OS blocks it (as it should).