TAP dancing with x64

It appears that some installations of vista act inconsistently in their kernel-level driver installation behaviors. Is it the user who has an IDS system that silently blocks the installation of low level drivers? Could it be an anti-rootkit software that sees and censors TAP drivers? Whatever the case, it appears that the user having UAC disabled, or being the administrator himself, is unable to thoroughly convince x64 that things are running appropriately.

The question is 'how to we fix that?'... first we must figure out what is causing it to behave inconsistently. It is either the user, legitimate programs, illegitimate programs, or the operating system itself. Because it works for some users and not others we are inclined to think it is not the operating system itself.

We're going to investigate what is going on with OpenVPN and x64, and other conflicting softwares. Particularly VMWare and other virtualized TAP/TUN drivers. Over the next couple months, we will be focusing on the problems in OpenVPN GUI/driver implementations, particularly in windows, and see if we can design a cross-compatible software to avoid the hassle of OpenVPN GUI and Tunnelblick. We will also be patching a security hole we found in OpenVPN GUI, while we are under the hood.

Wish us luck!

Update: x64 drivers appear to be solved!