PowerShell脚本无法检测Chrome配置文件运行状态的修复咨询

问题概述 #

编写的PowerShell脚本旨在检测指定Chrome配置文件是否运行，未运行则启动，但存在以下问题：

• 无法正确识别已运行的配置文件，导致重复启动实例
• 调整后仅能识别Default配置文件，其他带空格的配置文件（如Profile 10）仍会重复启动

已尝试操作 #

• 确认$profiles数组中的配置文件名与Chrome用户数据目录实际文件夹名一致
• 添加详细日志查看Chrome进程命令行
• 添加启动延迟确保配置文件正常启动
• 验证脚本以管理员权限运行

当前PowerShell版本 #

PSVersion                      5.1.22621.4391
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.4391
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

原脚本 #

# Function to request elevated permissions (run as admin)
function Test-Admin {
    $isAdmin = ([System.Security.Principal.WindowsIdentity]::GetCurrent().Groups -match "S-1-5-32-544")
    if (-not $isAdmin) {
        Write-Host "This script requires administrator privileges. Restarting with elevated rights."
        # Start a new PowerShell process with admin rights
        Start-Process powershell -ArgumentList "-NoProfile -ExecutionPolicy Bypass -File `"$PSCommandPath`"" -Verb RunAs
        exit
    }
}

# Request admin rights at the start of the script
Test-Admin

# Full path to Chrome executable
$chromePath = "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"

# List of Chrome profiles to open
$profiles = @("Default", "Profile 10", "Profile 7", "Profile 8", "Profile 9", "Profile 3", "Profile 2", "Profile 6", "Profile 5", "Profile 17", "Profile 20", "Profile 18", "Profile 4", "Profile 1", "Profile 21", "Profile 19", "Profile 15")

# Get all chrome processes (filtering out renderer and crashpad processes)
$chromeProcesses = Get-WmiObject Win32_Process | Where-Object { $_.Name -eq "chrome.exe" -and $_.CommandLine -notlike "*--type=renderer*" -and $_.CommandLine -notlike "*--type=crashpad-handler*" }

# Loop through each profile
foreach ($profile in $profiles) {
    Write-Host "Checking if Chrome profile $profile is running..."

    $profileRunning = $false

    # Check if any process has the profile argument in its command line
    foreach ($process in $chromeProcesses) {
        if ($process.CommandLine -like "*--profile-directory=$profile*" -or $process.CommandLine -like "*--profile-directory=`"$profile`"") {
            $profileRunning = $true
            Write-Host "Profile $profile is already running with process ID $($process.ProcessId)."
            break
        }
    }

    # If the profile isn't running, start Chrome with that profile
    if (-not $profileRunning) {
        Write-Host "Starting Chrome with profile $profile at $(Get-Date)"
        Start-Process -FilePath $chromePath -ArgumentList "--profile-directory=`"$profile`"" -NoNewWindow
        Start-Sleep -Seconds 1 # Adding a brief delay for performance
    }
}

Write-Host "All requested profiles checked. Only non-running profiles were started."

问题分析 #

原脚本的核心缺陷：

1. 命令行匹配逻辑不完整：对于带空格的配置名，Chrome命令行用双引号包裹，但原判断仅匹配了双引号的开头，未覆盖完整的"$profile"格式
2. Get-WmiObject获取的命令行输出不稳定，在部分场景下会出现格式偏差
3. 权限检查逻辑依赖SID匹配，不如直接使用Windows身份角色判断直观可靠

修改后的脚本 #

# 检查管理员权限，无权限则重新启动脚本
function Test-Admin {
    $currentIdentity = [System.Security.Principal.WindowsIdentity]::GetCurrent()
    $principal = New-Object System.Security.Principal.WindowsPrincipal($currentIdentity)
    $isAdmin = $principal.IsInRole([System.Security.Principal.WindowsBuiltInRole]::Administrator)
    
    if (-not $isAdmin) {
        Write-Host "脚本需要管理员权限，正在重新启动..."
        Start-Process powershell.exe -ArgumentList "-NoProfile -ExecutionPolicy Bypass -File `"$PSCommandPath`"" -Verb RunAs
        exit
    }
}

Test-Admin

# Chrome可执行文件路径
$chromePath = "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"

# 需要检查的配置文件列表
$profiles = @("Default", "Profile 10", "Profile 7", "Profile 8", "Profile 9", "Profile 3", "Profile 2", "Profile 6", "Profile 5", "Profile 17", "Profile 20", "Profile 18", "Profile 4", "Profile 1", "Profile 21", "Profile 19", "Profile 15")

# 获取Chrome主进程（排除渲染器和崩溃处理进程）
$chromeProcesses = Get-CimInstance Win32_Process | Where-Object {
    $_.Name -eq "chrome.exe" -and
    $_.CommandLine -notlike "*--type=renderer*" -and
    $_.CommandLine -notlike "*--type=crashpad-handler*"
}

# 遍历每个配置文件
foreach ($profile in $profiles) {
    Write-Host "正在检查配置文件: $profile"
    $profileRunning = $false

    # 生成两种匹配模式：带引号和不带引号
    $patternNoQuotes = "*--profile-directory=$profile*"
    $patternWithQuotes = "*--profile-directory=`"$profile`"*"

    foreach ($process in $chromeProcesses) {
        # 检查命令行是否匹配任一模式
        if ($process.CommandLine -like $patternNoQuotes -or $process.CommandLine -like $patternWithQuotes) {
            $profileRunning = $true
            Write-Host "配置文件 $profile 已运行，进程ID: $($process.ProcessId)"
            break
        }
    }

    # 未运行则启动该配置文件
    if (-not $profileRunning) {
        Write-Host "[$(Get-Date)] 启动配置文件: $profile"
        Start-Process -FilePath $chromePath -ArgumentList "--profile-directory=`"$profile`"" -NoNewWindow
        Start-Sleep -Seconds 1
    }
}

Write-Host "所有配置文件检查完成，仅启动未运行的实例。"

修改说明 #

• 替换Get-WmiObject为Get-CimInstance：后者是更现代的WMI访问方式，命令行输出更稳定
• 完善匹配逻辑：同时检查带双引号和不带双引号的命令行参数，确保带空格的配置名能被正确识别
• 优化管理员权限检查：使用WindowsPrincipal角色判断，逻辑更直观可靠
• 调整日志输出格式，提升可读性

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