Same problem here. I had this problem a couple times in the past and was always able to solve it. This time I am not. The driver installs but there is a signature problem (Code 52, little yellow exclamation mark in device manager). Thus the driver does not start and there is no tap device.

I tried to uninstall old versions, clean the registry, removed suspicious 3rd party software and so on. No success....

Yes I agree! It is possible to correctly install the TAP driver by disabling driver signature enforcement (solution 1). BUT you also have to disable secure boot in the UEFI BIOS settings of your computer to make it work permanently after reboot. This in turn means that bitlocker drive encrypton does only work if you are willing to type in your 40 digit key on every boot which is unacceptable. Turning off bitlocker on a business notebook is also unacceptable.

So please dear developers fix the signining issues. Unfortunately I do not know how to do it myself....

If it gives any clues, the publisher in the 'Programs & Features' control panel item shows up incorrectly. Perhaps this flows through the driver publisher too giving rise to the signature error? It shows up at ${PRODUCT_PUBLISHER}, not OpenVPN, Inc. as you would expect.

The PRODUCT_PUBLISHER thing is a separate problem. I've create new Windows installers which bundle the old tap-windows6 version. This is an interim solution while figuring out how to make MS sign the driver.

I'm experiencing the same issue. Windows 10 1803 and installing tap-windows6 9.21.2. This started 3 days ago. Have tried all the options spoken above, and also, tried uninstalling TAP driver, and removing it from the registry. Still no change.

I'm experiencing the same issue. Windows 10 1803 and installing tap-windows6 9.21.2. This started 3 days ago. Have tried all the options spoken above, and also, tried uninstalling TAP driver, and removing it from the registry. Still no change.

ghost887 did you fix the problem? It started for me about a week ago.

None of the fixes in this thread, or others I tried from other forums, worked for me.