Windows 10: I changed account from Admin to User, now scheduled task does not run

[Corrected description of the problem]

In the past i always used an Admin account without problems. Now i changed this User to a non-admin account and the scheduled task that was previously always running at log-in does not work anymore.

I have no clue why. The task history says disabled (why?). Even when i create a new task in another admin account, it does not run in my user account.

Please help!

:)

 

where user account for running the tasks are stored? How to delete and edit them?

John,

Task scheduler records both the computer name & user name in its Author
field, hence me-pc/me, but only the username me in the field for
When running the task, use the following user account. That is its normal behaviour and not a sign of any fault.

When intending to alter the user name for a task, always open Task scheduler as Admin or it will object to any change.

[Right-click on the shortcut to Task scheduler & select Run as Admin.]

You can delete user accounts in Settings, Accounts, family & other users. If the user account entries in the dropdown list have already been deleted then that is a caching issue & I suggest you post another question called something like
Task scheduler user account list includes user accounts that have already been deleted from the computer. In your question text, include the dropdown list picture to avoid any misunderstandings.

Denis

 

Windows 10 Task Scheduler not finding Admin

I've got 2 users on one machine. One "Standard" user and one "Administrator". They both log in fine. The Admin user has a password assigned, the Standard user does not. I am trying to run a program that requires elevated access on logon of the Standard
user. So while logged into the Standard user account, I open Task Scheduler and set all the specifics, including the "Run with highest privileges" checkbox. Then I click OK, select the Admin user to run as, and enter the password. Task Scheduler always says
that either the user is unknown (how it could be unknown, I don't know since I selected it from the dropdown) or the password is incorrect, which it definitely is not. Can anyone else confirm that this does or does not work on their machine? Is there a workaround?
Maybe a different 3rd party task scheduler that is verified to work in this case?

 

What are the tasks it would seem they require admin rights to run could they be run at start not as schedule tasks

 

The task is simple. Run silently a driver install EXE at log-on. I'm solving a problem where the driver is not seen after restart, so i have to always run the installer every time i reboot. But it has to run delayed, for example 30sec after logon.

 

Pls read the updated description. Thanks!

 

I think you're going to have to activate the built-in admin account in order to elevate your standard acct back to admin-level; I have Windows 7, so I might be incorrect. There might be a DOS/command-line, however, I do not know what it is.

 

I apologize, i've been on the wrong track. The error message was because i tried to run the task even without log-on. I've corrected the original post - i hope it's clearer now and that someone has an idea what could be wrong.

 

History is turned off by default. To turn it on open Task Scheduler, go to the "Action" tab at the top and click on "Enable All Tasks History".

Then you can reboot and see why it is failing.

You can't run tasks requiring Administrative rights under a standard account so that may be it.

 

I assume what your doing is running a unsigned driver which the system rejects after reboot you can force it to accept the driver How to Disable Driver Signature Verification on 64-Bit Windows 8 or 10 (So That You Can Install Unsigned Drivers)

Its not a good idea to run these drivers that are untested

 

Now we're talking. I didn't know that. Thanks for this vital information. The task indeed needs admin rights, i tested it manually.

Hmm, it's a Wacom driver 64bit for Windows 7. Do you think it is unsigned? Anyway, i'm not gonna compromise my security with disabling the driver signatures. Not worth it. I guess for the time being i'll start the EXE manually every time i need the digitizer - not ideal, but still better than paying for new hardware.

Thanks for the help, guys - at least we tried. *Smile