An Error Occurred Installing The Tap-win32 Device Driver Vista
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 29 Sep 2016 21:47:10 GMT by s_hv972 (squid/3.5.20)
Defect (worksforme) Error occured installing tap device driver Reported by: FrancoisC Owned by: samuli Priority: major Milestone: release 2.3.6 Component: tap-windows Version: 2.3-beta / 2.3-RC Severity: Not set (if unsure, select this one) an error occurred installing tap-win32 device driver Keywords: tap window error Cc: Description Hi, I've been digging into tapinstall install returned 2 cyberoam some similar reports and blogs, but none of them have solved my problem. While installing OpenVPN 2.3.3 cyberoam tap-win32 error 64 bit version on a Windows 7 laptop, I get this (seemed to be famous) error message: "An error occured installing tap device driver" I've looked at bu report http://answers.microsoft.com/en-us/windows/forum/windows_vista-hardware/error-while-installing-driver/b16cb444-0e32-49ac-a1c9-958cc02a0b6c #266, and tried a few things: replace devcon.exe with the 64 bit version from http://www.ryanvictory.com/posts/automating-6to4-adapter-removal-in-windows/ uninstall the all thing and reinstall a 32 bit version uninstall and install an older version 2.3.2 install the standalone tap-windows-9.9.2_3 All gave me the exact same error. Also, calling the addtap.bat script in admin mode give me the following error: C:\Windows\system32>rem Add https://community.openvpn.net/openvpn/ticket/393 a new TAP virtual ethernet adapter C:\Windows\system32>"C:\Program Files\TAP-Windows\bin\devcon.exe" install "C:\Pr ogram Files\TAP-Windows\driver\OemWin2k.inf" tap0901 Device node created. Install is complete when drivers are installed... Updating drivers for tap0901 from C:\Program Files\TAP-Windows\driver\OemWin2k.i nf. devcon.exe failed. C:\Windows\system32>pause I've seen on report #266 there might be an issue with VMWare being installed. It is my case. But it's not clear from this report this is really an issue or if there is a workaround. Anyone has a clear, comprehensive, working solution or workaround ? Regards François Oldest first Newest first Threaded Comments only Change History (7) comment:1 Changed 2 years ago by francoisC Any update, help would be appreciated. Regards François comment:2 Changed 2 years ago by cron2 Owner set to samuli Status changed from new to assigned Anything in the system logs when this happens? Samuli, any ideas where to look? (I'm inclined to classify this as "something is weird with the laptop in question" as it worked for all my test cases on Win7, but since this is happening every now and t
to install the PIA software on the public release of Windows 10 Pro, 64 bit.I'm currently running build 10240 and it is fully updated.To date, working with PIA support Brendon T https://www.privateinternetaccess.com/forum/discussion/18340/windows-10-pro-final-release-tap-driver-installation-failure and Will BFirst I installed the PIA software per the instructions on the website. The original installation seemed to work fine, but I discovered after trying to connect that the TAP driver wasn't installed correctly. I immediately contacted support and got a case going. While discussing my setup with the tech, he suggested some changes to my anti-virus (Kaspersky) which I did. I use a Zywall USG50 hardware firewall, so an error I have both the Kaspersky and Windows firewalls disabled, but I did put in the exceptions into the application scanning, etc, that were suggested.Trying to reinstall the TAP driver from the start menu as an administrator was the first step. It failed (it takes approximately 4 minutes every time, btw). It just times out, and then you get a popup saying it failed. Each time you install, either PIA installer an error occurred in the command window, or with the OpenVPN installer, it gives you a notice that you may need confirmation ...but there is no popup or anything for approval at any point, so this may also be one of the issues.I then tried going to the device manager, which shows the driver in Other Devices, and tried updating from there. It also times out.PIA support requested a copy of the setupapi.dev.log, which I sent them, and we both continued to research the problem. Will B discovered that it seems that Windows 10 is handling driver signing differently than windows had in the past, so we tried rebooting with Driver Signature Enforcement disabled, and tried again. It continued to fail.Next, we tried downloading the 64 bit version of OpenVPN for post Vista versions of Windows, and installing just the TAP driver, again with DSE disabled. It failed again.In checking through problems with earlier builds of Windows 10, prior to the public release, it turns out there should be a registry entry for the Tap Adapter at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\[00XX] (XX being the adapter number, which varies by your particular setup. In my case, it's 14). The fix for previous versions had been to do the following: add string value/data ComponentId/tap0901(REG_SZ) with regeditvalue name=Com