237dmitry

Show your `$env:PATH -split ';'` There has to be two paths to `$PSHOME`. One is from system (or user's ?) environment and automatic one.

> doesn't find existing registry key >> existing Could not reproduce

> Which Windows build are you on? 23H2 Win 11 Home 22631.2506 

> The problem equally affects nested Start-ThreadJob and Start-Job calls I did not find any problems in pwsh-7.5.0-p.1 on Linux: ```powershell $ gc ./t.ps1 $foo = 1; 0..2 | ForEach-Object...

> the problem at hand is about nested $using contexts in the context of remoting ssh works fine, but Invoke-Command.... ``` $ Invoke-Command -HostName localhost -FilePath ./t.ps1 user@localhost's password: subsystem...

This work without starting issue: 

> you should see this fail on Unix-like platforms too Yes, when $foo set not in script (t.ps1), the error occurs

There is [slackbuild](https://slackbuilds.org/repository/15.0/system/powershell/?search=powershell) (precompiled)

> That's a build from a compressed tar release of PowerShell Yes, I always use it myself (Arch linux). There is no need to build anything, just extract tar.gz, chmod...

What's stopping you from using the format you need? For example, I don't need such an output to a file. I believe that users themselves should decide how they want...