There is a script to do this, but it only works if you have not changed the text strings in your driver package Key step: The driver needs to be removed from the driver store also. now, only re-installs the old driver that was copied into the driver store.
The command tapinstall remove TAP0901 - removes the driver.Updating the Driver, and the Windows Driver Store:Īt some point, you will build a shinny new driver and need to test it. As a result, the driver will be copied into the Windows Driver Store.
Because your driver is not signed, the tapinstall install step will pop up the "Big Scary Unsigned Driver Warning", you'll need to click OK.The command tapinstall install OemVista.inf TAP0901 installs the driver.The result should be Test Mode in the bottom right corner of the windows screen.Specifically, bcdedit /set testsigning off or bcdedit /set testsigning on.Virtual Box: SecureBoot is not supported on Virtual Box.Secure Boot: Varies depending on PC Maker and/or the BIOS setting on your test machine.
Unsigned drivers require disabling secure boot. If you are actively developing the driver (e.g.: Edit, Compile, Debug, Loop.), you may not be signing your driver each time, thus you need to be aware of the following additional items. cd to amd64, i386, or arm64 depending on your system's processor architecture.place tapinstall.exe/devcon.exe to your PATH.Tap-windows NDIS 6 driver follow these steps: OpenVPN tapinstall.exe is called devcon.exe. The driver can be installed using a command-line tool, tapinstall.exe, which isīundled with OpenVPN and tap-windows installers. Developer Mode: Installing, Removing and Replacing the Driver Will get wiped before MakeNSIS is able to find them. Also don't use the "-c" flag or the above directories Please note that the NSIS packaging (-p) step will fail if you don't have Replace "Release" with your build configuration įor example, when using -Hlk you'd use "Hlk". This structure is equal to what building tapinstall would create. To make sure the buildsystem finds the executables, create the followingĭirectory structure under tap-windows6 directory: devcon The build system also supports reuse of pre-built tapinstall.exe executables. $ Copy-Item -Recurse Windows-driver-samples/setup/devcon tap-windows6 The easiest way to build tapinstall is to clone the Microsoft driver samplesĪnd copy the source for devcon.exe into the tap-windows6 tree. The NSIS installer package will be placed to On successful completion, all build products will be placed in the "dist"ĭirectory as well as. timestamp=URL Timestamp URL to use, default=Įdit version.m4 and paths.py as necessary then build: $ python buildtap.py -b
crosscert=CERT The cross-certificate file to use, default=MSCV. certpw=CERTPW Password for the code signing certificate/key certfile=CERTFILE Path to the code signing certificate cert=CERT Common name of code signing certificate, m, -package-msm generate a MSM installer from the compiled files p, -package generate an NSIS installer from the compiled files sdk=SDK SDK to use for building: ewdk or wdk, default=ewdk b, -build build TAP-Windows and possibly tapinstall (add -c to c, -clean do an nmake clean before build hlk build for HLK tests (test sign, no debug) s SRC, -src=SRC TAP-Windows top-level directory, default= h, -help show this help message and exit View build script options: $ python buildtap.py
Tap-windows6 has been successfully build on Windows 10 and Windows Server 2016 using Make sure you add Python's install directory (usually c:\python27) to the PATH