Skip to content
Search found 7 matches
Search found 7 matches
Page 1 of 1
- by HelplessRube
- Sat Jun 12, 2021 3:25 am
- Forum: Viscosity Support (Windows Version)
- Topic: Advanced Configuration Line Breaks Broken
- Replies: 2
- Views: 5274
The current 1.9.4 beta appears to resolve the issue.
- by HelplessRube
- Fri Jun 11, 2021 4:14 pm
- Forum: Viscosity Support (Windows Version)
- Topic: Advanced Configuration Line Breaks Broken
- Replies: 2
- Views: 5274
On Surface Pro X / Windows ARM / Viscosity 1.9.3, I can't add line breaks when editing the connection's advanced configuration (and so, I can't add lines to the configuration).
- by HelplessRube
- Thu Jan 07, 2021 6:29 am
- Forum: Viscosity Support (Windows Version)
- Topic: Kill switch script requires elevation
- Replies: 9
- Views: 7968
Here is a script that ended up working for me:
Code: Select all
The call to this specific netsh executable succeeds, while a call to "C:\Windows\System32\netsh.exe" fails."C:\Windows\SysWOW64\netsh.exe" interface set interface "Wi-Fi" admin=DISABLED
- by HelplessRube
- Mon Jan 04, 2021 4:06 pm
- Forum: Viscosity Support (Windows Version)
- Topic: Kill switch script requires elevation
- Replies: 9
- Views: 7968
Thanks for the information. The simple "test" script does work.
- by HelplessRube
- Mon Jan 04, 2021 2:19 pm
- Forum: Viscosity Support (Windows Version)
- Topic: Kill switch script requires elevation
- Replies: 9
- Views: 7968
Thanks for the support. I'm still having a couple of issues. First, looks like I do have to turn on the "Allow unsafe OpenVPN commands to be used" setting. If I don't, the connections refuse to start and give the error: Error: The OpenVPN script is not located in the required directory (C:...
- by HelplessRube
- Mon Jan 04, 2021 11:44 am
- Forum: Viscosity Support (Windows Version)
- Topic: Kill switch script requires elevation
- Replies: 9
- Views: 7968
I have tried either way - same error code.
BTW - it wasn't clear to me whether this setting was necessary. The instructions don't refer to enabling this setting, and the x86 version worked fine without enabling it.
BTW - it wasn't clear to me whether this setting was necessary. The instructions don't refer to enabling this setting, and the x86 version worked fine without enabling it.
- by HelplessRube
- Mon Jan 04, 2021 8:01 am
- Forum: Viscosity Support (Windows Version)
- Topic: Kill switch script requires elevation
- Replies: 9
- Views: 7968
I'm also having problems with this. I'm using Viscosity 1.9 (1695) on two different computers - Windows 10 x86 64 bit and Windows 10 ARM 64. On the x86 system, the spark lab instructions work fine, but on the ARM 64 system, the command fails with an error: WARNING: Failed running command (--up/--dow...
Search found 7 matches
Page 1 of 1