Use of $env:COMSPEC may be invalid in some cases.

[u1f992]

In certain environments, this will be reproduced by running the installer as usual and launching Pico - Developer PowerShell.

Sorry for the Japanese UI, but it says "The expression after '&' in a pipeline element produced an object that was not valid. It must result in a command name, a script block, or a CommandInfo object."

This indicates that $env:COMSPEC is not defined. In fact, echo $env:COMSPEC did not print anything. Of course, I did not intentionally erase it... perhaps.

The disappearance seems to be a common occurrence, as evidenced by reports of similar problems occurring in other projects (other 3rd party applications supposedly erasing it? I have not investigated further).
ref: ScoopInstaller/Scoop#3845

Anyway, $env:COMSPEC is just an environment variable, and since it can disappear or contain strange things, some people think it is wise to specify cmd.exe directly if we obviously know we will use it.
ref: ScoopInstaller/Scoop#4692

[ndabas]

Thanks for the bug report/debugging and resolution! I will fix this for the next release.

[u1f992]

@ghollingworth No modifications have been made since this issue was opened, and $env:COMSPEC is still being used.

pico-setup-windows/packages/pico-setup-windows/pico-env.ps1

Line 6 in e412aa4

& "${env:COMSPEC}" /s /c "`"$PSScriptRoot\pico-env.cmd`" && set" | ForEach-Object {

Could you please explain why this issue was closed as completed?

Sorry, I saw your update to the README. It is unfortunate that support for pico-setup-windows is being discontinued.