TAP install failing on Windows 7

This forum is for all inquiries relating to the installation of OpenVPN from source and with binaries.

Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech

Forum rules
Please visit (and READ) the OpenVPN HowTo http://openvpn.net/howto prior to asking any questions in here!
lolo815
OpenVpn Newbie
Posts: 1
Joined: Sat Dec 14, 2013 12:20 pm

Re: TAP install failing on Windows 7

Post by lolo815 » Sat Dec 14, 2013 12:23 pm

Hi , I'm on windows 7 32 bits and therefore i can't use de unpacked Hotspot Shield that you posted. I can't find a 32 bits version neither. Please help me because i can't install the TAP driver for OpenVpn.

Thank for your comprehention.

sambul21
OpenVpn Newbie
Posts: 17
Joined: Wed Dec 04, 2013 6:08 pm

Re: TAP install failing on Windows 7

Post by sambul21 » Sun Dec 15, 2013 2:08 am

The above link for unpacked Hotspot Shield package contains both Anchorfree TAP drivers: OemWin2k.inf (64-bit) and OemWin2k_1.inf (32-bit). They were separated from a single driver by the unpacker.

You may want to post your log section with errors for OpenVPN TAP-Windows driver install here, since tapinstall.exe (devcon.exe) writes a log to c:\Windows\inf\setupapi.dev.log. Someone will suggest you the best approach, as this thread is devoted to the specific error:

Code: Select all

!!!  cci:                     NdisCoinst: NcipAllocateNetLuidIndex failed with error 0x5aa
     cci:                     [NdisCoinst: Exit NcipHandleInstallPreProcessing]
!!!  dvi:                CoInstaller 1: failed(0x000005aa)!
!!!  dvi:                Error 1450: Insufficient system resources exist to complete the requested service.
If your error is different, it may need a different cure: Debugging TAP installation problems.

If your error is the same, consider following this post. Note, IfUsedNetLuidIndices value hex:01 is default on a newly installed Windows. Since most users never exceed maximum number of adapters allowed (once fake adapters are deleted from Registry by the above MS fix), you might get away with the default value on most PCs. Or use hex:0xFF 0x01 , if you have a typical number of 9 adapters. Here is the reprint (message 2), what may be affected by this value:

"NDIS must allocate a (locally) unique number for each network interface, the NET_LUID. The NET_LUID consists of the ifType, paired with a unique ID number.
To generate that unique ID, we keep track of the IDs that have already been
assigned in

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NDIS\IfTypes\[ifType] !
IfUsedNetLuidIndices (REG_BINARY) for each ifType. For example, look in \6 if your NIC is Ethernet (ifType=3D=6).

In there, there is IfUsedNetLuidIndices, which is (IIRC) a bitmap of the unique IDs that have been assigned to other network interfaces. Make sure this value is present and not damaged (e.g., a huge number of 0xFF's). Typically, its value will be something like 0xFF 0x01, if you have 9 NICs. Note that you can't just whack this value and replace it with something else, since then NDIS will incorrectly assign the same NET_LUID to two interfaces, and all sorts of things will break when that happens.

sambul21
OpenVpn Newbie
Posts: 17
Joined: Wed Dec 04, 2013 6:08 pm

Re: TAP install failing on Windows 7

Post by sambul21 » Sun Dec 15, 2013 2:37 am

To add, if IfUsedNetLuidIndices value for a certain IfType adapter is broken, Windows code to calculate that value might also be broken, so it might remain unchanged anyway (was in my case), when you add new adapters of the same IfType. But it doesn't mean, they all be assigned the same IDs - its highly unlikely.

Also, you can simply delete the IfType adapter key, for which IfUsedNetLuidIndices value is broken, then run the above MS Fix, and then reinstall TAP-Windows driver again. You may need to reinstall other adapters & drivers of the same IfType, if any were previously installed - just check them all in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NDIS\IfTypes\[ifType] key before deleting it.

bnohue
OpenVpn Newbie
Posts: 2
Joined: Wed Apr 04, 2012 3:13 pm

Re: TAP install failing on Windows 7

Post by bnohue » Sun Dec 15, 2013 8:05 am

May be you want to take a look on the driver installers and drivers inside?
tap files

sambul21
OpenVpn Newbie
Posts: 17
Joined: Wed Dec 04, 2013 6:08 pm

Re: TAP install failing on Windows 7

Post by sambul21 » Mon Dec 16, 2013 2:43 am

Instead of deleting the broken NDIS IfType adapters summary key, you may want to look first through all subkeys in the related Registry key, which lists your PC network connections of that IfType, like HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}. If you see multiple subkeys with connections you don't recognize, consider deleting them. Then run the above MS Fix, which ideally should fix your broken IfUsedNetLuidIndices value for the broken IfType adapters key.

Lenchanteurmerlin
OpenVpn Newbie
Posts: 1
Joined: Tue Feb 11, 2014 4:02 pm

Re: TAP install failing on Windows 7

Post by Lenchanteurmerlin » Tue Feb 11, 2014 4:10 pm

Firts I have to say that I am impressed by Stambul 21. Second that I have tried everything suggested here and elsewhere and nothing works.

I can also compare register shots taken when I reinstalled W7 Ultimate and taken now and none of the reg entries suspected have changed (in fact my If UsedNetLuiIndexes always was at 0). I have even disconnected my antivirus (avast free) and it does not help. Team Viewer works, Expat Shield works, but Cyberghost, OpenVPN in whatever form don't. The Tap Win32 992 error.

Where else do you think I should look?
Thank you.

harrysnorlax
OpenVpn Newbie
Posts: 1
Joined: Mon Nov 17, 2014 12:14 am

Re: TAP install failing on Windows 7

Post by harrysnorlax » Mon Nov 17, 2014 12:38 am

Thank you for the helpful discussion.

In case another user stumbles upon this thread trying to solve the same problem - Error 1450, insufficient resources - I found a different workaround that will let you install the driver.

Disclaimer: This is probably not the best/smartest way to do this, but it is very simple.

Instead of installing the drives as an ifType(other), install it as another ifType, e.g. ifType(ethernet). To do this is fairly simple and only requires adding one line to your inf file.
  • -Open your OemWin2k.inf or OemWin2k_1.inf (32-bit) file in a text editor.
    -Add the line "*IfType = 6" to the driver section of the file.
    -Save.
Your new inf file should look like:

Code: Select all

;---------------------------------------------------------------
;                             Driver Section (Done)
;---------------------------------------------------------------

;----------------- Characteristics ------------
;    NCF_PHYSICAL = 0x04
;    NCF_VIRTUAL = 0x01
;    NCF_SOFTWARE_ENUMERATED = 0x02
;    NCF_HIDDEN = 0x08
;    NCF_NO_SERVICE = 0x10
;    NCF_HAS_UI = 0x80
;----------------- Characteristics ------------

[tap0901.ndi]
   *IfType         = 6;   IF_TYPE_ETHERNET_CSMACD 
   CopyFiles       = tap0901.driver, tap0901.files
   AddReg          = tap0901.reg
   AddReg          = tap0901.params.reg
   Characteristics = 0x81

[tap0901.ndi.Services]
   AddService = tap0901,        2, tap0901.service

[tap0901.reg]
   HKR, Ndi,            Service,      0, "tap0901"
   HKR, Ndi\Interfaces, UpperRange,   0, "ndis5"
   HKR, Ndi\Interfaces, LowerRange,   0, "ethernet"
   HKR, ,               Manufacturer, 0, "%Provider%"
   HKR, ,               ProductName,  0, "%DeviceDescription%"

[tap0901.params.reg]
   HKR, Ndi\params\MTU,                  ParamDesc, 0, "MTU"
   HKR, Ndi\params\MTU,                  Type,      0, "int"
   HKR, Ndi\params\MTU,                  Default,   0, "1500"
   HKR, Ndi\params\MTU,                  Optional,  0, "0"
   HKR, Ndi\params\MTU,                  Min,       0, "100"
   HKR, Ndi\params\MTU,                  Max,       0, "1500"
   HKR, Ndi\params\MTU,                  Step,      0, "1"
   HKR, Ndi\params\MediaStatus,          ParamDesc, 0, "Media Status"
   HKR, Ndi\params\MediaStatus,          Type,      0, "enum"
   HKR, Ndi\params\MediaStatus,          Default,   0, "0"
   HKR, Ndi\params\MediaStatus,          Optional,  0, "0"
   HKR, Ndi\params\MediaStatus\enum,     "0",       0, "Application Controlled"
   HKR, Ndi\params\MediaStatus\enum,     "1",       0, "Always Connected"
   HKR, Ndi\params\MAC,                  ParamDesc, 0, "MAC Address"
   HKR, Ndi\params\MAC,                  Type,      0, "edit"
   HKR, Ndi\params\MAC,                  Optional,  0, "1"
   HKR, Ndi\params\AllowNonAdmin,        ParamDesc, 0, "Non-Admin Access"
   HKR, Ndi\params\AllowNonAdmin,        Type,      0, "enum"
   HKR, Ndi\params\AllowNonAdmin,        Default,   0, "1"
   HKR, Ndi\params\AllowNonAdmin,        Optional,  0, "0"
   HKR, Ndi\params\AllowNonAdmin\enum,   "0",       0, "Not Allowed"
   HKR, Ndi\params\AllowNonAdmin\enum,   "1",       0, "Allowed"
After this you should be able to install the driver with devcon.exe, or the installer, without any issues. Hopefully this helps the next person who runs into this problem.

Post Reply