Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
Thank you for the PR! I proposed to complete a bit by adding the fact that these commands must be run with administrator privileges. Is this okay for you?
  • Loading branch information
af-airbus authored Feb 21, 2025
1 parent 6212d5b commit 2a0205f
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -343,20 +343,20 @@ such as `nc`, and use the available command:

### Citrix

If you get an error like `failed to open channel handle: virtual channel open failed (last_error = 5)` that's means there are some restrictions on citrix host virtual channels (default behavior in last citrix version).
To fix this, you can disable citrix restrictions on virtual channels (which is not recommended):
If you get an error like `failed to open channel handle: virtual channel open failed (last_error = 5)` that's means there are some restrictions on citrix host virtual channels (default behavior in last Citrix version).
To fix this, if you have (local) administrator privileges, you can disable Citrix restrictions on virtual channels (which is not recommended):

```powershell
reg add HKLM\SOFTWARE\WOW6432Node\Policies\Citrix\VCPolicies /v VirtualChannelWhiteList /t REG_MULTI_SZ /d =disabled=
```

Or you can whitelist `SOXY` like this:
Or you can whitelist `SOXY` like this if you have (local) administrator privileges:

```powershell
reg add HKLM\SOFTWARE\WOW6432Node\Policies\Citrix\VCPolicies /v VirtualChannelWhiteList /t REG_MULTI_SZ /d SOXY,C:\Users\<USER>\<PATH_TO_SOXY_EXE>
```

Note that in both case, you have to reboot citrix host after.
Note that in both case, you have to reboot Citrix host after.

## 🚧 Contributing

Expand Down

0 comments on commit 2a0205f

Please sign in to comment.