If I run the following command in a Poweshell script file ($cmd refers to some executable):
Start-Process -FilePath $cmd -Verb RunAs Powershell
Then it executes OK
But if I slightly modify it:
Start-Process -NoNewWindow -FilePath $cmd -Verb RunAs Powershell
Or like this:
Start-Process -FilePath $cmd -ArgumentList @("status") -Verb RunAs Powershell
... then the command fails with the following error message:
Start-Process : Parameter set cannot be resolved using the specified named parameters.
I wonder why this format is not accepted and how should I modify the command to both specify an argument list and option "-Verb RunAs..."
Guessing that -NoNewWindow and -Verb RunAs cannot be combined since you can't elevate the session currently used.
Upon futher investigation you are not the only one to look into this. I read that they are incompatible here
Depending on your motivation for running it like this you could just hide the window
Start-Process "powershell" -Verb "runas" -WindowStyle hidden
You can also look into PSSessions which can handle this type of thing as well. That could start an interactive session in the same window.
Maybe this helps you out:
$cmd = 'powershell.exe'
$arguments = "-NoLogo -NoProfile -WindowStyle Maximized"
Start-Process $cmd $arguments -Verb runAs
Another example from here:
Start-Process powershell -Credential mydomain\mydomainAdmin -ArgumentList '-noprofile -command &{Start-Process notepad -verb runas}'
Can you try it with your program and arguments and see how it goes?
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With