ProcessEx VS PowerShell

If it's as another user then using Start-Process ... -Credential $cred will give you a process that is not elevated. If you want to start it as the current user there isn't really an easy way to do so with the cmdlets builtin and what dotnet offers you. If you are open to using a custom module I have ProcessEx which exposes the ability to start a new process with a custom parent. With this you can set the parent as explorer.exe which will be unelevated and the process inherits the same access token.

There are a few ways you can spawn a sub process as the limited token but it's not something you can easily do with the builtin cmdlets and dotnet APIs available. The simplest option I know is to spawn a new process with a custom parent that is not elevated. For example I can use my ProcessEx module to spawn a limited process with the parent of explorer.exe.

Using Start-ProcessWith with a -Credential object should work for both running in session 0 (Enter-PSSession) and using the -Wait parameter to wait for it to complete. Unfortunately it will spawn in a new window (which you can hide though). If you want it to run the new process as another user but in the same window you essentially need Start-ProcessEx with a -Token. This allows you to spawn a process in the current terminal but unfortunately the -Token side requires privileges that not even normal Administrators typically have, thus would need to be run as SYSTEM.

For Windows, the only thing you can do with an exe like this is to rely on the ConPTY APIs Windows provides and reads from that. Unfortunately there is no builtin way to do this with PowerShell so you are reliant on either writing the PInvoke code yourself or using a 3rd party module. I have one called ProcessEx which can be used to spawn a new process under a ConPTY and capture that as a string with the following:

msiexec.exe /package https://github.com/PowerShell/PowerShell/releases/download/v7.2.6/PowerShell-7.2.6-win-x64.msi /quiet ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1 ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL=1 ENABLE_PSREMOTING=1 REGISTER_MANIFEST=1 USE_MU=1 ENABLE_MU=1 ADD_PATH=1

This smells like when PowerShell aliased curl and wget to a completely different command, with incompatible arguments.

https://github.com/PowerShell/PowerShell/pull/1901

PowerShell is available on macOS and Linux as well (source on Github: https://github.com/PowerShell/PowerShell). It may not be as well-integrated with things like system services management, but the language still works well. You can still use all the command line tools you're used to on Linux, of course.

nushell does look interesting, though the lack of a .deb repository does put it pretty low on my to-do list.

Issue #7940 discusses potential improvements to array slicing.

Note: This can be problematic as it prevents upstream commands from running their end {} block. See here. The new clean {} block introduced in PowerShell v7.3 does not suffer from this issue.

Can you give an example of something that PS can do that is built-in for text processing, instead of a proprietary symbolic query language?

[1] https://github.com/PowerShell/PowerShell

https://github.com/PowerShell/PowerShell/blob/master/LICENSE... is the MIT license. (Microsoft supplies debs directly which may reduce the motivation for Debian to do so.)

Oh, heh, also https://github.com/PowerShell/PowerShell/blob/master/docs/bu... the build script is written in PowerShell, so there's a bootstrapping problem :-) (Debian has solved those before of course, but with community sentiment like the above maybe noone is motivated to bother.)

According to https://github.com/PowerShell/PowerShell/issues/19628, the default behaviour is invoked whenever the completion script returns no output. To attempt to do so, I tried exiting the script via returning an empty string, or using the return keyword to exit the script completely, unfortunately with no avail. Is there a technique to achieve what I want, and is there any documentation about it other than the official one? Thank you in advance.