Windows 10: Scheduled task to decrease UAC level?

I have the local admin rights on my work laptop but at the same time GPO enforces default UAC settings on the power up. This is annoying as it prevents some apps I use from proper running (e.g. PhraseExpress or DirectFolders). I have no idea why those apps need a prior UAC approval, but it's not the case here.

Is there a way to create a scheduled task that would decrease the level of UAC to "never notify" / lowest level? Or is there any other way to do so and make sure GPO will not kill it at next boot?

:)

 

Is it possible to disable UAC for a specific application for all administrator users on that machine?

Hi everybody,

is it possible to disable UAC for a specific application for all administrator users on that machine?

I tried to create a scheduled task with high privileges but it works only when its author starts it. If another administrator user logs in, he doesn't succeed to run the scheduled task.

Thank you all

 

Error in Task Scheduler - Requested Operation Requires Elevation (0x800702E4)

From Windows 10 version 1607 and Windows Server 2016, we get an error when the scheduled task are executed.

We use the Task Scheduler API 1.0 to create scheduled tasks, that will run whether user is logged on or not and with highest privileges.

But when we try to execute this task we get the error "The requested operation requires elevation. (0x800702E4)".

We get this error only if the account who execute the task has a session opened.

If we change the execution account to other that has not session opened, it works. Or if we use the default administrator account who doesn't pass through the UAC (User Account Control) to elevate privileges, it works also.

I have not found the report of the problem in the Windows 10 Anniversary Update (Version 1607).

 

https://www.tenforums.com/tutorials/5...dows-10-a.html

 

Hi, @mikolajek:

In addition to the excellent advice already offered...

...if this is your WORK laptop, you might want to consult with your IT/security folks at work before making changes to the system that affect or bypass UAC, Group Policies or other security settings.
In many Enterprise environments, these sorts of configurations are controlled by the company's IT folks for a reason.
They may not wish (or permit) end users to make such changes.

<just a thought>

MM