Windows 10 PowerShell script doesn't run with Task Scheduler trigger set for logon or logoff

Question

I'm trying to have a simple PowerShell script start at Windows session login or logoff...

the script runs ok with manual launch the script runs ok when launched by scheduled task at a specific time (and I'm logged in as admin) But it doesn't run with a launch at logon or logoff.

In the task scheduler I have the following :

my account (with admin rights) is designated to run the script

the button "run if not connected" is on

the box "execute with highest priv" is checked

trigger : "when connecting to a win session" / any user / local connexion / Advanced parameters "Activate" box is checked

action : powershell.exe with arguments : -noprofile -executionpolicy Bypass -File .\wlem.ps1 / start in c:\public

no condition box is checked

Thanks for the help :-)

Answer 1

This is a easy fix:

navigate to here: C:\Users\ YOURUSERNAMEHERE \AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

Drop a shortcut to your script (notice it has to be a shortcut)

You can make a shortcut of your script by sending it desktop, and use that shortcut on desktop. place that shortcut in the startup folder.

That's it! Simple startup trick i learned a while back.

Answer 2

I can only get this to work with the following changes:

• Run the task as SYSTEM.
• Specify the full path to the script file with the -File switch, even though you already set the starting directory.

If you're using a laptop, make sure the task isn't set to only start on AC power.

You can specify -WindowStyle Hidden as well if you like, though it isn't strictly necessary. Also, you only need to check Activate and set a date if you don't want the task to start firing until that date/time.

As Bob mentioned in the comments, you might consider using the logon trigger and the event trigger for logoffs instead of these connection and disconnection triggers. The ones you're currently using will fire every time user switching happens, not just at logon and logoff. If you're willing to abandon Task Scheduler, you could switch to Group Policy logon/logoff scripts, which are fairly easy to manage.