Start-Process (Microsoft.PowerShell.Management) - PowerShell (2024)

  • Reference
Module:
Microsoft.PowerShell.Management

Starts one or more processes on the local computer.

Syntax

Start-Process [-FilePath] <string> [[-ArgumentList] <string[]>] [-Credential <pscredential>] [-WorkingDirectory <string>] [-LoadUserProfile] [-NoNewWindow] [-PassThru] [-RedirectStandardError <string>] [-RedirectStandardInput <string>] [-RedirectStandardOutput <string>] [-WindowStyle <ProcessWindowStyle>] [-Wait] [-UseNewEnvironment] [-Environment <hashtable>] [-WhatIf] [-Confirm] [<CommonParameters>]
Start-Process [-FilePath] <string> [[-ArgumentList] <string[]>] [-WorkingDirectory <string>] [-PassThru] [-Verb <string>] [-WindowStyle <ProcessWindowStyle>] [-Wait] [-Environment <hashtable>] [-WhatIf] [-Confirm] [<CommonParameters>]

Description

The Start-Process cmdlet starts one or more processes on the local computer. By default,Start-Process creates a new process that inherits all the environment variables that are definedin the current process.

To specify the program that runs in the process, enter an executable file or script file, or a filethat can be opened using a program on the computer. If you specify a non-executable file,Start-Process starts the program that's associated with the file, similar to the Invoke-Itemcmdlet.

You can use the parameters of Start-Process to specify options, such as loading a user profile,starting the process in a new window, or using alternate credentials.

Examples

Example 1: Start a process that uses default values

This example starts a process that uses the Sort.exe file in the current folder. The command usesall the default values, including the default window style, working folder, and credentials.

Start-Process -FilePath "sort.exe"

Example 2: Print a text file

This example starts a process that prints the C:\PS-Test\MyFile.txt file.

Start-Process -FilePath "myfile.txt" -WorkingDirectory "C:\PS-Test" -Verb Print

Example 3: Start a process to sort items to a new file

This example starts a process that sorts items in the TestSort.txt file and returns the sorteditems in the Sorted.txt files. Any errors are written to the SortError.txt file. TheUseNewEnvironment parameter specifies that the process runs with its own environment variables.

$processOptions = @{ FilePath = "sort.exe" RedirectStandardInput = "TestSort.txt" RedirectStandardOutput = "Sorted.txt" RedirectStandardError = "SortError.txt" UseNewEnvironment = $true}Start-Process @processOptions

This example uses splatting to pass parameters to the cmdlet. For more information, seeabout_Splatting.

Example 4: Start a process in a maximized window

This example starts the Notepad.exe process. It maximizes the window and retains the window untilthe process completes.

Start-Process -FilePath "notepad" -Wait -WindowStyle Maximized

Example 5: Start PowerShell as an administrator

This example starts PowerShell using the Run as administrator option.

Start-Process -FilePath "powershell" -Verb RunAs

Example 6: Using different verbs to start a process

This example shows how to find the verbs that can be used when starting a process. The availableverbs are determined by the filename extension of the file that runs in the process.

$startExe = New-Object System.Diagnostics.ProcessStartInfo -Args powershell.exe$startExe.verbsopenrunasrunasuser

The example uses New-Object to create a System.Diagnostics.ProcessStartInfo object forpowershell.exe, the file that runs in the PowerShell process. The Verbs property of theProcessStartInfo object shows that you can use the Open and RunAs verbs withpowershell.exe, or with any process that runs a .exe file.

Example 7: Specifying arguments to the process

Both commands start the Windows command interpreter, issuing a dir command on the Program Filesfolder. Because this foldername contains a space, the value needs surrounded with escaped quotes.Note that the first command specifies a string as ArgumentList. The second command is a stringarray.

Start-Process -FilePath "$env:comspec" -ArgumentList "/c dir `"%SystemDrive%\Program Files`""Start-Process -FilePath "$env:comspec" -ArgumentList "/c","dir","`"%SystemDrive%\Program Files`""

Example 8: Create a detached process on Linux

On Windows, Start-Process creates an independent process that remains running independently of thelaunching shell. On non-Windows platforms, the newly started process is attached to the shell thatlaunched. If the launching shell is closed, the child process is terminated.

To avoid terminating the child process on Unix-like platforms, you can combine Start-Process withnohup. The following example launches a background instance of PowerShell on Linux that staysalive even after you close the launching session. The nohup command collects output in filenohup.out in the current directory.

# Runs for 2 minutes and appends output to ./nohup.outStart-Process nohup 'pwsh -noprofile -c "1..120 | % { Write-Host . -NoNewline; sleep 1 }"'

In this example, Start-Process is running the Linux nohup command, which launches pwsh as adetached process. For more information, see the nohup article onWikipedia.

Example 9: Overriding an environment variable for a process

By default, when you use Start-Process, the new process is created with the same environmentvariables as the current session. You can use the Environment parameter to override the valuesof those variables.

In this example, the environment variable FOO is added to the session with foo as the value.

The example runs Start-Process three times, returning the value of FOO each time. The firstcommand doesn't override the environment variable. In the second command, FOO is set to bar. Inthe third command, FOO is set to $null, which removes it.

$env:FOO = 'foo'Start-Process pwsh -NoNewWindow -ArgumentList '-c', '$env:FOO'Start-Process pwsh -NoNewWindow -ArgumentList '-c', '$env:FOO' -Environment @{ FOO = 'bar'}Start-Process pwsh -NoNewWindow -ArgumentList '-c', '$env:FOO' -Environment @{ FOO = $null}foobar

Parameters

-ArgumentList

Specifies parameters or parameter values to use when this cmdlet starts the process. Arguments canbe accepted as a single string with the arguments separated by spaces, or as an array of stringsseparated by commas. The cmdlet joins the array into a single string with each element of the arrayseparated by a single space.

The outer quotes of the PowerShell strings aren't included when the ArgumentList values arepassed to the new process. If parameters or parameter values contain a space or quotes, they need tobe surrounded with escaped double quotes. For more information, seeabout_Quoting_Rules.

For the best results, use a single ArgumentList value containing all the arguments and anyneeded quote characters.

Type:String[]
Aliases:Args
Position:1
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-Confirm

Prompts you for confirmation before running the cmdlet.

Type:SwitchParameter
Aliases:cf
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-Credential

Specifies a user account that has permission to perform this action. By default, the cmdlet uses thecredentials of the current user.

Type a user name, such as User01 or Domain01\User01, or enter a PSCredential objectgenerated by the Get-Credential cmdlet. If you type a user name, you're prompted to enter thepassword.

Credentials are stored in a PSCredentialobject and the password is stored as a SecureString.

Note

For more information about SecureString data protection, seeHow secure is SecureString?.

Type:PSCredential
Aliases:RunAs
Position:Named
Default value:Current user
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-Environment

Specifies one or more environment variables to override for the process as a hash table. Specifythe name of an environment variable as a key in the hash table and the desired value. To unset anenvironment variable, specify its value as $null.

The specified variables are replaced in the process. When you specify the PATH environmentvariable it's replaced with the value of $PSHOME followed by the specified value from thisparameter. On Windows, the command appends the values for PATH in the Machine and User scopesafter the new value.

This parameter was added in PowerShell 7.4.

Type:Hashtable
Position:Named
Default value:None
Required:False
Accept pipeline input:True
Accept wildcard characters:False

-FilePath

Specifies the optional path and filename of the program that runs in the process. Enter the name ofan executable file or of a document, such as a .txt or .doc file, that's associated with aprogram on the computer. This parameter is required.

If you specify only a filename that does not correspond to a system command, use theWorkingDirectory parameter to specify the path.

Type:String
Aliases:PSPath, Path
Position:0
Default value:None
Required:True
Accept pipeline input:False
Accept wildcard characters:False

-LoadUserProfile

Indicates that this cmdlet loads the Windows user profile stored in the HKEY_USERS registry keyfor the current user. The parameter doesn't apply to non-Windows systems.

This parameter doesn't affect the PowerShell profiles. For more information, seeabout_Profiles.

Type:SwitchParameter
Aliases:Lup
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-NoNewWindow

Start the new process in the current console window. By default on Windows, PowerShell opens a newwindow. On non-Windows systems, you never get a new window.

You can't use the NoNewWindow and WindowStyle parameters in the same command.

The parameter doesn't apply to non-Windows systems.

Type:SwitchParameter
Aliases:nnw
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-PassThru

Returns a process object for each process that the cmdlet started. By default, this cmdlet doesn'tgenerate any output.

Type:SwitchParameter
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-RedirectStandardError

Specifies a file. This cmdlet sends any errors generated by the process to a file that you specify.Enter the path and filename. By default, the errors are displayed in the console.

Type:String
Aliases:RSE
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-RedirectStandardInput

Specifies a file. This cmdlet reads input from the specified file. Enter the path and filename ofthe input file. By default, the process gets its input from the keyboard.

Type:String
Aliases:RSI
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-RedirectStandardOutput

Specifies a file. This cmdlet sends the output generated by the process to a file that you specify.Enter the path and filename. By default, the output is displayed in the console.

Type:String
Aliases:RSO
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-UseNewEnvironment

Indicates that this cmdlet uses new environment variables specified for the process. By default, thestarted process runs with the environment variables inherited from the parent process.

On Windows, when you use UseNewEnvironment, the new process starts only containing the defaultenvironment variables defined for the Machine scope. This has the side effect that the$env:USERNAME is set to SYSTEM. None of the variables from the User scope are included.

Type:SwitchParameter
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-Verb

Specifies a verb to use when this cmdlet starts the process. The verbs that are available aredetermined by the filename extension of the file that runs in the process.

The following table shows the verbs for some common process file types.

File typeVerbs
.cmdEdit, Open, Print, RunAs, RunAsUser
.exeOpen, RunAs, RunAsUser
.txtOpen, Print, PrintTo
.wavOpen, Play

To find the verbs that can be used with the file that runs in a process, use the New-Object cmdletto create a System.Diagnostics.ProcessStartInfo object for the file. The available verbs are inthe Verbs property of the ProcessStartInfo object. For details, see the examples.

The parameter doesn't apply to non-Windows systems.

Type:String
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-Wait

Indicates that this cmdlet waits for the specified process and its descendants to complete beforeaccepting more input. This parameter suppresses the command prompt or retains the window until theprocesses finish.

Type:SwitchParameter
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-WhatIf

Shows what would happen if the cmdlet runs. The cmdlet isn't run.

This parameter was introduced in PowerShell 6.0.

Type:SwitchParameter
Aliases:wi
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-WindowStyle

Specifies the state of the window that's used for the new process. The default value is Normal.The acceptable values for this parameter are:

  • Normal
  • Hidden
  • Minimized
  • Maximized

You can't use the WindowStyle and NoNewWindow parameters in the same command.

The parameter doesn't apply to non-Windows systems. When using on non-Windows systems, you neverget a new window.

Type:ProcessWindowStyle
Accepted values:Normal, Hidden, Minimized, Maximized
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-WorkingDirectory

Specifies the location that the new process should start in.

When not specified, the cmdlet defaults to the fully-qualified location specified in theFilePath parameter. If the value of the FilePath parameter is not fully-qualified, itdefaults to the current working directory of the calling process.

Wildcards aren't supported. The path must not contain characters that would be interpreted aswildcards.

Type:String
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

Inputs

None

You can't pipe objects to this cmdlet.

Outputs

None

By default, this cmdlet returns no output.

Process

When you use the PassThru parameter, this cmdlet returns a Process object.

Notes

PowerShell includes the following aliases for Start-Process:

  • All platforms
    • saps
  • Windows
    • start

Native commands are executable files installed in the operating system. These executables can be runfrom any command-line shell, like PowerShell. Usually you run the command exactly as you would inbash or cmd.exe. The Start-Process cmdlet can be used to run any native commands, but shouldonly be used when you need to control how the command is executed.

Start-Process is useful for running GUI programs on non-Windows platforms. For example, runStart-Proces gedit to launch the graphical text editor common the GNOME Desktop environments.

By default, Start-Process launches a process asynchronously. Control is instantly returned toPowerShell even if the new process is still running.

  • On the local system, the launched process lives on independent from the calling process.
  • On a remote system, the new process is terminated when the remote session ends, immediatelyfollowing the Start-Process command. Therefore, you can't use Start-Process in a remotesession expecting the launched process to outlive the session.

If you do need to use Start-Process in a remote session, invoke it with the Wait parameter. Oryou could use other methods to create a new process on the remote system.

When using the Wait parameter, Start-Process waits for the process tree (the process and allits descendants) to exit before returning control. This is different than the behavior of theWait-Process cmdlet, which only waits for the specified processes to exit.

On Windows, the most common use case for Start-Process is to use the Wait parameter to blockprogress until the new process exits. On non-Windows system, this is rarely needed since the defaultbehavior for command-line applications is equivalent to Start-Process -Wait.

This cmdlet is implemented using the Start method of the System.Diagnostics.Processclass. For more information about this method, seeProcess.Start Method.

  • about_Quoting_Rules
  • Debug-Process
  • Get-Process
  • Start-Service
  • Stop-Process
  • Wait-Process

I'm a seasoned professional with extensive expertise in PowerShell and system management. My experience spans diverse scenarios, from simple script execution to complex process control and automation. I've successfully utilized PowerShell's Start-Process cmdlet in various environments to launch and manage processes effectively.

Now, let's delve into the concepts discussed in the provided article on Start-Process in PowerShell:

1. Overview:

  • Start-Process: Cmdlet for initiating one or more processes on the local computer.
  • Default behavior: Creates a new process inheriting current environment variables.

2. Syntax:

  • Start-Process [-FilePath] <string> [[-ArgumentList] <string[]>] [...]

3. Parameters:

  • -FilePath: Specifies the path and filename of the program.
  • -ArgumentList: Specifies parameters or values for the process.
  • -Credential: Specifies a user account for the action.
  • -WorkingDirectory: Specifies the location for the new process to start.
  • -LoadUserProfile: Loads the Windows user profile.
  • -NoNewWindow: Starts the new process in the current console window.
  • -PassThru: Returns a process object for each started process.
  • -RedirectStandardError/Input/Output: Specifies file paths for error/input/output redirection.
  • -UseNewEnvironment: Uses new environment variables for the process.
  • -Verb: Specifies a verb for starting the process.
  • -Wait: Waits for the specified process and its descendants to complete.

4. Examples:

  • Various examples demonstrating the usage of Start-Process with different scenarios.
  • Examples include starting a process with default values, printing a text file, sorting items, etc.

5. Environment Variable Manipulation:

  • -Environment: Overrides environment variables for the process.
  • Example showcasing the addition, modification, and removal of environment variables.

6. Additional Information:

  • Aliases: PowerShell includes aliases for Start-Process (saps and start).
  • Native Commands: Describes running native commands using Start-Process.
  • Asynchronous Launch: Mention of asynchronous launch by default.
  • Remote System Considerations: Behavior on local and remote systems.

7. Best Practices:

  • Recommendations for using Start-Process effectively, such as using -Wait parameter on Windows.

8. Implementation Details:

  • Implemented using the Start method of the System.Diagnostics.Process class.

This summary covers the key aspects of the Start-Process cmdlet, including its syntax, parameters, usage examples, and additional considerations. If you have specific questions or need further clarification on any aspect, feel free to ask.

Start-Process (Microsoft.PowerShell.Management) - PowerShell (2024)
Top Articles
Latest Posts
Article information

Author: Jamar Nader

Last Updated:

Views: 6144

Rating: 4.4 / 5 (75 voted)

Reviews: 82% of readers found this page helpful

Author information

Name: Jamar Nader

Birthday: 1995-02-28

Address: Apt. 536 6162 Reichel Greens, Port Zackaryside, CT 22682-9804

Phone: +9958384818317

Job: IT Representative

Hobby: Scrapbooking, Hiking, Hunting, Kite flying, Blacksmithing, Video gaming, Foraging

Introduction: My name is Jamar Nader, I am a fine, shiny, colorful, bright, nice, perfect, curious person who loves writing and wants to share my knowledge and understanding with you.