Hi, To recap, after installing and uninstalling TINC a number of times, TINC eventually wouldn't start. Debug gave a "".. not a usable Windows TAP Device.. File not found" error. After doing some digging, I found a dozen or so duplicate Network Adaptor bindings for the TAP driver in the Windows Registry. These were essentially orphaned entries as there was no corresponding Adaptor in "Network Connections" panel. I manually deleted these orphaned keys and then TINC was happy. I haven't found a reason why this situation exists but I did find a related article on MS Support site - http://support.microsoft.com/kb/899868 Tried putting some code together to try and "fix" this, but this didn't work. App received an "Access Denied" error even though I am running as Admin. Checked permissions, tried reboots, tried rebooting in Safe Mode etc., no luck. It appears that one cannot programmatically delete these keys using api calls ? Further searching found this article which offers a solution, though purist's may consider it messy :) - http://www.robvanderwoude.com/regedit.html
[part of post was cut off] ....
Graham Smith schrieb:> Hi, > > To recap, after installing and uninstalling TINC a number of times, TINC > eventually wouldn't start. > > Debug gave a "".. not a usable Windows TAP Device.. File not found" error. > > After doing some digging, I found a dozen or so duplicate Network Adaptor > bindings for the TAP driver in the Windows Registry. > > These were essentially orphaned entries as there was no corresponding > Adaptor in "Network Connections" panel. > > I manually deleted these orphaned keys and then TINC was happy. > > I haven't found a reason why this situation exists but I did find a related > article on MS Support site - http://support.microsoft.com/kb/899868Hi, 6 months ago I had the same problems. Before I discovered the duplicate entry's in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318} I found some other solution: Go to Start, Settings, Network Connections, right-click on your TAP Adapter and choose disable. Wait a few seconds and re-enable it. Now TINC works until the next reboot. I had even a script written that disabled and re-enabled my TAP-Adapter and then started TINC. Maybe this info helps someone to find the real source of the problem. Kind regards Andreas Weger
Hi Andreas, Thanks for your comments. Yeah, this is another of those "things that make you go mmmmm" Part of my original post was cut off for some reason (maybe too long :-), I have included it below. Kind regards Graham Smith>> >> From this article, I was able to create a utility that successfullyremoves these orphaned entries using a combination >> of api calls and .REG/Batch scripts.>> >> Conclusion, this is not a TINC or a TAP-Win32 issue. It is a Windowsissue.>> >> All Network Interfaces/Drivers that are installed under Windows willsuffer the same fate when uninstalled.