通过任务计划程序调用PowerShell执行LockWorkStation失效问题求助

Let's break down why your LockWorkStation command isn't working and how to fix it—this is a super common gotcha with task scheduler and interactive desktop commands.

First, let's recap your setup to make sure I'm aligned:

• You trigger an Alexa command (like "Lock my PC"), which tells IFTTT to drop a lock.txt file into a specific Dropbox folder
• A PowerShell script runs on a 5-second loop via Task Scheduler, checks for these files, and runs the corresponding system command
• Shutdown/Restart/Sleep work fine, but LockWorkStation fails completely

The Root Cause #

The issue almost always boils down to Task Scheduler permissions and session context. When you run a script via Task Scheduler with the "Run whether user is logged on or not" option enabled, the script runs in a non-interactive background session. LockWorkStation requires access to your active, logged-in desktop session—something background sessions don't have.

Step 1: Fix Task Scheduler Settings #

First, adjust your task to run in the correct context:

• Open Task Scheduler and locate your PowerShell task
• Go to the General tab
  • Make sure the task is configured to run under your current user account (not a system account)
  • Check the box for "Run only when user is logged on"
  • Uncheck "Run whether user is logged on or not" if it's enabled
• Save the changes and re-run the task

Step 2: Update the PowerShell Script for Reliable Locking #

While the built-in LockWorkStation might work in a regular PowerShell window, calling the Windows API directly is more reliable in automated scripts. Replace your lock command logic with this:

# Detect and handle lock.txt
if (Test-Path "$SearchDirectory\lock.txt") {
    # Delete the file immediately to prevent repeated triggers
    Remove-Item -Path "$SearchDirectory\lock.txt" -Force -ErrorAction SilentlyContinue
    
    # Call the Windows LockWorkStation API directly
    Add-Type @"
    using System;
    using System.Runtime.InteropServices;
    public class User32 {
        [DllImport("user32.dll")]
        public static extern bool LockWorkStation();
    }
    "@
    [User32]::LockWorkStation()
}

Bonus: Clean Up Your Script #

You can simplify the initial file cleanup with a loop to avoid repeating Remove-Item commands, and standardize all system commands with direct API calls for consistency:

$SearchDirectory = "C:\Users\Username\Dropbox\IFTTT"
$SleepTime = 5

# Clean up any leftover command files on startup
@("shutdown.txt", "restart.txt", "sleep.txt", "lock.txt") | ForEach-Object {
    Remove-Item -Path "$SearchDirectory\$_" -Force -ErrorAction SilentlyContinue
}

# Main loop
while ($true) {
    # Handle lock command
    if (Test-Path "$SearchDirectory\lock.txt") {
        Remove-Item -Path "$SearchDirectory\lock.txt" -Force -ErrorAction SilentlyContinue
        Add-Type @"
        using System;
        using System.Runtime.InteropServices;
        public class User32 {
            [DllImport("user32.dll")]
            public static extern bool LockWorkStation();
        }
        "@
        [User32]::LockWorkStation()
    }

    # Handle shutdown command
    if (Test-Path "$SearchDirectory\shutdown.txt") {
        Remove-Item -Path "$SearchDirectory\shutdown.txt" -Force -ErrorAction SilentlyContinue
        Stop-Computer -Force
    }

    # Handle restart command
    if (Test-Path "$SearchDirectory\restart.txt") {
        Remove-Item -Path "$SearchDirectory\restart.txt" -Force -ErrorAction SilentlyContinue
        Restart-Computer -Force
    }

    # Handle sleep command
    if (Test-Path "$SearchDirectory\sleep.txt") {
        Remove-Item -Path "$SearchDirectory\sleep.txt" -Force -ErrorAction SilentlyContinue
        Add-Type @"
        using System;
        using System.Runtime.InteropServices;
        public class PowrProf {
            [DllImport("powrprof.dll", SetLastError = true)]
            public static extern bool SetSuspendState(bool hibernate, bool forceCritical, bool disableWakeEvent);
        }
        "@
        [PowrProf]::SetSuspendState($false, $true, $false)
    }

    Start-Sleep -Seconds $SleepTime
}

Why This Works #

By setting the task to run only when you're logged on, you ensure the script runs in your active desktop session—giving it the necessary permissions to trigger the workstation lock. Calling the Windows API directly avoids any quirks with PowerShell's default command execution in automated contexts.

内容的提问来源于stack exchange，提问作者Explisam