Windows is reporting a problem with Viscosity's network interface. Status :-1

Got a problem with Viscosity or need help? Ask here!

mcleanit

Posts: 2
Joined: Tue Nov 09, 2021 9:17 am

Post by mcleanit » Tue Nov 09, 2021 9:26 am
I keep getting this error on specifically one computer. I've done all the troubleshooting I can think of: Updating Windows, DISM repair, SFC, CHKDSK, removing the TUN/TAP drivers, reinstalling Viscosity, updating to beta version, re-creating the profile, etc.

Nothing works so far.

Nov 08 2:16:50 PM: State changed to Connecting
Nov 08 2:16:50 PM: Viscosity Windows 1.10.1 (1746) Beta1
Nov 08 2:16:50 PM: Running on Windows 10 2009 (19043) 64 bit
Nov 08 2:16:50 PM: Running on .NET Framework Version 4.8.04084.528372
Nov 08 2:16:50 PM: Checking reachability status of connection...
Nov 08 2:16:50 PM: Connection is reachable. Starting connection attempt.
Nov 08 2:16:50 PM: Interface Type: visctap0901
Nov 08 2:16:50 PM: Bringing up interface...
Nov 08 2:16:50 PM: 2021-11-08 14:16:50 WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set.
Nov 08 2:16:50 PM: 2021-11-08 14:16:50 WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set.
Nov 08 2:16:50 PM: DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
Nov 08 2:16:50 PM: OpenVPN 2.5.4 Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [AEAD] built on Oct 18 2021
Nov 08 2:16:50 PM: library versions: OpenSSL 1.1.1l 24 Aug 2021, LZO 2.10
Nov 08 2:16:56 PM: Resolving address: "___SERVER FQDN___"
Nov 08 2:16:56 PM: Valid endpoint found: ___SERVER FQDN___:1194:udp
Nov 08 2:16:56 PM: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Nov 08 2:16:56 PM: TCP/UDP: Preserving recently used remote address: [AF_INET]__SERVER IP__:1194
Nov 08 2:16:56 PM: UDP link local (bound): [AF_INET][undef]:1194
Nov 08 2:16:56 PM: UDP link remote: [AF_INET]__SERVER IP__:1194
Nov 08 2:16:56 PM: State changed to Authenticating
Nov 08 2:16:57 PM: [___SERVER FQDN___] Peer Connection Initiated with [AF_INET]__SERVER IP__:1194
Nov 08 2:16:57 PM: State changed to Connecting
Nov 08 2:16:57 PM: Awaiting adapter to come up...
Nov 08 2:16:57 PM: Windows is reporting a problem with Viscosity's network interface. Errorcode = -1
Nov 08 2:16:57 PM: State changed to Disconnecting (Adapter Startup Failed)

Eric

User avatar
Posts: 1146
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Tue Nov 09, 2021 10:26 am
Hi mcleanit,

A status of -1 means that Viscosity & ViscosityService are being blocked from accessing system resources and information. The most likely culprit is AV or enterprise security software which is blocking either process. Please ensure both processes are whitelisted, you may wish to try disabling any security software temporarily to see if this helps. After disabling, you will most likely need to restart the service.

If disabling security software doesn't help, or you don't have any, the system is most likely damaged and will need a repair on Windows from Settings -> Update & Security -> Recovery.

Regards,
Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

mcleanit

Posts: 2
Joined: Tue Nov 09, 2021 9:17 am

Post by mcleanit » Tue Nov 09, 2021 10:32 am
Thanks Eric I'll try that.

When you say "a repair on Windows from Settings -> Update & Security -> Recovery" can I assume you mean the "Reset this PC" option or did you mean one of the "Troubleshooters"?

Eric

User avatar
Posts: 1146
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Tue Nov 09, 2021 6:32 pm
Hi mcleanit,

The troubleshooters only tend to fix obvious issues in my experience, there's no harm trying them though. "Reset this PC", or a complete reimage is what I'd recommend though for a single machine having a localised issue within a fleet.

Regards,
Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
4 posts Page 1 of 1