Powershell script not working through Task Scheduler

Question

Powershell script not working through Task Scheduler

Pankajbhakta95 106

Hi,
I am trying to disable few users on AD with the help of a simple PowerShell script as below.

Import-Module ActiveDirectory

Read content from DisableUser.csv file

$users=Import-CSV C:\ADUSERS\DisableUsers.csv

ForEach ($user in $users)
{
Disable-ADAccount -Identity $($user.name)

}

When I run the above script from my laptop through PowerShell console it works fine and disables the AD accounts but the script does not run
through the Task Scheduler. In the Scheduler I found that the Task starts and finishes but the script does not run.

I even added the command below to check it the script runs but no luck.

Set-Content -Path "C:\ADUSERS\TestTaskSch.txt" -Value "Hello World"

The Task Scheduler settings are given below.

Program/Script: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Argument : -File "C:\PSScripts\DisableADUsers.ps1" ( file location of the script)

Kindly help.

Cheers

Pankaj

Dey, Avijit 6 Reputation points

2022-11-21T08:38:20.077+00:00

Thanks a Lot @Pankajbhakta95 this worked for me too. I was stuck at same situation & googling everywhere for this.

Accepted answer

1 additional answer

Your answer

Dey, Avijit 6 Reputation points

2022-11-21T08:38:20.077+00:00

Thanks a Lot @Pankajbhakta95 this worked for me too. I was stuck at same situation & googling everywhere for this.

Answer 1

MotoX80 35,726

Look in the History tab for errors.

Change the task to run cmd.exe instead of powershell.exe. In the arguments field specify a bat file name, C:\PSScripts\DisableADUsers.bat

Create the .bat file to call the PS script but also redirect stdout and stderr to a log file where you can check for error messages.

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -File "C:\PSScripts\DisableADUsers.ps1"  1>C:\Windows\temp\DisableADUsers.log 2>&1

Pankajbhakta95 106 Reputation points

2021-04-19T06:29:16.443+00:00

Hi,

I have tested the solution provided by @MotoX80 by creating a batch file and calling the PowerShell script from it.

It is working fine.

Later I read few more post and added the following.

Argument -> - ExecutionPolicy Bypass
Start in -> C:\PSScripts\

The Task Scheduler config shown below.

Program/Script -> C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

Argument -> -ExecutionPolicy Bypass -File "C:\PSScripts\DisableADUsers.ps1"

Start In -> C:\PSScripts\

The earlier Scheduled Task is also working alright now.

Hence, I can use either method.

Thanks to both @Karlie Weng and @@MotoX80 for all your suggestion and help.

Cheers

Pankaj
Shinde, Vaibhav (WIPRO TECHNOLOGIES) 1 Reputation point

2021-12-02T12:21:40.82+00:00

I had same issue powershell script not working when scheduled I tried below code, error resolved. Thank you.
Program/Script -> C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

Argument -> -ExecutionPolicy Bypass -File "C:\PSScripts\DisableADUsers.ps1"
Baddham, Srunaj 0 Reputation points

2023-06-10T22:31:33.8833333+00:00

you need to put the actual file path and file in Program/Script section and ignore arguments for windows 10.
MotoX80 35,726 Reputation points

2023-06-11T02:03:43.2566667+00:00

and ignore arguments for windows 10.

There should be no problem if you configure the task to execute cmd.exe, and specify the name/path of the bat file in the arguments field.
Mohiuddin Chy 6 Reputation points

2023-07-19T08:55:35.8833333+00:00
Hi MotoX80,

i am also facing the same my powershell script is getting terminated by SYSTEM user in task scheduler, but if i right click and run its successfully executed.

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>
<Provider Name="Microsoft-Windows-TaskScheduler" Guid="{de7b24ea-73c8-4a09-985d-5bdadcfa9017}" />
<EventID>111</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>111</Task>
<Opcode>103</Opcode>
<Keywords>0x8000000000000001</Keywords>
<TimeCreated SystemTime="2023-07-19T03:39:29.1061191Z" />
<EventRecordID>6315719</EventRecordID>
<Correlation ActivityID="{2ba64b84-7b42-4c6a-a272-a496915eb36c}" />
<Execution ProcessID="1496" ThreadID="10248" />
<Channel>Microsoft-Windows-TaskScheduler/Operational</Channel>
<Computer>BD-DAC-01-SCC01.hwl-family.net</Computer>
<Security UserID="S-1-5-18" />
</System>

<EventData Name="TaskTerminationEvent">
<Data Name="TaskName">\Event Log</Data>
<Data Name="InstanceId">{2ba64b84-7b42-4c6a-a272-a496915eb36c}</Data>
</EventData>
</Event>
Mohiuddin Chy 6 Reputation points

2023-07-19T08:57:11.7133333+00:00

what is the command from cmd.exe to call powershell script, could you please share
MotoX80 35,726 Reputation points

2023-07-19T16:44:51.1033333+00:00

@Mohiuddin Chy follow the instructions that I posted to capture stdout and stderr.

You could also capture a transcript of the script.

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.host/start-transcript?view=powershell-7.3
UlisCalde 0 Reputation points

2023-08-17T19:08:40.27+00:00

This worked for me, thanks!
Sunny 0 Reputation points

2025-01-30T16:59:28.4033333+00:00

@MotoX80 I did try your solution giving Program/Script to cmd.exe and file path alone in arguments but still same issue. Task scheduler not running the bat file which is pointed to run PS script.
MotoX80 35,726 Reputation points

