From Tunngle Wiki
Error 4-109: Could not initialize the Tunngle network adapter!
- The Tunngle client installation has failed.
- The Tunngle network adapter installation has failed.
- The adapter installation was manually aborted (see Windows Logo testing).
- An installed security software has blocked the adapter installation.
- An installed security software has prevented the setup from creating the new registry entries.
- An installed security software has blocked the access to the adapter.
- Your IP settings are corrupted.
- Your Windows user account doesn't have sufficient administration rights for the adapter installation.
- An obsolete Tunngle key is present in Windows Registry Virtual Store
- If Tunngle was working fine before and this is the first time that you get this issue, the best thing is to do nothing and attempt to restart your PC first. If you don't want to reboot, you can also Force Restart.
- If restarting doesn't work, you can right-click over My Computer, select properties then open the Device Manager and verify that the TAP-Win32 Adapter V9 (Tunngle) is installed under Network Adapters.
- If you can't find the device under Device Manager->Network Adapters or if the adapter is marked with a yellow warning sign you can try one of the following:
- If the adapter is installed, listed in device manager and working properly (no marks in it), we recommend that you properly configure exception for the Tunngle Executables in your security software (please note that some security software keeps interfering even if you disable it).
- You can also go to Windows->Start->Run->Regedit and check that there is no Tunngle key under: HKEY_USERS\<User SID>_Classes\VirtualStore\Machine\Software. If you find a Tunngle key you can try to delete it and restart Tunngle.
- If this fails please note that certain firewalls might require additional configuration. More info in the Troubleshooting section.
- If you still have issues you can try to check if you have any incompatible software installed.
- If you think that your IP settings might be corrupted you can try to check the last point of this section.
- We'd like to remind you that the installation requires administrator rights in order to be successful. If your Windows user account doesn't have enough rights, you can always start the Tunngle client setup by right clicking and selecting 'Run as administrator'.
- You can also try to install Tunngle from Windows Safe Boot mode
- If, before seeing this error, you get an empty adapter selection dialog please check that the SYSTEM account has Full Control permissions for the C:\Users\All Users\Tunngle (Win 7) or C:\Documents and Settings\All Users\Application Data\Tunngle (Win Xp) folder. To do this:
- Open the containing folder (e.g. C:\Users\All Users\ for Windows 7).
- Right-click over the Tunngle folder that appears in the list and select Properties.
- Open the Security Tab.
- If the SYSTEM user not there click Edit, Add, type SYSTEM inside the Enter the object names to select input-box and click OK.
- Select the SYSTEM user and tick the Allow column of the Full Control row.
- Click OK twice, uninstall, reboot, install, reboot Tunngle.
- Some members have reported that disabling and enabling back the Tunngle adapter from Network Connections before starting Tunngle might help in some cases.
- Some members have reported that they had to turn on Windows User Account Control (UAC) and uninstall, reboot, reinstall Tunngle before the adapter was properly recognized (more).
- Some members have reported that they solved the issue by right-clicking and running Tunngle.exe as administrator (although this is not required under normal circumstances it seems to help some persons with the issue).
- If you are running Windows 10 you can try to restart the DNS client service as suggested here.
- If you are running Windows 10 you can try to set the Tunngle Windows Network Location to private.
- If you are using a Wi-Fi connection, you can try to use cable for testing purposes. If it works please provide more details on the forum.
- If everything else fails please check the Broken Internet Security Suites section.