MSI (s) (58:10) : Executing op: CustomActionSchedule(Action=InstallTUNTAPAdapters,ActionType=3073,Source=BinaryData,Target=ProcessDeferredAction,CustomActionData=x create="OpenVPN Wintun|Wintun" create="OpenVPN TAP-Windows6|root\tap0901") MSI (s) (58:10) : Executing op: ActionStart(Name=InstallTUNTAPAdapters,Description=Creating TUN/TAP adapters,Template=: )Īction 22.01.49: InstallTUNTAPAdapters. MSI (s) (58:10) : Executing op: CustomActionSchedule(Action=InstallTUNTAPAdaptersRollback,ActionType=3329,Source=BinaryData,Target=ProcessDeferredAction,CustomActionData=x) MSI (s) (58:10) : Executing op: ActionStart(Name=InstallTUNTAPAdaptersRollback,)Īction 22.01.49: InstallTUNTAPAdaptersRollback. Perhaps this is at the root of the problems? Looks like both Wintun and tap-windows6 get registered to ROOT\NET\0000. in Control panel) I see references to wintun as well. One interesting possibly related issue is that when looking at adapter events for TAP-Windows (e.g. So netsh is probably somehow to blame here.
#OPENVPN TAP DRIVER NOT INSTALLING DRIVERS#
The failure happens after the drivers have been installed to the driver store, i.e. Wintun installation fails consistently with the original error message, even if starting from (apparently) clean state, that is after having removed all traces of OpenVPN, registry keys (above) and drivers from the driver store. If the "wintun" feature is disabled then installation of OpenVPN + tap-windows6 succeeds consistently. These keys thus seem to be metadata for"installed programs" or the installers themselves. On a successful uninstallation the registry key(s) are removed. If a feature is disabled the registry key is not added. PSParentPath : \Registry::HKEY_LOCAL_MACHINE\software PSPath : \Registry::HKEY_LOCAL_MACHINE\software\tap0901 PS HKLM:\SOFTWARE> get-itemproperty tap0901 It also happens during upgrades (beta1->beta2). The problem manifests itself even if no tap-windows6 adapters are installed or in driver store. MSI (s) (7C:90) : Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=,CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: ) MSI (s) (7C:90) : Executing op: DialogInfo(Type=1,Argument=OpenVPN) MSI (s) (7C:90) : Executing op: DialogInfo(Type=0,Argument=1033) MSI (s) (7C:90) : Machine policy value 'DisableRollback' is 0
![openvpn tap driver not installing openvpn tap driver not installing](https://www.vpnlux.com/i/instructions/wxp_ovpnp_en_05.jpg)
MSI (s) (7C:90) : User policy value 'DisableRollback' is 0
#OPENVPN TAP DRIVER NOT INSTALLING CODE#
OpenVPNMSICA: tap_set_adapter_name: Error renaming adapter Error 1: Funktio ei kelpaa.ĬustomAction InstallTUNTAPAdapters returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)Īction ended 12.05.18: InstallExecute. OpenVPNMSICA: tap_set_adapter_name: Error renaming adapter Error 1: Funktio ei kelpaa. MSI (s) (7C:90) : Executing op: ActionStart(Name=InstallTUNTAPAdapters,Description=Creating TUN/TAP adapters,Template=: )Įrs: Creating adapter: OpenVPN Wintun WintunĮrror 2551. MSI (s) (7C:90) : Executing op: CustomActionSchedule(Action=InstallTUNTAPAdaptersRollback,ActionType=3329,Source=BinaryData,Target=ProcessDeferredAction,CustomActionData=x) MSI (s) (7C:90) : Executing op: ActionStart(Name=InstallTUNTAPAdaptersRollback,)Īction 12.05.08: InstallTUNTAPAdaptersRollback. WriteRegistryValues: Key: \SOFTWARE\Wintun, Name:, Value: #1 WriteRegistryValues: Key: \SOFTWARE\tap0901, Name:, Value: #1
![openvpn tap driver not installing openvpn tap driver not installing](https://winerrorfixer.com/wp-content/uploads/2019/10/TAP-Windows-Adapter-V9.jpg)
MSI (s) (7C:90) : Executing op: RegAddValue(,Value=#1,) WriteRegistryValues: Key: \Software\OpenVPN, Name: priority, Value: NORMAL_PRIORITY_CLASS