普通用户与管理员用户PowerShell脚本执行差异问题咨询

Hey there! Let's figure out why your admin PowerShell can't recognize the menu command while your regular user account can. The issue almost certainly boils down to differences in environment configuration between the two user contexts—here's how to fix it:

When you run menu as a regular user, PowerShell knows where to find Menu.ps1 because your scripts folder is added to your user-specific PATH environment variable. For the admin account, this path is probably missing.

• Open an elevated PowerShell (admin mode)
• Run this command to list your current PATH entries:

  $env:PATH -split ';'
  

• Look for the full path to your scripts folder (the one containing Menu.ps1). If it's not listed, we'll add it permanently.

You can update the admin user's environment variables either via PowerShell or the Windows GUI:

Option A: PowerShell (fastest method) #

Run this in elevated PowerShell, replacing C:\Full\Path\To\Your\Scripts with your actual scripts folder path:

# Get the current user's PATH from the registry
$currentUserPath = [Environment]::GetEnvironmentVariable('PATH', 'User')

# Append the scripts folder if it's not already present
if (-not $currentUserPath.Contains('C:\Full\Path\To\Your\Scripts')) {
    $updatedPath = "$currentUserPath;C:\Full\Path\To\Your\Scripts"
    [Environment]::SetEnvironmentVariable('PATH', $updatedPath, 'User')
    # Refresh the current session's PATH to apply changes immediately
    $env:PATH = $updatedPath
}

Option B: Windows GUI #

• Press Win + R, type sysdm.cpl and hit Enter to open System Properties
• Go to the Advanced tab, then click Environment Variables
• Under User variables for [YourAdminUsername], locate the Path variable and click Edit
• Click New and paste the full path to your scripts folder
• Click OK on all windows to save changes, then restart your elevated PowerShell

If you set up an alias menu pointing to Menu.ps1 in your regular user's PowerShell profile, you need to copy that setup to the admin user's profile:

• In elevated PowerShell, open the admin profile script with:

  notepad $PROFILE
  

• Add the same alias line you have in your regular user's profile (it should look similar to this):

  Set-Alias -Name menu -Value "C:\Full\Path\To\Your\Scripts\Menu.ps1"
  

• Save the file, then restart your elevated PowerShell for the alias to take effect

While you can run the script when in the PSDrive, it's worth confirming the admin user's execution policy allows running local scripts:

Get-ExecutionPolicy

If the result is Restricted, change it to RemoteSigned (a safe default that allows local scripts):

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

(You'll need to confirm the change when prompted)

After completing either step 2 or 3 (or both, if you use both PATH and aliases), you should be able to type menu in any folder from elevated PowerShell and have it run Menu.ps1 just like your regular user account does.

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