2025-01-30T17:48:04.53+00:00

@Sunny Is the E drive a local drive or a mapped network drive? I suspect that it is a network drive that may be mapped by a logon script. The task scheduler does not perform a full desktop logon, in which case you would need to reference the file using UNC notation. \\servername\sharename\mio\CMM\CMM......

It would be best to put the .bat file that the task scheduler runs on the C:\ and capture stdout and stderr to see what it does.

https://learn.microsoft.com/en-us/answers/questions/2141466/how-to-run-a-task-with-task-scheduler
Sunny 0 Reputation points

2025-01-30T21:32:53.4133333+00:00

@MotoX80 Thanks for the quick response.
E drive is a local drive for the server. However, I tried placing bat file in C: Drive and update path but no luck. In fact, the same task scheduler is working across multiple servers with same PowerShell script placed in E drive. This particular server is having the issue.

The only difference is the current server has office 2021 while the other servers where the task scheduler is working having office 2016. AL the other setting related to PS script and task scheduler are same.

Not sure if the office version is causing any issue since the ps script has to take a file, format it as per script and place in another folder. This may not be the root cause since the ps script is doing its job while running manually. This is the issue that it currently encounters. All setting were same which is working for other servers where this is copied from!
MotoX80 35,726 Reputation points

2025-01-30T22:56:23.89+00:00

The only difference is the current server has office 2021

Don't run Office apps (Word and Excel) through the task scheduler. They are GUI programs and expect to be interacting with a human being. They put out message boxes like "Click ok to continue". There is no way for you to see or interact with those.

https://learn.microsoft.com/en-us/office/client-developer/integration/considerations-unattended-automation-office-microsoft-365-for-unattended-rpa

The fact that your task indicates that it is still running is a great example. It likely displayed some message box, and is waiting for the user to respond. But there is no "user" and there no way for you to see what the message box says or do anything with it.
MotoX80 35,726 Reputation points

2025-01-31T12:34:54.55+00:00
You need to clean up any hung processes that the task scheduler has initiated. Use Process explorer and look for cmd.exe and powershell.exe. If your script is trying to run excel look for those too.

https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer

Procexp will indent names to show parent/child processes. Find the cmd.exe that is running your bat file (double click on cmd.exe and look at the command line value). and kill the process tree.

Use the link I posted and configure the task to capture stdout and stderr. In the bat file add statements like this.

@echo %date% %time% Task started. powershell.exe e:\mio\cmm\whatever @echo %date% %time% Task ended.

In the powershell script add similar write-host statements at key processing points to display what the script is doing.

If the task hangs again, look at the log file to see how far it got in processing.
sourabh agarwal 0 Reputation points

2025-02-20T10:36:59.94+00:00

I tried the solution but this is not working for me.
MotoX80 35,726 Reputation points

2025-02-20T12:37:34.4833333+00:00

I tried the solution but this is not working for me.

We can't help you based on "this is not working".

It would be best if you asked you own question. In it you should describe the details of how you defined the task. Ie; is it running as system, is it running if the user is logged on, etc. What program are you running? If you captured stdout/stderr, and a Powershell transcript, then please share the contents of those files. Explain exactly what isn't working.
Goran 0 Reputation points

2025-04-23T01:18:11.8533333+00:00

please what should be in my case be line

Argument -> -ExecutionPolicy Bypass -File "C:\PSScripts\DisableADUsers.ps1"
MotoX80 35,726 Reputation points

2025-04-23T10:37:47.61+00:00

@Goran Replace C:\PSScripts\DisableADUsers.ps1" with the full path to the script that you wish to execute.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
MotoX80 35,726 Reputation points

2025-04-26T17:22:27.98+00:00

The task scheduler does not capture the output of any program that it runs. If it is able to run a program, but if the program does not do what you want it to do, then you need to capture the output from that program to do further troubleshooting.

Some programs implement a logging capability. Powershell has the Start-Transcript and Stop-Transcript cmdlets.

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.host/start-transcript?view=powershell-5.1

Add that to your script and look in the log file to see what the script did.

If a transcript file does not get created, then refer to this post.

https://learn.microsoft.com/en-us/answers/questions/2259950/task-scheduler-isnt-opening-a-program

In that discussion refer to my answer dated Apr 25, 2025, 10:41 AM. There I describe how have the task scheduler run a .bat file and capture stdout and stderr. In the .bat file put the statement to call Powershell.exe. If there is any problem with Powershell it should be recorded in the log file.

Answer 2

Hello @Pankajbhakta95

First please check your configuration steps :How to: Run PowerShell Scripts from Task Scheduler
Change that to "Run whether user is logged on or not".
Leave the Do Not Store password option unchecked
Mark "Run with Highest Privileges" option
The account being use to execute task must have "Logon as batch job" rights under the local security policy of the server (or be member of local Admin group). You must specified the account you need to run scripts/bat files.

Please see:
Task Security Context

Powershell script does not run via Scheduled Tasks

Best Regards
Karlie

----------

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Pankajbhakta95 106 Reputation points

2021-04-15T20:10:51.47+00:00

@Karlie Weng

Thanks for your reply.

All the points you have mentioned in your reply are true but no luck.

Please check the screenshot of Task Scheduler.

Cheers

Pankaj
Karlie Weng 19,256 Reputation points Microsoft External Staff

2021-04-19T01:25:30.227+00:00

Hi,
Please check if below answer helps.

Share via

Powershell script not working through Task Scheduler

Read content from DisableUser.csv file

1 additional answer

Your answer