Process is killed when PowerShell exits

[crashingstatic]

If a process is being paused by Pause-Process, the Powershell session that invoked Pause-Process needs to remain open for the process to continue to be paused. Once the session exits, the paused process is then terminated.

[crashingstatic]

Start-AppBackgroundTask requires a GUID of the task to be performed.
Get-AppBackgroundTask shows that only Windows Packages Families (e.g. "Microsoft.BingSports_8wekyb3d8bbwe") are listed with GUIDs, not individual processes.

[crashingstatic]

$job=Start-Job -ScriptBlock {Pause-Process -ID 1288} returned without error but...

Receive-Job -Job $job
The term 'pause-process' 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.
    + CategoryInfo          : ObjectNotFound: (pause-process:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
    + PSComputerName        : localhost

Invoke-Command -ScriptBlock {Start-Job -ScriptBlock {pause-process -ID 1288}}

Id     Name            PSJobTypeName   State         HasMoreData     Location             Command
--     ----            -------------   -----         -----------     --------             -------
5      Job5            BackgroundJob   Running       True            localhost            pause-process -ID 1288

Did not successfully pause PID 1288. Both of these methods would have been problematic due to the requirement that pause-process would have to be loaded as a local module for each session.

[crashingstatic]

What if you execute the code remotely without ever spawning powershell.exe in the first place? Would that change anything?

https://github.com/Mr-Un1k0d3r/PowerLessShell

[crashingstatic]

Take another look at Kansa. They've added asynchronity and powershell spawning. Watch out for EDR-freak-outs!

https://github.com/davehull/Kansa