Windows 10: Keep Console Open after running power shell script through task scheduler

I am running a powershell script using task scheduler:

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

Add arguments optional: C:\Users\Administrator\Desktop\JO.ps1



This works fine. However I want the powershell console to remain open. After looking at this article keep-powershell-console-window, I tried:


1. Adding an argument within task scheduler

Add arguments optional: -NoExit "C:\Users\Administrator\Desktop\JO.ps1"

The script runs fine but the console window does not remaining open I can't even see it momentarily appear.


2. Changing the script file itself

I added the following line to the end of my script: Read-Host -Prompt "Press Enter to exit"

When the script is run manually the console window remains open, but if the script is run through the task scheduler the console window does not remain open.



Please help.

Haresh


:)

 

Scheduled tasks run with elevated privileges can't access stored Windows credentials

It seems that after Creators update scheduled tasks run with elevated privileges ('run with highest privileges' option) can't access stored Windows credentials. Is that a bug or an intentional change and is there a recommended workaround?

Here's one way to reproduce the behaviour:

• Start Credential Manger and add some Windows share credentials.
• In a console window type 'cmdkey /list', which should list the added credentials
• Create a task in a task manager:
  • Trigger: on user logon
  • Action: run cmd.exe
  • Tick the 'run with highest privileges' option
• Reboot the machine and log in
• In the console window (let's call it 'console 1') opened from the scheduled task type 'cmdkey /list'. This most likely won't display the credentials added in step 1 and properly listed in step 2. ->
  This looks like a bug
• Now, without closing 'console 1' open another console window as an administrator (let's call it 'console 2') and type 'cmdkey /list'. This will properly list credentials added in step 1.
• Switch to 'console 1' and type 'cmdkey /list' again. This time the credentials are listed properly, unlike in step 5. It looks like an access to Windows credentials was somehow 'unlocked' by step 6.

 

Task Scheduler doesn't run script

Hi,

Thank you for writing to Microsoft Community Forums.

Are you able to run the script manually? If yes, does it do what it is intended to?

Disable the UAC temporarily.

Make sure that the Task scheduler
service is running.

Press ‘Win+R’.

Type Services.msc.

Locate the service Task scheduler
and make sure that it is in running state.

Go to the Conditions
tab in task scheduler and make sure that no such condition is set which could block the task from running.

Enable All Tasks History in Task scheduler and run the scheduled task.

Refresh the task scheduler and check if you find any error message/code for any step in the task run.

Also try with disabling Run whether the user is logged on or not
option and see if the script runs.

Hope it helps.

Peer Samie

Microsoft Community-Moderator

 

Task Scheduler doesn't run script

Hey Microsoft Community,

I'm trying to create a task in Task Scheduler that runs a specific script. The issue is that when the task runs (whether I do it manually or if it's scheduled), the script doesn't actually get executed. I know that the script works, and I have tried using
both .EXE and .BAT scripts. I have set the task to run whether I'm logged in or not, using Highest Privileges, from my Administrator account; I have Full Access to the script file and the directory it's in; I have tried putting the directory it's in into the
"Start in" field; I have tried opening Task Scheduler as an Administrator. Every time the task runs successfully, but the thing my script is supposed to do isn't done, from which I am inferring that the script doesn't get executed. The script isn't using any
network connections. It's also not being blocked by my antivirus, I checked by temporarily turning it off.

System info:

Windows 10 x64 version 1803

Thanks in advance!