MAJOR problem, please help!

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

asdffdsa6131

Posts: 30
Joined: Sat Feb 23, 2019 12:15 pm

Post by asdffdsa6131 » Sat Jan 30, 2021 2:20 am
Hello,

I have run into major problems with the software on windows.
Computationally crippled now!
I sent the following as an email but i am also posting in the forum.

When creating a new connection, the software fails to create a new adapter.

So I
--- uninstalled the software.
--- checked that C:\Program Files\Viscosity no longer existed.
--- checked that C:\Users\user01\AppData\Roaming\Viscosity no longer existed.
--- checked that Viscosity Virtual TUN Adapter no longer existed.
--- rebooted
--- installed Viscosity Installer 1.9.exe
--- tried to create a new connection, got the following error from the connection log.

Jan 29 10:04:29 AM: State changed to Creating...
Jan 29 10:04:59 AM: Failed to create adapter.
Jan 29 10:04:59 AM: State changed to Disconnected

After the re-install I noticed this in device manager, that yellow warning icon.
see the attached image.

Please, what is the next step?

Thanks in advance,
David
Attachments
driver.icon.PNG
driver.icon.PNG (5.34 KiB) Viewed 2494 times

asdffdsa6131

Posts: 30
Joined: Sat Feb 23, 2019 12:15 pm

Post by asdffdsa6131 » Sat Jan 30, 2021 2:42 am
after the re-install, i also tried to and failed with the same error "Failed to create adapter."
--- delete all connections
--- switch to using legacy adapter.
--- create new connection

asdffdsa6131

Posts: 30
Joined: Sat Feb 23, 2019 12:15 pm

Post by asdffdsa6131 » Sat Jan 30, 2021 4:27 am
imported another connection, got new error about a source code file "tun.c"

Jan 29 12:24:20 PM: State changed to Connecting
Jan 29 12:24:20 PM: Awaiting adapter to come up...
Jan 29 12:24:20 PM: Failed to process command >OPENTUN:HANDLE. The handle is invalid
Jan 29 12:24:20 PM: Netsh method failed. Object reference not set to an instance of an object.
Jan 29 12:24:20 PM: WARNING: The TAP-Windows driver rejected a TAP_WIN_IOCTL_SET_MEDIA_STATUS DeviceIoControl call. The handle is invalid
Jan 29 12:24:20 PM: Assertion failed at W:\Projects\SparkLabs\viscosity-windows\external-tools\openvpn\build\build64.tmp\openvpn-2.4.9\src\openvpn\tun.c:3434 (tt->cpHandle)
Jan 29 12:24:20 PM: State changed to Disconnected
Jan 29 12:24:20 PM: State changed to Disconnected

asdffdsa6131

Posts: 30
Joined: Sat Feb 23, 2019 12:15 pm

Post by asdffdsa6131 » Sat Jan 30, 2021 4:36 am
notice the unknown device which seems to be a viscosity device
device.manager.PNG
device.manager.PNG (86.29 KiB) Viewed 2479 times

asdffdsa6131

Posts: 30
Joined: Sat Feb 23, 2019 12:15 pm

Post by asdffdsa6131 » Sat Jan 30, 2021 8:17 am
hello,
since i cannot edit a previous post, i am not able to delete all of this post.

in the end, a corruption of comodo security seemed to be the problem.

if you did read this entire post, i apologize for the time wasted.

so far the tech support has been very good.

James

User avatar
Posts: 2102
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Sat Jan 30, 2021 8:40 am
Hi David,

Glad to hear you resolved the problem!
since i cannot edit a previous post, i am not able to delete all of this post.
I've gone ahead and removed all of your replies with potentially confidential connection information (such as your server's IP address). I'll leave the rest of the topic up as it may be of use to others who run into the same problem with Comodo's security software.

Cheers,
James
James Bekkema
Viscosity Developer

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

asdffdsa6131

Posts: 30
Joined: Sat Feb 23, 2019 12:15 pm

Post by asdffdsa6131 » Sun Jan 31, 2021 4:27 am
thanks much,

the strange thing is i have been using comodo for 10 years, on dozens of machines.
7 posts Page 1 of 1