How to get current username in Windows Powershell?

Question

How to get the current username in Windows Powershell?

Answer 1

$env:username is the easiest way

Answer 2

I'd like to throw in the whoami command, which basically is a nice alias for doing %USERDOMAIN%\%USERNAME% as proposed in other answers.

Write-Host "current user:"
Write-Host $(whoami)

Answer 3

1. get-content "cm.txt"
2. write-host "entr file name" $file = read-host get-content $file
3. $content = get-content "cm.txt"
4. $content = get-content "cn.txt" for each ($line in $count) {write-host $line}

Answer 4

In my case, I needed to retrieve the username to enable the script to change the path, ie. c:\users\%username%\. I needed to start the script by changing the path to the users desktop. I was able to do this, with help from above and elsewhere, by using the get-location applet.

You may have another, or even better way to do it, but this worked for me:

$Path = Get-Location

Set-Location $Path\Desktop

Answer 5

I thought it would be valuable to summarize and compare the given answers.

If you want to access the environment variable:

(easier/shorter/memorable option)

• [Environment]::UserName -- @ThomasBratt
• $env:username -- @Eoin
• whoami -- @galaktor

---

If you want to access the windows access token:

(more dependable option)

• [System.Security.Principal.WindowsIdentity]::GetCurrent().Name -- @MarkSeemann

---

If you want the name of the logged in user

(rather than the name of the user running the PowerShell instance)

• $(Get-WMIObject -class Win32_ComputerSystem | select username).username -- @TwonOfAn on this other forum

---

Comparison

@Kevin Panko's comment on @Mark Seemann's answer deals with choosing one of the categories over the other:

[The windows access token approach] is the most secure answer because $env:USERNAME can be altered by the user, but this will not be fooled by doing that.

In short, the environment variable option is more succinct, and the windows access token option is more dependable.

I've had to use @Mark Seemann's windows access token approach in a PowerShell script that I was running from a C# application with impersonation. The C# application is run with my user account, and it runs the powershell script as a service account. Because of a limitation of the way I'm running the PowerShell script from C#, the PowerShell instance uses my user account's environment variables, even though it is run as the service account user. In this setup, the environment variable options return my account name, and the windows access token option returns the service account name (which is what I wanted), and the logged in user option returns my account name.

---

Testing

Also, if you want to compare the options yourself, here is a script you can use to run a script as another user. You need to use the Get-Credential cmdlet to get a credential object, and then run this script with the script to run as another user as argument 1, and the credential object as argument 2.

Usage:

$cred = Get-Credential UserTo.RunAs
Run-AsUser.ps1 "whoami; pause" $cred
Run-AsUser.ps1 "[System.Security.Principal.WindowsIdentity]::GetCurrent().Name; pause" $cred

Contents of Run-AsUser.ps1 script:

param(
  [Parameter(Mandatory=$true)]
  [string]$script,
  [Parameter(Mandatory=$true)]
  [System.Management.Automation.PsCredential]$cred
)

Start-Process -Credential $cred -FilePath 'powershell.exe' -ArgumentList 'noprofile','-Command',"$script"

Answer 6

[System.Security.Principal.WindowsIdentity]::GetCurrent().Name