How can I get the current PowerShell executing file

Question

Note  PowerShell 1 0 I d like to get the current executing PowerShell file name  That is  if I start my session like this     powershell exe   myfile ps1   I d like to get the string    myfile ps1   or something like that   EDIT   myfile ps1  is preferable  Any ideas

User · Answer

Try the following    path     MyInvocation MyCommand Definition    This may not give you the actual path typed in but it will give you a valid path to the file

User · Answer

If you only want the filename  not the full path  use this    ScriptName    MyInvocation MyCommand Name

User · Answer

beware  Unlike the  PSScriptRoot and  PSCommandPath automatic variables  the       PSScriptRoot and PSCommandPath properties of the  MyInvocation automatic       variable contain information about the invoker or calling script  not the       current script   e g   PS C  Users S ms OneDrive Documents gt  C  Users SP ms OneDrive Documents DPM       C  Users S ms OneDrive Documents DPM ps1      where DPM ps1 contains  Write-Host        MyInvocation PSCommandPath       PSCommandPath

User · Answer

This can works on most powershell versions     amp     MyInvocation ScriptName       This can work for Scheduled Job  Get-ScheduledJob    Name -Match  JOBNAMETAG     Command

User · Answer

I would argue that there is a better method  by setting the scope of the variable  MyInvocation MyCommand Path   ex   script MyInvocation MyCommand Name  This method works in all circumstances of invocation   EX  Somescript ps1  function printme           In function          MyInvocation ScriptName       string   MyInvocation ScriptName           script MyInvocation MyCommand Name       string   script MyInvocation MyCommand Name           MyInvocation MyCommand Name       string   MyInvocation MyCommand Name       Main      MyInvocation ScriptName       string   MyInvocation ScriptName       script MyInvocation MyCommand Name       string   script MyInvocation MyCommand Name       MyInvocation MyCommand Name       string   MyInvocation MyCommand Name        printme exit   OUTPUT   PS gt  powershell C  temp test ps1 Main  MyInvocation ScriptName  script MyInvocation MyCommand Name  test ps1 MyInvocation MyCommand Name  test ps1  In function  MyInvocation ScriptName  C  temp test ps1 script MyInvocation MyCommand Name  test ps1 MyInvocation MyCommand Name  printme   Notice how the above accepted answer does NOT return a value when called from Main  Also  note that the above accepted answer returns the full path when the question requested the script name only  The scoped variable works in all places   Also  if you did want the full path  then you would just call    script MyInvocation MyCommand Path

User · Answer

I ve tried to summarize the various answers here  updated for PowerShell 5   If you re only using PowerShell 3 or higher  use  PSCommandPath  If want compatibility with older versions  insert the shim  if   PSCommandPath -eq  null    function GetPSCommandPath     return  MyInvocation PSCommandPath     PSCommandPath   GetPSCommandPath    This adds  PSCommandPath if it doesn t already exist  The shim code can be executed anywhere  top-level or inside a function   though  PSCommandPath variable is subject to normal scoping rules  eg  if you put the shim in a function  the variable is scoped to that function only     Details There s 4 different methods used in various answers  so I wrote this script to demonstrate each  plus  PSCommandPath   function PSCommandPath     return  PSCommandPath    function ScriptName     return  MyInvocation ScriptName    function MyCommandName     return  MyInvocation MyCommand Name    function MyCommandDefinition           Begin of MyCommandDefinition         Note  ouput of this script shows the contents of this function  not the execution result     return  MyInvocation MyCommand Definition        End of MyCommandDefinition     function MyInvocationPSCommandPath     return  MyInvocation PSCommandPath     Write-Host  quot  quot   Write-Host  quot PSVersion     PSVersionTable PSVersion  quot   Write-Host  quot  quot   Write-Host  quot   PSCommandPath  quot   Write-Host  quot      Direct   PSCommandPath quot   Write-Host  quot    Function    PSCommandPath  quot   Write-Host  quot  quot   Write-Host  quot   MyInvocation ScriptName  quot   Write-Host  quot      Direct     MyInvocation ScriptName  quot   Write-Host  quot    Function    ScriptName  quot   Write-Host  quot  quot   Write-Host  quot   MyInvocation MyCommand Name  quot   Write-Host  quot      Direct     MyInvocation MyCommand Name  quot   Write-Host  quot    Function    MyCommandName  quot   Write-Host  quot  quot   Write-Host  quot   MyInvocation MyCommand Definition  quot   Write-Host  quot      Direct     MyInvocation MyCommand Definition  quot   Write-Host  quot    Function    MyCommandDefinition  quot   Write-Host  quot  quot   Write-Host  quot   MyInvocation PSCommandPath  quot   Write-Host  quot      Direct     MyInvocation PSCommandPath  quot   Write-Host  quot    Function    MyInvocationPSCommandPath  quot   Write-Host  quot  quot    Output  PS C   gt    Test test ps1  PSVersion  5 1 19035 1   PSCommandPath       Direct  C  Test test ps1    Function  C  Test test ps1   MyInvocation ScriptName       Direct     Function  C  Test test ps1   MyInvocation MyCommand Name       Direct  test ps1    Function  MyCommandName   MyInvocation MyCommand Definition       Direct  C  Test test ps1    Function        Begin of MyCommandDefinition         Note this is the contents of the MyCommandDefinition   function  not the execution results     return  MyInvocation MyCommand Definition        End of MyCommandDefinition      MyInvocation PSCommandPath       Direct     Function  C  Test test ps1  Notes   Executed from C    but actual script is C  Test test ps1  No method tells you the passed invocation path    Test test ps1   PSCommandPath is the only reliable way  but was introduced in PowerShell 3 For versions prior to 3  no single method works both inside and outside of a function

User · Answer

If you are looking for the current directory in which the script is being executed  you can try this one    fullPathIncFileName    MyInvocation MyCommand Definition  currentScriptName    MyInvocation MyCommand Name  currentExecutingPath    fullPathIncFileName Replace  currentScriptName       Write-Host  currentExecutingPath

User · Answer

A short demonstration of  gregmac s  excellent and detailed  answer  which essentially recommends  PSCommandPath as the only reliable command to return the currently running script where Powershell 3 0 and above is used  Here I show returning either the full path or just the file name  Test ps1   Direct    PSCommandPath    Full Path  Split-Path -Path  PSCommandPath -Leaf    File Name only  function main              Within a function      PSCommandPath   Split-Path -Path  PSCommandPath -Leaf    main  Output  PS gt    Test ps1 Direct  C  Users John Documents Sda Code Windows PowerShell Apps xBankStatementRename Test ps1 Test ps1  Within a function  C  Users John Documents Sda Code Windows PowerShell Apps xBankStatementRename Test ps1 Test ps1

User · Answer

While the current Answer is right in most cases  there are certain situations that it will not give you the correct answer  If you use inside your script functions then    MyInvocation MyCommand Name    Returns the name of the function instead name of the name of the script   function test        MyInvocation MyCommand Name     Will give you  test  no matter how your script is named  The right command for getting the script name is always    MyInvocation ScriptName   this returns the full path of the script you are executing  If you need just the script filename than this code should help you   split-path  MyInvocation PSCommandPath -Leaf

User · Answer

Did some testing with the following script  on both PS 2 and PS 4 and had the same result  I hope this helps people    PSVersionTable PSVersion function PSscript      PSscript   Get-Item  MyInvocation ScriptName   Return  PSscript       PSscript   PSscript  PSscript FullName  PSscript Name  PSscript BaseName  PSscript Extension  PSscript DirectoryName      PSscript   Get-Item  MyInvocation InvocationName  PSscript FullName  PSscript Name  PSscript BaseName  PSscript Extension  PSscript DirectoryName   Results -  Major  Minor  Build  Revision -----  -----  -----  -------- 4      0      -1     -1        C  PSscripts Untitled1 ps1 Untitled1 ps1 Untitled1  ps1 C  PSscripts  C  PSscripts Untitled1 ps1 Untitled1 ps1 Untitled1  ps1 C  PSscripts

User · Answer

As noted in previous responses  using   MyInvocation  is subject to scoping issues and doesn t necessarily provide consistent data  return value vs  direct access value   I ve found that the  cleanest   most consistent  method for getting script info like script path  name  parms  command line  etc  regardless of scope  in main or subsequent nested function calls  is to use  Get-Variable  on  MyInvocation        Get the MyInvocation variable at script level   Can be done anywhere within a script  ScriptInvocation    Get-Variable MyInvocation -Scope Script  Value    Get the full path to the script  ScriptPath    ScriptInvocation MyCommand Path    Get the directory of the script  ScriptDirectory   Split-Path  ScriptPath    Get the script name   Yes  could get via Split-Path  but this is  simpler  since this is the default return value  ScriptName    ScriptInvocation MyCommand Name    Get the invocation path  relative to  PWD     GregMac  this addresses your second point  InvocationPath   ScriptInvocation InvocationName   So  you can get the same info as  PSCommandPath  but a whole lot more in the deal  Not sure  but it looks like  Get-Variable  was not available until PS3 so not a lot of help for really old  not updated  systems   There are also some interesting aspects when using  -Scope  as you can backtrack to get the names  etc  of the calling function s   0 current  1 parent  etc   Hope this is somewhat helpful   Ref  https   docs microsoft com en-us powershell module microsoft powershell utility get-variable

[powershell] How can I get the current PowerShell executing file?

Examples related to powershell