Doc and install: avoid security issue on Windows

[paugier]

Problem description

In https://pixi.sh/latest/, the given install command is currently

iwr -useb https://pixi.sh/install.ps1 | iex

I was not able to run this because of a security software.

However, I was able to follow the installation instructions "Install via Scoop:" in https://pipx.pypa.io/stable/installation/ for which one needs to execute:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Invoke-RestMethod -Uri https://get.scoop.sh | Invoke-Expression

Therefore, I guess installation instructions for Pixi (or the script I don't know) could be improved to avoid such security blockage.

[ruben-arts]

Thanks for the tip! Would you be able to share the command that did work for you?

[paugier]

I was finally able to install Pixi with the .ps1 installer with

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
irm https://pixi.sh/install.ps1 -OutFile install-pixi.ps1
iex .\install-pixi.ps1

So it might just be that what does not like the security software is only the | iex ? However, | Invoke-Expression worked with Scoop, so I don't know.

It might be useful to improve the documentation. About this potential issue with security solftware and also not using short Powershell aliases. I guess very few people know "irm" and "iex" so it is really "copy paste this command that you don't understand". The longer version with few steps and with a local (and checkable) install-pixi.ps1 script might be better (?). Anyway, people copy/paste so Invoke-Expression could be better than iex in documentation.

[JoerivanEngelen]

FYI: On our company's Windows laptops, we also have to set the execution policy of Powershell to install pixi. Some more info I found (for Windows 7, but still relevant on Windows 11)

On our machines, this is sufficient:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
iwr -useb https://pixi.sh/install.ps1 | iex