You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Commit 2ab5e88 introduced a 'g' before the definition of PRODUCT_TAP_WIN_CHARACTERISTICS in version.m4, which doesn't match the regex in buildtap.py's BuildTAPWindows.parse_version_m4 method. Consequently, the generated INF describes the characteristics of the device as "" (the empty string), which erroneously becomes a 0 in the registry, rather than the correct value of 0x81 (NCF_VIRTUAL | NCF_HAS_UI).
The text was updated successfully, but these errors were encountered:
We're in the process of getting an EV code-signing certificate for signing the tap-windows6 driver. Once that is taken care of, we can fix this bug and rebuild. If we did publish a new driver now, it will not (afaik) work on Windows 10, because of Microsoft's new driver signing policy.
Commit 2ab5e88 introduced a 'g' before the definition of PRODUCT_TAP_WIN_CHARACTERISTICS in version.m4, which doesn't match the regex in buildtap.py's BuildTAPWindows.parse_version_m4 method. Consequently, the generated INF describes the characteristics of the device as "" (the empty string), which erroneously becomes a 0 in the registry, rather than the correct value of 0x81 (NCF_VIRTUAL | NCF_HAS_UI).
The text was updated successfully, but these errors were encountered: