C:\Program Files\TAP-Windows\driver\OemVista.inf.īy installing multiple times, you will create additional TAP-Windows adapter instances, which can be used for multiple concurrent VPN tunnels.
You need to specify the full path to this file, e.g. is typically OemWin2k.inf (old tap-drivers) or OemVista.inf (newer tap-drivers).refers to the driver identifier which is tap0901 for OpenVPN 2.2+, but may be different in older/newer OpenVPN versions.Updating drivers for from C:\Program Files\TAP-Windows\driver\OemVista.inf.
Install is complete when drivers are installed. View information about an installed driver:ĭevice node created. Below are some common commands you can run from an administrator Powershell or cmd.exe console: In this case you can use devcon.exe from the Windows command-prompt. Occasionally you may need play with different TAP-driver versions. This setting is persistent across reboots. Note also that the command line tool "netsh" can do many of these same functions.įor example, the following command will set the IP and subnet for my-tap: For the example below we will use an IP of 10.3.0.1 and a subnet mask of 255.255.255.0. Set the IP address and subnet mask of your new TAP device. Select Internet Protocol (TCP/IP) from the list and click on "Properties". Now right click again and select properties. Right click and rename this to something shorter and without embedded spaces such as "my-tap". You should see a "TAP-Windows Adapter" with a name like "Local Area Connection 3". On XP Go to Start -> Control Panel -> Network Connections. Manual configuration of the TAP-Windows adapter OpenVPN 2.3_rc2 installer does not install TAP utilities by default.