Hey there! Let's break down your issues step by step—first, why your Bash script is throwing errors in PowerShell, then how to get it running on startup, either using WSL or converting it to PowerShell.

一、Why your Bash script fails in PowerShell #

First things first: PowerShell and Bash are completely different shell environments with totally separate syntax rules. That's why you're seeing errors like "missing left parenthesis for if statement" or "missing type name after ["—those are Bash-specific constructs that PowerShell doesn't understand.

For example:

• Bash uses if [ -f "$file" ] to check if a file exists; PowerShell uses if (Test-Path $file -PathType Leaf)
• Bash's case statement is replaced by PowerShell's switch
• Even basic commands like mkdir -p become New-Item -ItemType Directory -Force in PowerShell

So you have two options: run the Bash script via WSL (Windows Subsystem for Linux), or rewrite it in PowerShell syntax.

二、Running your Bash script on Windows 10 startup #

Option 1: Use WSL (best for keeping your existing Bash script) #

Since you mentioned finding Ubuntu-related solutions, WSL is exactly what you need—it lets you run a full Linux environment directly on Windows. Here's how to set it up:

1. Install WSL if you haven't already
   Open PowerShell as Administrator and run:

   wsl --install
   

   Restart your PC, then follow the prompts to install a Linux distro (Ubuntu is the default, but you can pick others too).

2. Test your script in WSL
   Launch your Linux terminal (e.g., Ubuntu), then run your script using its WSL path. Windows drives are mapped under /mnt/ in WSL, so if your script is at C:\Users\YourName\Desktop\cleanup.sh, the WSL path is /mnt/c/Users/YourName/Desktop/cleanup.sh.
   Run:

   bash /mnt/c/Users/YourName/Desktop/cleanup.sh
   

   Make sure it works as expected before moving on.

3. Set up auto-run on startup
   Use Windows Task Scheduler to trigger the script when you log in:

   • Search for Task Scheduler in the Start Menu and open it
   • Click Create Basic Task (in the right-hand pane)
   • Name it something like "Desktop Cleanup Bash Script" and click Next
   • Choose When I log on as the trigger, then Next
   • Select Start a program as the action, then Next
   • For Program/script, enter wsl
   • For Add arguments, enter bash /mnt/c/path/to/your/cleanup.sh (replace with your actual WSL path)
   • Optional: Check "Run whether user is logged on or not" if you want it to run even when you're not logged in
   • Click Finish, then restart your PC to test it out.

Option 2: Convert your Bash script to PowerShell (no WSL needed) #

If you'd rather avoid WSL, rewriting your script in PowerShell lets you run it natively on Windows. Let's use a common desktop cleanup script as an example—here's how a typical Bash version translates to PowerShell:

Original Bash script example:

#!/bin/bash
DESKTOP="$HOME/Desktop"
mkdir -p "$DESKTOP/Documents" "$DESKTOP/Images" "$DESKTOP/Archives"

for file in "$DESKTOP"/*; do
  if [ -f "$file" ]; then
    case "${file##*.}" in
      doc|docx|pdf|txt) mv "$file" "$DESKTOP/Documents/" ;;
      jpg|png|gif) mv "$file" "$DESKTOP/Images/" ;;
      zip|rar|tar) mv "$file" "$DESKTOP/Archives/" ;;
    esac
  fi
done

Equivalent PowerShell script:

# Get the user's Desktop path
$desktop = [Environment]::GetFolderPath("Desktop")

# Create target folders if they don't exist
$targetFolders = @("Documents", "Images", "Archives")
foreach ($folder in $targetFolders) {
    $folderPath = Join-Path -Path $desktop -ChildPath $folder
    if (-not (Test-Path -Path $folderPath)) {
        New-Item -Path $folderPath -ItemType Directory | Out-Null
    }
}

# Sort files into their respective folders
Get-ChildItem -Path $desktop -File | ForEach-Object {
    $extension = $_.Extension.ToLower().TrimStart('.')
    switch ($extension) {
        {'doc','docx','pdf','txt' -contains $_} {
            Move-Item -Path $_.FullName -Destination (Join-Path $desktop "Documents") -Force
        }
        {'jpg','png','gif' -contains $_} {
            Move-Item -Path $_.FullName -Destination (Join-Path $desktop "Images") -Force
        }
        {'zip','rar','tar' -contains $_} {
            Move-Item -Path $_.FullName -Destination (Join-Path $desktop "Archives") -Force
        }
    }
}

Set up auto-run for the PowerShell script:

1. Save the PowerShell code above as DesktopCleanup.ps1 (e.g., in C:\Scripts\)
2. Open Task Scheduler, create a basic task with the "When I log on" trigger
3. For the action, select "Start a program"
   • Program/script: powershell.exe
   • Add arguments: -ExecutionPolicy Bypass -File "C:\Scripts\DesktopCleanup.ps1"
     • The -ExecutionPolicy Bypass flag gets around PowerShell's default script execution restrictions. If you've already set your execution policy to allow local scripts (run Set-ExecutionPolicy RemoteSigned as Admin), you can skip this flag.
4. Finish the setup and restart to test.

三、Quick troubleshooting tips #

• WSL script not running on startup? Double-check the WSL path (remember /mnt/c is your C drive), and make sure the Task Scheduler task has the right permissions (try checking "Run with highest privileges" if needed).
• PowerShell script throwing permission errors? Open PowerShell as Admin and run Set-ExecutionPolicy RemoteSigned—this lets you run local scripts without requiring a digital signature.

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