Page 1 of 1

Windows 7 Tap-Win32 Adapter V9 conflict. Please Help! Help!!

Posted: Fri Sep 30, 2011 7:53 am
by faxonet
This is the correct post...please ignore 2nd post above. Thank you.

Upon installing a Linksys router WRT160N at home on 2 pc network, I noticed a device conflict error (under Network Devices) in my TAP-Win32 Adapter V9. The driver was signed by OpenVPN technologies.

I cannot determine how to correct this device conflict error (small yellow triangle beside this device symbol in Device Manager), and ask for any expert help.

Is it a matter of a driver? Went to OpenVPN and saw numerous .exe packages with OpenGUI interfaces that advise to enter a portal upon configuring and I am unsure this is my solution.

Can anyone help?

It's a Windows 7 Final Release Build 7600. I had updated thefirmware on my router to 2.0.3 to hopefully address Win7 issues if any.

Is this a matter of a driver update or the settings of Home/Private/Public in Network system settings. Please forgive my ignorance and lack of technical knowledge. Would appreciate assistance.

Can I just delete the device in Device Manager? How do I delete it? Don't see that option. Do I disable? (Thanks for that suggestion ab poster).

I see that the driver for the conflict is OpenVPN Technologies. Is this a matter of a driver? I saw the driver download packages at Open VPN but they seem to install an entire program and I would have to use that program for a VPN. I do not know what a VPN is, how to use it or why I would need to. The router I installed seems to be working and I am able to connect to the internet from both networked PCs.

But I do not want a conflicted device. Has anyone ever seen this, know what is happening, what a Tap-Win32 Adapter V9 is and if this must be fixed. Or can I leave it be? Thanks for your help. Very worried as it is a new pc. And there was no conflict until the router was installed.

Device Manager pic...

Image

Re: Windows 7 Tap-Win32 Adapter V9 conflict. Please Help! He

Posted: Fri Sep 30, 2011 8:11 am
by janjust
which version of OpenVPN did this tap-win32 come out of? download openvpn 2.2.1 and install it - anything before 2.1.0 (tap-win32 driver v9.3 IIRC) is not compatible with Win7.

Re: Windows 7 Tap-Win32 Adapter V9 conflict. Please Help! He

Posted: Fri Sep 30, 2011 6:22 pm
by faxonet
Thank you JanJust for the reply. Downloaded s you said. Could not find any information on OpenVpn from an earlier, alreay installed version. I assume I had whatever comes standard on Win7.

Well, downloaded and installed. Went through help file. Could not see option to place certificate in specific OpenVpn config file. But installed certificate in default file. Attempted to update my driver to driver in folder of OpenVPN and it said old driver was correct version. New driver was same as preinstalled Win7 earlier driver with conflict. Problem must be something else.

After installing 2.2.1 .exe OpenVpn and starting GUI as administrator (but do not see program running??? invisible??), I checked Device Manager and still have conflict. So I uninstalled OpenVPN (did not see it as solution or know what it does).

On restart, there is no TAP-Win32 Adapter V9 on system any longer? Check network and ran "net view" from cmd line on both pcs and they are "on network". So seems I lost adapter but everything works. Is this normal? No need for OpenVPN? Should I do system restore back to original or reload OpenVPN and levae device conflict?

Please assist. You folks are much more intelligent. Apologize for low tech savvy. Help greatly appreciated. Perhaps the Device Conflict error was just a virtual entry as result of router install and served no purpose and causes no harm. Input?

Here is pic with device gone....

Image

Re: Windows 7 Tap-Win32 Adapter V9 conflict. Please Help! He

Posted: Fri Sep 30, 2011 9:01 pm
by janjust
what happens if you run 'tap-install' (from the OpenVPN start menu entries) ? does the driver install at all? there are some reports of people having problems to install the driver in the first place...

PS I respond infrequently to private messages - you were lucky this time :mrgreen: