Skip to content

fix(docs): use one-time PowerShell bypass for install.ps1 #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RenatoFarruggio wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix(docs): use one-time PowerShell bypass for install.ps1 #3

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
21ddbb1
docs: use one-time PowerShell bypass for install.ps1
RenatoFarruggio Feb 28, 2026
aae502c
docs: update formulation
RenatoFarruggio Feb 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 3 additions & 11 deletions docs/public/docs/help/troubleshoot.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,21 +16,13 @@ If you still want to use the app, you will need to:

It's possible that your computer has a restricted script execution policy set, either by you or via a company Device Management System.

In order to check if that's the case for the execution of the script, you should open `Powershell` in Administrator mode, and run:
In order to run the installation script without changing your system policy, open `Powershell` as your current user (not Administrator), move to the folder that contains `install.ps1`, and run:

```powershell
Get-ExecutionPolicy
PowerShell -ExecutionPolicy Bypass -File install.ps1
```

There you will be able to check the current execution policy. In order to allow the installation of the script, you can run this command:

```powershell
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine
```

It will only allow to run scripts that are signed, and the provided `install.ps1` is properly signed, so your computer should be able to run it without any further restrictions.

Once you have successfully installed it, you can set back the execution policy to its previous value by running back again the `Set-ExecutionPolicy` command and passing the original value you got by running `Get-ExecutionPolicy`.
This command applies a bypass for this script execution without changing your current execution policy.

## SSH Agent troubleshooting

Expand Down