Open elise700 opened 9 years ago
Building kernel drivers with all the new driver signature requirements is an exercise in madness. I don't see any code signature issues in the above code, which is the usual culprit.
One question: did you change the PRODUCT_TAP_WIN_COMPONENT_ID value in version.m4? It should probably say
define([PRODUCT_TAP_WIN_COMPONENT_ID], [tavvetun])
Without that tapinstall.exe will fail.
I solved the problem and the biggest issue turned out to be that when you uninstall a windows driver and then recreate the drive and re-install it, the original driver was installed not the new one. I had to manually follow some steps to remove the original driver from the windows system files. After that it all worked ok. I don't remember the exact steps as it was almot 2 years ago.
Thanks for your suggestion.
@elise700 : out of curiosity: what process did you use to remove the driver's system files?
This link has the directions I used: https://technet.microsoft.com/en-us/library/cc730875.aspx
I actually implemented tap-windows removal tool in Powershell about a year ago, see https://github.com/mattock/tap-windows-scripts.
I have followed the directions to install a custom driver but it will not install.
At this point I would gladly contract out this work.
I am trying to build a custom tuntap driver. I followed the instructions and used buildtap.py to create a new 9.0.21 IPv6 supported driver. I then signed it. It was build on Windows 2012 and I am trying to install it on a different Windows 2012 server.
Trying to install, results in the below:
c:\tapinstall.exe install driver\OemVista.inf tavvetun
Device node created. Install is complete when drivers are installed... Updating drivers for tavvetun from C:\Users\gary\tuntap\driver\OemVista.inf. tapinstall.exe failed.
setupapi.dev look like the following: