Spaces cause split in path with PowerShell

Powershell

Powershell Problem Overview


I'm having an issue with powershell when invoking an exe at a path containing spaces.

PS C:\Windows Services> invoke-expression "C:\Windows Services\MyService.exe"

> The term 'C:\Windows' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

It seems to be splitting on the space between 'Windows' and 'Services'. Any idea how to get around this problem?

Powershell Solutions


Solution 1 - Powershell

Would this do what you want?:

& "C:\Windows Services\MyService.exe"

Use &, the call operator, to invoke commands whose names or paths are stored in quoted strings and/or are referenced via variables, as in the accepted answer. Invoke-Expression is not only the wrong tool to use in this particular case, it should generally be avoided.

Solution 2 - Powershell

You can escape the space by using single quotations and a backtick before the space:

$path = 'C:\Windows Services\MyService.exe'
$path -replace ' ', '` '
invoke-expression $path

Solution 3 - Powershell

"&'C:\Windows Services\MyService.exe'" | Invoke-Expression

via https://www.vistax64.com/powershell/52905-invoke-expression-exe-has-spaces-its-path.html

Solution 4 - Powershell

Not sure if someone still needs it... I needed to invoke msbuild in powershell and following worked fine:

$MSBuild = "${Env:ProgramFiles(x86)}\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\MSBuild.exe"

& $MSBuild $PathToSolution /p:OutDir=$OutDirVar /t:Rebuild /p:Configuration=Release

Solution 5 - Powershell

For any file path with space, simply put them in double quotations will work in Windows Powershell. For example, if you want to go to Program Files directory, instead of use

PS C:\> cd Program Files

which will induce error, simply use the following will solve the problem:

PS C:\> cd "Program Files"

Solution 6 - Powershell

This worked for me:

$scanresults = Invoke-Expression "& 'C:\Program Files (x86)\Nmap\nmap.exe' -vv -sn 192.168.1.1-150 --open"

Solution 7 - Powershell

Using Powershell on Windows10 in 2018, what worked for me was simply to replace double quotes " by simple quotes '. Adding the backtick before the space, as suggested in an answer, broke the path.

Solution 8 - Powershell

There's a hack I've used since the Invoke-Expression works fine for me.

You could set the current location to the path with spaces, invoke the expression, get back to your previous location and continue:

$currLocation = Get-Location
Set-Location = "C:\Windows Services\"
Invoke-Expression ".\MyService.exe"
Set-Location $currLocation

This will only work if the exe doesn't have any spaces in its name.

Hope this helps

Solution 9 - Powershell

Can use the . dot operator.

. "C:\Users\user\AppData\Local\Programs\Microsoft VS Code\bin\code.cmd"

or the Start-Process command

Start-Process -PSPath "C:\Users\user\AppData\Local\Programs\Microsoft VS Code\bin\code.cmd"

or using ProcessStartInfo and Process

$ProcessInfo = New-Object -TypeName System.Diagnostics.ProcessStartInfo
$ProcessInfo.FileName = 'C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe'
if($Admin){ $ProcessInfo.Verb = 'runas' }
$ProcessInfo.UseShellExecute = $false

$CommandParameters = '-noexit -noprofile -command Set-Location -LiteralPath c:\; $host.ui.RawUI.WindowTitle = ''[{0}] PS''; Set-PSReadlineOption -HistorySaveStyle SaveNothing;' -f $Cred.UserName
$ProcessInfo.Arguments = $CommandParameters
$ProcessInfo.Domain = ($Cred.UserName -split '\\')[0]
$ProcessInfo.UserName = ($Cred.UserName -split '\\')[1]
$ProcessInfo.Password = $Cred.Password

$ProcessObject = New-Object -TypeName System.Diagnostics.Process
$ProcessObject.StartInfo = $ProcessInfo
$ProcessObject.Start() | Out-Null

Solution 10 - Powershell

What worked for me (I needed the path to create a MySQL dump), was to place the directory in between 6 double quotes like so:

$path = """C:\Path\To\File"""

Solution 11 - Powershell

Please use this simple one liner:

Invoke-Expression "C:\'Program Files (x86)\Microsoft Office\root\Office16'\EXCEL.EXE"

Solution 12 - Powershell

Try this, simple and without much change:

invoke-expression "'C:\Windows Services\MyService.exe'"

using single quotations at the beginning and end of the path.

Solution 13 - Powershell

Simply put the path in double quotes in front of cd, Like this:

> cd "C:\Users\MyComputer\Documents\Visual Studio 2019\Projects"

Solution 14 - Powershell

Due to several PowerShell quoting rules that are used for passing arguments to native commands which also have specific experimental Features in PowerShell, quoting might get very confusing. Therefore the solution in some cases might be simply to don't go down the rabbit hole:

Avoid quoting file paths with spaces by using the 8.3 filenames

$FSO = New-Object -ComObject Scripting.FileSystemObject
$FSO.getfile('C:\Windows Services\MyService.exe').ShortPath
C:\WINDOW~1\MYSERV~1.EXE

Solution 15 - Powershell

Just put ${yourpathtofile/folder}

PowerShell does not count spaces; to tell PowerShell to consider the whole path including spaces, add your path in between ${ & }.

Solution 16 - Powershell

  1. enter the root C drive by entering command

> C:

  1. type cd and then press Tab key, it will toggle through all available locations and press enter when you have reached the desired one

> cd {press tab}

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionjaffaView Question on Stackoverflow
Solution 1 - PowershellAdil HindistanView Answer on Stackoverflow
Solution 2 - PowershellAnthony NeaceView Answer on Stackoverflow
Solution 3 - PowershellAlanView Answer on Stackoverflow
Solution 4 - PowershellJacek PlesnarView Answer on Stackoverflow
Solution 5 - PowershellCathyQianView Answer on Stackoverflow
Solution 6 - PowershellJ. FischleinView Answer on Stackoverflow
Solution 7 - PowershellseinecleView Answer on Stackoverflow
Solution 8 - Powershellc-chavezView Answer on Stackoverflow
Solution 9 - PowershelljkdbaView Answer on Stackoverflow
Solution 10 - PowershellMvHView Answer on Stackoverflow
Solution 11 - PowershellpramodView Answer on Stackoverflow
Solution 12 - PowershelldjspView Answer on Stackoverflow
Solution 13 - PowershellShoaib KhalilView Answer on Stackoverflow
Solution 14 - PowershelliRonView Answer on Stackoverflow
Solution 15 - PowershellGSKKCView Answer on Stackoverflow
Solution 16 - Powershelltechloris_109View Answer on Stackoverflow