start-process

I have a PowerShell script that edits the registry, so it needs to run as admin. To do this, I start up a new PowerShell process from my running PowerShell script, and pass in part of the registry key path using a Script Block with a function in it. When I use double quotes within that function, PowerShell tries to interpret them as commands, rather than a string. If I use single quotes though, then everything works fine. I've created a little stripped down sample powershell script that reproduces the problem. Here's the snippet: $ScriptBlock = { function Test { $status = "This is a string"

For some odd reaseon this code fails: p.StartInfo.FileName = @"%temp%\SSCERuntime_x86-ENU.msi"; and this code succes: p.StartInfo.FileName = @"C:\Users\USERNAME\AppData\Local\Temp\SSCERuntime_x86-ENU.msi"; Is there any reason I am missing? Note I just copied the path, I don't think the rest of the code is needed but I'll put it anyway: Process p = new Process(); p.StartInfo.FileName = @"%temp%\SSCERuntime_x86-ENU.msi"; p.StartInfo.Arguments = "/passive"; p.Start(); The Process class does not expand strings with environment variables (i.e. %temp% ). If you want to use environment variables to

I've got a script that's I want to run as a scheduled task, but it's not doing the thing it's supposed to. I'm trying to call an executable with Start-Process and the -Wait switch before continuing. Line is Start-Process -FilePath "C:\Pfx Engagement\Admin\Utilities\Backup Restore\BackupRestoreUtil.exe" -ArgumentList "/f "$backup_directory "" -Wait If I call it from a command prompt, ie: powershell .\script.ps1 it works. It runs the command and waits for it to finish before moving on. There's more to the script that has to be run after that command is finished. The problem is that when it's a

I'm running into a strange behavior with a powershell Start-Process call. Here is the call: $process = start-process ` "C:\somepath\MyBinary.exe" ` -PassThru ` -Credential $defaultCredential ` -Wait ` -WorkingDirectory "C:\somepath" ` -LoadUserProfile if ($process.ExitCode -ne 0) { #do something } This call always return with the exit code - 1073741502 . After a quick search, this exit code seems related to a generic error when the program could not load its required dll (aka. STATUS_DLL_INIT_FAILED ). When I run it without -Credential $credential the program runs correctly. In order to

Im my PS script I want to be able to run another script in another PS instance by doing the following: $filepath = Resolve-Path "destruct.ps1" start-process powershell.exe "$filepath" destruct.ps1 is in the same folder as this script However when running this script in a location which includes spaces ("C:\My Scripts\") i will get the following error: The term 'C:\My' is not recognized as a cmdlet, function, operable program, or script file. Verify the term and try again. I know by using a '&' with the Invoke-Expression method solves this problem, how can i do the same but by using the start