runa | A Python-like systems programming language

I think your code is fine and the issue is in the execution context as you suspected. I get the same error when trying to run powercfg /srumutil in non-elevated PowerShell session, while it works fine in elevated which points into lack of admin rights. But, in this case, the error message might be misleading. I also get the same error when running the code in x86 process, instead of x64 - both in PowerShell and C#. Try to check if your application is x86 or x64 and compare that to the PowerShell process in which you test that powercfg /srumutil runs fine.

powershell.exe, the Windows PowerShell CLI, doesn't directly support -Verb RunAs in order to launch a process with elevation (as admin).

Instead, you must use use the -Command (-c) parameter to pass a command that calls Start-Process -Verb RunAs, which in turn requires a nested powershell.exe call in order to execute the .ps1 file with elevation:

Here's a proof of concept that uses the following approach:

• Make the powershell call invoke another, aux. powershell instance as the elevated target process.

• This allows the outer powershell instance to "bake" Set-Item statements that re-create the caller's environment variables (which the outer instance inherited, and which can therefore be enumerated with Get-ChilItem Env:) into the -command string passed to the aux. instance, followed by a re-invocation of the original batch file.

Caveat: This solution blindly recreates all environment variables defined in the caller's process in the elevated process - consider pre-filtering, possibly by name patterns, such as by a shared prefix; e.g., to limit variable re-creation to those whose names start with foo, replace Get-ChildItem Env: with Get-ChildItem Env:foo* in the command below.

You can not keep variables, you will lose them immediately after the new window is created, the best you can do instead is to create a script containing all your activities then save it in the same working directory.

When you open a new window just call your script that will be able to give you the same information as in the other window.

You can try the following workarounds to resolve this issue:

• Check Visual studio is running as administrator.
• Checkbotframework.com whether bot is listed.
• Users have the write to create apps in AD.

Also try the below steps:

1. go to your bot in the Azure portal.
2. select the 'Authentication' menu on the left panel.
3. select 'Accounts in any organizational directory (Any Azure AD directory - Multitenant)' in the 'Supported account types' as below :

^{Note: On 15 Nov 2021 a bug was fixed in the code below in order to make it work properly with advanced scripts - see this answer for details.}

The closest you can get to a robust, cross-platform self-elevating script solution that supports:

• both positional (unnamed) and named arguments
  • while preserving type fidelity within the constraints of PowerShell's serialization (see this answer)
• preserving the caller's working directory.
• On Unix-like platforms only: synchronous, same-window execution with exit-code reporting (via the standard sudo utility).

is the following monstrosity (I certainly wish this were easier):

• Note:

  • For (relative) brevity, I've omitted your Test-IsUacEnabled test, and simplified the test for whether the current session is already elevated to [bool] (net.exe session 2>$null)

  • You can drop everything between # --- BEGIN: Helper function for self-elevation. and # --- END: Helper function for self-elevation. into any script to make it self-elevating.

    • If you find yourself in repeated need of self-elevation, in different scripts, you can copy the code into your $PROFILE file or - better suited to wider distribution - convert the dynamic (in-memory) module used below (via New-Module) into a regular persisted module that your scripts can (auto-)load. With the Ensure-Elevated function available available via an auto-loading module, all you need in a given script is to call Ensure-Elevated, without arguments (or with -Verbose for verbose output).

Quoting this excellent answer which explains really well what you're doing wrong:

PowerShell aliases do not allow for arguments.
They can only refer to a command name, which can be the name of a cmdlet or a function, or the name / path of a script or executable

And from the official Docs:

The Set-Alias cmdlet creates or changes an alias for a cmdlet or a command, such as a function, script, file, or other executable. An alias is an alternate name that refers to a cmdlet or command.

This should help you understand what is going:

I believe this should work, it's easier if you use a Here-String. Since you're using the -like operator, I would assume you're looking for a Log that "contains" the input given in $PiEventLog, in that case, you should use wildcard characters: -like "*$PiEventLog*".

With @mklement0's help (see the comment above), I realized I had to use a double-quoted string with Start-Process to make the instruction work: