PowerShell not showing up in contextual menu on Windows 11 Pro

[Jeremy-Krall]

Prerequisites

• I have read CONTRIBUTING.md

Rayhunter Version

v0.9.0

Device

Orbic RC400L

Installer OS

Windows

Describe the Issue

The install website states "hold Shift, Right-Click inside the folder, then click "Open in PowerShell"" to launch installer.exe. But on Windows 11 Pro the option to use PowerShell is not in the contextual menu. And if someone uses the normal Command Prompt tool (assuming PowerShell isn't there) putting the password in with single quotes around it results in a retcode: 201 error. Double quotes needs to be used within Command Prompt.

[untitaker]

trying to think of the best way to handle this without unnecessarily bloating the docs

1. some admin passwords contain dollar signs, so posix needs single quotes, or we end up explaining shell escaping
2. cmd is annoying to deal with because people have to figure out how to open it and cd to the right directory. we don't want to assume familiarity with cmd.
3. pretty sure on my win11 install, the menu exists, not sure why it doesn't.
4. i'd like to avoid adding per-OS commands to the docs, keep it simple

maybe it won't matter if we end up shipping the installer GUI

[eabase]

Indeed, from instructions:

On Windows you can decompress using the file browser, then navigate to the folder that contains installer.exe, hold Shift, Right-Click inside the folder, then click "Open in PowerShell".

This is simply not true in general. There's is no such context menu in Win-11 Pro, unless you add it yourself, or you're lucky your Windows install variant added it for you. Most likely it was added when you installed powershell.

You did install Powershell 7 (core), right!? Right❓

@untitaker

I totally agree, avoid any use of legacy CMD garbage!
But I also fail to see why someone who intend to build and configure an IC are not able to open a posh shell and cd to find their own file. So I'm sure it's ok to mention that Windows users have to use a recent powershell version (if not already on Win-11), and double quotes.

[untitaker]

@eabase honestly I can't remember if I explicitly installed powershell on my machine. it's possible that that step is missing from the docs.

EDIT: nah it's powershell 5, which allegedly is the preinstalled one

[untitaker]

But I also fail to see why someone who intend to build and configure an IC are not able to open a posh shell and cd to find their own file

we're aiming to be more user friendly than that, hence there is work ongoing to build a GUI around the installer. for as long as we only have the CLI though we need to give as much guidance as possible without bloating the docs unnecessarily. it's just tricky because most devs here are not using windows primarily/fulltime