If you’ve ever used a VPN service on desktop then you’ve probably come across the term TAP Adapter. Unfortunately, you’re most likely to have seen it in some unhelpful error message.
Whether it’s ‘All Windows TAP adapters in use’, ‘No TAP adapter available’, or ‘An error occurred installing the TAP device driver’, there’s often a TAP problem somewhere with your name on it!
And the messages usually give you little or no advice on how to figure out the problem, either, so the best you can do is pop them into a search engine and see what comes up.
But this isn’t quite as bad as it seems. In this article, we’ll explain what TAP adapters are, what they’re for and why they matter when you’re running a Windows 10 VPN on PC. And once you understand just some of the background, you’ll find you can fix most TAP issues very quickly.
Do I have a TAP adapter?
A TAP adapter is a software-based network device which allows a VPN to securely communicate with its servers. It’s such a fundamental component that if the TAP adapter isn’t installed or working then some VPNs won’t work at all, resulting in all those pesky error messages you know so well.
TAP adapters come in many different flavors, which can make life confusing. Some VPNs install a plain, ordinary, generic TAP adapter, but others have specially patched ones which only work with their own service. You might even have two or more versions installed at the same time.
To check your setup, click start, type DEVMGMT.MSC and press Enter to launch Device Manager.
Click the arrowhead to the left of Network Adapters to expand the tree, and look down the list of adapters. If you see ‘TAP-Windows Adapter V9’ then you have the generic TAP adapter installed.
But custom versions often have the VPN name included, too, like ‘TAP-NordVPN Windows Adapter V9.’ if you’re a NordVPN user. If you’re unsure, double-click a driver, click the Driver tab, then Driver Details: if the Provider or Copyright mentions OpenVPN then it’s probably a TAP adapter.
Multiple TAP adapters
Having two or more TAP adapters installed can sometimes cause problems, especially if you’ve also installed more than one VPN. One VPN app might try to use an adapter belonging to another VPN, for instance, leaving the second app to complain that there are no adapters available.
VPN providers recognize that this is a problem, and some apps include an option to ‘repair’ the TAP adapter, restoring its regular settings to help the app find it again. In the IPVanish Windows app, for instance, click Settings, Connection, and you’ll find an Install/ Repair OpenVPN Driver option which could solve the problem.
You can also try resetting a TAP adapter by disabling and enabling it, the software equivalent of turning it off and on again. Right-click your VPN’s TAP adapter in Device Manager that you found earlier, choose Disable Device, and click Yes when you’re asked to confirm that. Wait a few seconds, right-click Enable Device, reboot your PC and try connecting to the VPN again.
Uninstall and reinstall a TAP adapter
Most VPN apps automatically install a TAP adapter with their own files, so reinstalling the app often fixes any TAP issues.
Click Start, type and launch Control Panel, then click Programs, Uninstall a Program. Find the entry for your Windows VPN app, click it and select Uninstall.
Sometimes there’s a second item representing the TAP adapter, something like ‘MyVPNName network TAP’. If it’s still there, uninstall that, too.
Reboot, then download and install the latest app. Reboot again, launch the app, and see if you have any more connection success.
If you have two or more VPNs installed, we’d recommend uninstalling any that you don’t really need, to reduce the chance of conflicts. Even if you absolutely must run a couple of VPNs side-by-side, for some reason, uninstall one of them temporarily to see if that fixes the problem.
(opens in new tab)
More TAP tricks
Stubborn TAP adapter problems can be due to leftovers from a previous installation. We’ve previously been unable to install a new TAP adapter because it was blocked by a previous, damaged version, for instance.
If you really know what you’re doing, follow our guide on how to completely uninstall a VPN (particularly the Network Adaptors and System Drivers sections) to clean up any old VPN files and settings. But be careful: messing up here can damage your PC, so don’t even think of it unless you’re confident in your disaster recovery abilities.
If you still can’t solve your problem, it’s possible you can bypass it. Disable the NordVPN TAP adapter, for instance, and its app can’t connect via OpenVPN. But switch to the NordLynx protocol (click Settings, Auto-connect, choose NordLynx from the VPN Protocol list) and it should work again.
That kind of quick fix isn’t a great choice, because if a VPN app is displaying errors and you don’t know exactly why, then it may be reliably protecting you any more (there might also be encryption issues, say.) But it should keep you running for a while, if that’s the priority.
After all your hard troubleshooting work, though, the best idea is to contact your VPN support team and ask for help. Tell them everything you’ve tried so far, and they should be able to point you in the right direction.
Read more:
- Get protected online for less with a great cheap VPN…
- …and with market-leading antivirus software
- Stop logging of your PC activities with our Windows 10 privacy guide
Sign up to theTechRadar Pro newsletter to get all the top news, opinion, features and guidance your business needs to succeed!
Mike is a lead security reviewer at Future, where he stress-tests VPNs, antivirus and more to find out which services are sure to keep you safe, and which are best avoided. Mike began his career as a lead software developer in the engineering world, where his creations were used by big-name companies from Rolls Royce to British Nuclear Fuels and British Aerospace. The early PC viruses caught Mike’s attention, and he developed an interest in analyzing malware, and learning the low-level technical details of how Windows and network security work under the hood.
If you’ve ever used a VPN service on desktop then you’ve probably come across the term TAP Adapter. Unfortunately, you’re most likely to have seen it in some unhelpful error message.
Whether it’s ‘All Windows TAP adapters in use’, ‘No TAP adapter available’, or ‘An error occurred installing the TAP device driver’, there’s often a TAP problem somewhere with your name on it!
And the messages usually give you little or no advice on how to figure out the problem, either, so the best you can do is pop them into a search engine and see what comes up.
But this isn’t quite as bad as it seems. In this article, we’ll explain what TAP adapters are, what they’re for and why they matter when you’re running a Windows 10 VPN on PC. And once you understand just some of the background, you’ll find you can fix most TAP issues very quickly.
Do I have a TAP adapter?
A TAP adapter is a software-based network device which allows a VPN to securely communicate with its servers. It’s such a fundamental component that if the TAP adapter isn’t installed or working then some VPNs won’t work at all, resulting in all those pesky error messages you know so well.
TAP adapters come in many different flavors, which can make life confusing. Some VPNs install a plain, ordinary, generic TAP adapter, but others have specially patched ones which only work with their own service. You might even have two or more versions installed at the same time.
To check your setup, click start, type DEVMGMT.MSC and press Enter to launch Device Manager.
Click the arrowhead to the left of Network Adapters to expand the tree, and look down the list of adapters. If you see ‘TAP-Windows Adapter V9’ then you have the generic TAP adapter installed.
But custom versions often have the VPN name included, too, like ‘TAP-NordVPN Windows Adapter V9.’ if you’re a NordVPN user. If you’re unsure, double-click a driver, click the Driver tab, then Driver Details: if the Provider or Copyright mentions OpenVPN then it’s probably a TAP adapter.
Multiple TAP adapters
Having two or more TAP adapters installed can sometimes cause problems, especially if you’ve also installed more than one VPN. One VPN app might try to use an adapter belonging to another VPN, for instance, leaving the second app to complain that there are no adapters available.
VPN providers recognize that this is a problem, and some apps include an option to ‘repair’ the TAP adapter, restoring its regular settings to help the app find it again. In the IPVanish Windows app, for instance, click Settings, Connection, and you’ll find an Install/ Repair OpenVPN Driver option which could solve the problem.
You can also try resetting a TAP adapter by disabling and enabling it, the software equivalent of turning it off and on again. Right-click your VPN’s TAP adapter in Device Manager that you found earlier, choose Disable Device, and click Yes when you’re asked to confirm that. Wait a few seconds, right-click Enable Device, reboot your PC and try connecting to the VPN again.
Uninstall and reinstall a TAP adapter
Most VPN apps automatically install a TAP adapter with their own files, so reinstalling the app often fixes any TAP issues.
Click Start, type and launch Control Panel, then click Programs, Uninstall a Program. Find the entry for your Windows VPN app, click it and select Uninstall.
Sometimes there’s a second item representing the TAP adapter, something like ‘MyVPNName network TAP’. If it’s still there, uninstall that, too.
Reboot, then download and install the latest app. Reboot again, launch the app, and see if you have any more connection success.
If you have two or more VPNs installed, we’d recommend uninstalling any that you don’t really need, to reduce the chance of conflicts. Even if you absolutely must run a couple of VPNs side-by-side, for some reason, uninstall one of them temporarily to see if that fixes the problem.
(opens in new tab)
More TAP tricks
Stubborn TAP adapter problems can be due to leftovers from a previous installation. We’ve previously been unable to install a new TAP adapter because it was blocked by a previous, damaged version, for instance.
If you really know what you’re doing, follow our guide on how to completely uninstall a VPN (particularly the Network Adaptors and System Drivers sections) to clean up any old VPN files and settings. But be careful: messing up here can damage your PC, so don’t even think of it unless you’re confident in your disaster recovery abilities.
If you still can’t solve your problem, it’s possible you can bypass it. Disable the NordVPN TAP adapter, for instance, and its app can’t connect via OpenVPN. But switch to the NordLynx protocol (click Settings, Auto-connect, choose NordLynx from the VPN Protocol list) and it should work again.
That kind of quick fix isn’t a great choice, because if a VPN app is displaying errors and you don’t know exactly why, then it may be reliably protecting you any more (there might also be encryption issues, say.) But it should keep you running for a while, if that’s the priority.
After all your hard troubleshooting work, though, the best idea is to contact your VPN support team and ask for help. Tell them everything you’ve tried so far, and they should be able to point you in the right direction.
Read more:
- Get protected online for less with a great cheap VPN…
- …and with market-leading antivirus software
- Stop logging of your PC activities with our Windows 10 privacy guide
Sign up to theTechRadar Pro newsletter to get all the top news, opinion, features and guidance your business needs to succeed!
Mike is a lead security reviewer at Future, where he stress-tests VPNs, antivirus and more to find out which services are sure to keep you safe, and which are best avoided. Mike began his career as a lead software developer in the engineering world, where his creations were used by big-name companies from Rolls Royce to British Nuclear Fuels and British Aerospace. The early PC viruses caught Mike’s attention, and he developed an interest in analyzing malware, and learning the low-level technical details of how Windows and network security work under the hood.
В этом посте рассказывается о адаптерах TAP-Windows , о том, что они собой представляют, зачем они нужны для VPN и где можно скачать драйверы TAP. Мы также покажем вам, как установить, обновить или удалить драйвер TAP.
Если вы откроете Настройки в Windows 10, вы увидите программу под названием TAP-Windows.
Пользователи Windows 10/8/7/Vista увидят его на панели управления .
Если вы откроете Диспетчер устройств и развернете Адаптеры, вы также увидите его там.
Читать . Где скачать драйверы для Windows 10.
Содержание
- Что такое адаптеры TAP-Windows
- Адаптеры TAP-Windows в этой системе в настоящее время используются
- В этой системе нет адаптеров TAP-Windows
- Скачать драйвер адаптера TAP-Windows
Что такое адаптеры TAP-Windows
TAP-Windows обеспечивает функциональность виртуального устройства TAP в ОС Windows. Он устанавливается в папку C: Program Files TAP-Windows и требуется для работы программного обеспечения VPN.
Устройства TAP – это устройства ядра виртуальной сети, полностью поддерживаемые программным обеспечением и не поддерживаемые аппаратными сетевыми адаптерами. Драйверы TAP используются для работы устройств TAP и имеют низкоуровневую поддержку ядра для туннелирования Ethernet.
Вам не нужно устанавливать TAP-окна отдельно, так как ваши установщики VPN включают их и устанавливают автоматически вместе с программным обеспечением VPN.
Драйвер TAP-Windows бывает двух типов:
- NDIS 6 (TAP-windows6, версия 9.21.x) для Windows 10/8/7/Vista.
- Драйвер NDIS 5 (TAP-windows, версия 9.9.x) для Windows XP.
Иногда вы можете столкнуться с проблемами , вызванными этим драйвером. Давайте посмотрим на некоторые из них.
Адаптеры TAP-Windows в этой системе в настоящее время используются
Если вы видите это сообщение или у вашего программного обеспечения VPN возникают проблемы с запуском, вы можете перезапустить адаптер TAP и посмотреть, поможет ли это. Для этого откройте Панель управления> Центр управления сетями и общим доступом> Нажмите «Изменить параметры адаптера», чтобы открыть «Сетевые подключения».
Вы увидите, что одно из локальных подключений будет иметь имя TAP-Windows Adapter . Щелкните правой кнопкой мыши по нему и выберите Отключить . Через несколько секунд снова щелкните его правой кнопкой мыши и выберите Включить . Теперь попробуйте подключиться снова и посмотреть, работает ли он.
Если у вас возникают другие проблемы с запуском вашего программного обеспечения VPN, я предлагаю вам открыть панель управления и оттуда либо восстановить , либо удалить и переустановить программное обеспечение VPN и посмотреть. Во время ремонта/установки будут установлены драйверы TAP.
Если вы хотите удалить, отключить или обновить TAP-Windows, из меню WinX Windows 10, откройте Диспетчер устройств и разверните Адаптеры, вы увидите Адаптер TAP-Windows v9.
Щелкните правой кнопкой мыши на нем, и вам предложат варианты обновить, отключить или удалить драйвер.
В этой системе нет адаптеров TAP-Windows
Если ваше программное обеспечение VPN не находит этот драйвер установленным на вашем компьютере, вы можете получить сообщение «В этом системном сообщении об ошибке отсутствуют адаптеры TAP-Windows». Затем вам нужно будет загрузить его настройки и установить драйвер.
Скачать драйвер адаптера TAP-Windows
Чтобы загрузить файл драйвера TAP-Windows, посетите openvpn.net. Прокрутите вниз, и вы увидите их ссылки для скачивания.
Запустите его установщик. После завершения установки драйвера перезагрузите компьютер и проверьте.
Если ваше Интернет-соединение перестает работать, вы можете удалить этот адаптер и посмотреть, поможет ли это вам. Если это не так, возможно, вам нужно удалить и переустановить последнюю версию этого драйвера заново .
Читать дальше : VPN не работает в Windows 10.
Содержание
- Что такое адаптеры TAP-Windows
- Как исправить проблемы с TAP-Windows
- Перезагрузите адаптер TAP-Windows
- Переустановите адаптер
- Создайте новый адаптер TAP-Windows
Прежде всего, мы собираемся объяснить, что такое адаптеры TAP-Windows. Когда мы идем в диспетчер устройств и вводим сетевые адаптеры, мы видим нашу карту Wi-Fi или карту Ethernet, а также другие, которые у нас есть. Это физические карты, которые установлены в нашем оборудовании. Но мы также можем установить виртуальные адаптеры. То есть TAP-Окна .
Поэтому можно сказать, что TAP-Windows адаптер — это виртуальный сетевой адаптер который существует в системе Windows. Его можно использовать для различных задач, в зависимости от конкретных характеристик программного обеспечения.
Обычно они связаны с установкой и использованием VPN инструменты , а также установка программ для изменения сетевых настроек. Поэтому они тесно связаны с правильным функционированием виртуальной частной сети. В случае возникновения проблем, если он не включен правильно, у нас могут возникнуть сбои с нашим VPN.
Многие пользователи замечают, что при использовании VPN в Windows устанавливается что-то под названием TAP-Windows V9. Это может вызвать проблемы при использовании VPN или при обычном подключении.
Этот виртуальный адаптер позволяет VPN подключаться к вашим серверам. По крайней мере, на бумаге пользователям не нужно прикасаться ни к одному из этих компонентов. Им просто нужно оставить все как есть, и все. Но иногда возникают проблемы.
Как исправить проблемы с TAP-Windows
Как мы говорим, иногда возникают проблемы и TAP-Windows плохо работает , это не позволяет нам использовать VPN в обычном режиме или даже нарушать наше сетевое соединение. К счастью, у нас есть ряд простых действий, которые мы можем выполнить.
Перезагрузите адаптер TAP-Windows
Один из первых шагов, которые мы можем сделать, — это перезапустить TAP-Окна адаптер . Иногда с помощью этого небольшого шага мы можем решить ошибки, которые влияют на наше соединение.
Для этого мы должны щелкнуть правой кнопкой мыши значок подключения в правом нижнем углу и выбрать «Открыть настройки сети и Интернета».
Здесь мы должны ввести параметры изменения адаптера. Там мы увидим значок адаптера TAP-Windows, и мы должны щелкнуть второй кнопкой над ним, мы нажимаем «Деактивировать», и мы повторно активируем его позже. Таким образом он перезапускается.
Переустановите адаптер
Другой вариант, который мы также можем принять во внимание, если предыдущий шаг не решил проблему, — это переустановите адаптер . Первым шагом будет удаление программного обеспечения VPN, которое мы используем, и его повторная установка. Как только мы сделаем этот процесс, мы должны перезагрузить компьютер.
Если это по-прежнему не дает решения, мы переустановим адаптер TAP-Windows. Для этого щелкаем правой кнопкой мыши по кнопке Пуск и открываем Диспетчер устройств. Мы идем в Cеть адаптеры, и когда мы покажем это, он появится. Мы должны щелкнуть правой кнопкой мыши по адаптеру и нажать «Удалить».
Позже мы запускаем VPN, и он может попросить нас снова установить адаптер TAP-Windows. Мы также можем скачать и установить его вручную.
Создайте новый адаптер TAP-Windows
Последним решением было бы создать новый TAP-Окна адаптер . Это происходит, когда мы подключаемся к новой VPN.
В конечном счете, это шаги, которые мы должны предпринять в случае, если у нас возникнут проблемы с использованием VPN в Windows, и ошибка связана с адаптером TAP-Windows. Мы можем повторно включить его, переустановить или создать новый, чтобы увидеть, можно ли легко решить эту проблему.
If you’ve ever used a VPN service on desktop then you’ve probably come across the term TAP Adapter. Unfortunately, you’re most likely to have seen it in some unhelpful error message.
Whether it’s ‘All Windows TAP adapters in use’, ‘No TAP adapter available’, or ‘An error occurred installing the TAP device driver’, there’s often a TAP problem somewhere with your name on it!
And the messages usually give you little or no advice on how to figure out the problem, either, so the best you can do is pop them into a search engine and see what comes up.
But this isn’t quite as bad as it seems. In this article, we’ll explain what TAP adapters are, what they’re for and why they matter when you’re running a Windows 10 VPN on PC. And once you understand just some of the background, you’ll find you can fix most TAP issues very quickly.
Do I have a TAP adapter?
A TAP adapter is a software-based network device which allows a VPN to securely communicate with its servers. It’s such a fundamental component that if the TAP adapter isn’t installed or working then some VPNs won’t work at all, resulting in all those pesky error messages you know so well.
TAP adapters come in many different flavors, which can make life confusing. Some VPNs install a plain, ordinary, generic TAP adapter, but others have specially patched ones which only work with their own service. You might even have two or more versions installed at the same time.
To check your setup, click start, type DEVMGMT.MSC and press Enter to launch Device Manager.
Click the arrowhead to the left of Network Adapters to expand the tree, and look down the list of adapters. If you see ‘TAP-Windows Adapter V9’ then you have the generic TAP adapter installed.
But custom versions often have the VPN name included, too, like ‘TAP-NordVPN Windows Adapter V9.’ if you’re a NordVPN user. If you’re unsure, double-click a driver, click the Driver tab, then Driver Details: if the Provider or Copyright mentions OpenVPN then it’s probably a TAP adapter.
Multiple TAP adapters
Having two or more TAP adapters installed can sometimes cause problems, especially if you’ve also installed more than one VPN. One VPN app might try to use an adapter belonging to another VPN, for instance, leaving the second app to complain that there are no adapters available.
VPN providers recognize that this is a problem, and some apps include an option to ‘repair’ the TAP adapter, restoring its regular settings to help the app find it again. In the IPVanish Windows app, for instance, click Settings, Connection, and you’ll find an Install/ Repair OpenVPN Driver option which could solve the problem.
You can also try resetting a TAP adapter by disabling and enabling it, the software equivalent of turning it off and on again. Right-click your VPN’s TAP adapter in Device Manager that you found earlier, choose Disable Device, and click Yes when you’re asked to confirm that. Wait a few seconds, right-click Enable Device, reboot your PC and try connecting to the VPN again.
Uninstall and reinstall a TAP adapter
Most VPN apps automatically install a TAP adapter with their own files, so reinstalling the app often fixes any TAP issues.
Click Start, type and launch Control Panel, then click Programs, Uninstall a Program. Find the entry for your Windows VPN app, click it and select Uninstall.
Sometimes there’s a second item representing the TAP adapter, something like ‘MyVPNName network TAP’. If it’s still there, uninstall that, too.
Reboot, then download and install the latest app. Reboot again, launch the app, and see if you have any more connection success.
If you have two or more VPNs installed, we’d recommend uninstalling any that you don’t really need, to reduce the chance of conflicts. Even if you absolutely must run a couple of VPNs side-by-side, for some reason, uninstall one of them temporarily to see if that fixes the problem.
(opens in new tab)
More TAP tricks
Stubborn TAP adapter problems can be due to leftovers from a previous installation. We’ve previously been unable to install a new TAP adapter because it was blocked by a previous, damaged version, for instance.
If you really know what you’re doing, follow our guide on how to completely uninstall a VPN (particularly the Network Adaptors and System Drivers sections) to clean up any old VPN files and settings. But be careful: messing up here can damage your PC, so don’t even think of it unless you’re confident in your disaster recovery abilities.
If you still can’t solve your problem, it’s possible you can bypass it. Disable the NordVPN TAP adapter, for instance, and its app can’t connect via OpenVPN. But switch to the NordLynx protocol (click Settings, Auto-connect, choose NordLynx from the VPN Protocol list) and it should work again.
That kind of quick fix isn’t a great choice, because if a VPN app is displaying errors and you don’t know exactly why, then it may be reliably protecting you any more (there might also be encryption issues, say.) But it should keep you running for a while, if that’s the priority.
After all your hard troubleshooting work, though, the best idea is to contact your VPN support team and ask for help. Tell them everything you’ve tried so far, and they should be able to point you in the right direction.
Read more:
- Get protected online for less with a great cheap VPN…
- …and with market-leading antivirus software
- Stop logging of your PC activities with our Windows 10 privacy guide
Sign up to theTechRadar Pro newsletter to get all the top news, opinion, features and guidance your business needs to succeed!
Mike is a lead security reviewer at Future, where he stress-tests VPNs, antivirus and more to find out which services are sure to keep you safe, and which are best avoided. Mike began his career as a lead software developer in the engineering world, where his creations were used by big-name companies from Rolls Royce to British Nuclear Fuels and British Aerospace. The early PC viruses caught Mike’s attention, and he developed an interest in analyzing malware, and learning the low-level technical details of how Windows and network security work under the hood.
If you’ve ever used a VPN service on desktop then you’ve probably come across the term TAP Adapter. Unfortunately, you’re most likely to have seen it in some unhelpful error message.
Whether it’s ‘All Windows TAP adapters in use’, ‘No TAP adapter available’, or ‘An error occurred installing the TAP device driver’, there’s often a TAP problem somewhere with your name on it!
And the messages usually give you little or no advice on how to figure out the problem, either, so the best you can do is pop them into a search engine and see what comes up.
But this isn’t quite as bad as it seems. In this article, we’ll explain what TAP adapters are, what they’re for and why they matter when you’re running a Windows 10 VPN on PC. And once you understand just some of the background, you’ll find you can fix most TAP issues very quickly.
Do I have a TAP adapter?
A TAP adapter is a software-based network device which allows a VPN to securely communicate with its servers. It’s such a fundamental component that if the TAP adapter isn’t installed or working then some VPNs won’t work at all, resulting in all those pesky error messages you know so well.
TAP adapters come in many different flavors, which can make life confusing. Some VPNs install a plain, ordinary, generic TAP adapter, but others have specially patched ones which only work with their own service. You might even have two or more versions installed at the same time.
To check your setup, click start, type DEVMGMT.MSC and press Enter to launch Device Manager.
Click the arrowhead to the left of Network Adapters to expand the tree, and look down the list of adapters. If you see ‘TAP-Windows Adapter V9’ then you have the generic TAP adapter installed.
But custom versions often have the VPN name included, too, like ‘TAP-NordVPN Windows Adapter V9.’ if you’re a NordVPN user. If you’re unsure, double-click a driver, click the Driver tab, then Driver Details: if the Provider or Copyright mentions OpenVPN then it’s probably a TAP adapter.
Multiple TAP adapters
Having two or more TAP adapters installed can sometimes cause problems, especially if you’ve also installed more than one VPN. One VPN app might try to use an adapter belonging to another VPN, for instance, leaving the second app to complain that there are no adapters available.
VPN providers recognize that this is a problem, and some apps include an option to ‘repair’ the TAP adapter, restoring its regular settings to help the app find it again. In the IPVanish Windows app, for instance, click Settings, Connection, and you’ll find an Install/ Repair OpenVPN Driver option which could solve the problem.
You can also try resetting a TAP adapter by disabling and enabling it, the software equivalent of turning it off and on again. Right-click your VPN’s TAP adapter in Device Manager that you found earlier, choose Disable Device, and click Yes when you’re asked to confirm that. Wait a few seconds, right-click Enable Device, reboot your PC and try connecting to the VPN again.
Uninstall and reinstall a TAP adapter
Most VPN apps automatically install a TAP adapter with their own files, so reinstalling the app often fixes any TAP issues.
Click Start, type and launch Control Panel, then click Programs, Uninstall a Program. Find the entry for your Windows VPN app, click it and select Uninstall.
Sometimes there’s a second item representing the TAP adapter, something like ‘MyVPNName network TAP’. If it’s still there, uninstall that, too.
Reboot, then download and install the latest app. Reboot again, launch the app, and see if you have any more connection success.
If you have two or more VPNs installed, we’d recommend uninstalling any that you don’t really need, to reduce the chance of conflicts. Even if you absolutely must run a couple of VPNs side-by-side, for some reason, uninstall one of them temporarily to see if that fixes the problem.
(opens in new tab)
More TAP tricks
Stubborn TAP adapter problems can be due to leftovers from a previous installation. We’ve previously been unable to install a new TAP adapter because it was blocked by a previous, damaged version, for instance.
If you really know what you’re doing, follow our guide on how to completely uninstall a VPN (particularly the Network Adaptors and System Drivers sections) to clean up any old VPN files and settings. But be careful: messing up here can damage your PC, so don’t even think of it unless you’re confident in your disaster recovery abilities.
If you still can’t solve your problem, it’s possible you can bypass it. Disable the NordVPN TAP adapter, for instance, and its app can’t connect via OpenVPN. But switch to the NordLynx protocol (click Settings, Auto-connect, choose NordLynx from the VPN Protocol list) and it should work again.
That kind of quick fix isn’t a great choice, because if a VPN app is displaying errors and you don’t know exactly why, then it may be reliably protecting you any more (there might also be encryption issues, say.) But it should keep you running for a while, if that’s the priority.
After all your hard troubleshooting work, though, the best idea is to contact your VPN support team and ask for help. Tell them everything you’ve tried so far, and they should be able to point you in the right direction.
Read more:
- Get protected online for less with a great cheap VPN…
- …and with market-leading antivirus software
- Stop logging of your PC activities with our Windows 10 privacy guide
Sign up to theTechRadar Pro newsletter to get all the top news, opinion, features and guidance your business needs to succeed!
Mike is a lead security reviewer at Future, where he stress-tests VPNs, antivirus and more to find out which services are sure to keep you safe, and which are best avoided. Mike began his career as a lead software developer in the engineering world, where his creations were used by big-name companies from Rolls Royce to British Nuclear Fuels and British Aerospace. The early PC viruses caught Mike’s attention, and he developed an interest in analyzing malware, and learning the low-level technical details of how Windows and network security work under the hood.
В этом посте рассказывается о адаптерах TAP-Windows , о том, что они собой представляют, зачем они нужны для VPN и где можно скачать драйверы TAP. Мы также покажем вам, как установить, обновить или удалить драйвер TAP.
Если вы откроете Настройки в Windows 10, вы увидите программу под названием TAP-Windows.
Пользователи Windows 10/8/7/Vista увидят его на панели управления .
Если вы откроете Диспетчер устройств и развернете Адаптеры, вы также увидите его там.
Читать . Где скачать драйверы для Windows 10.
Содержание
- Что такое адаптеры TAP-Windows
- Адаптеры TAP-Windows в этой системе в настоящее время используются
- В этой системе нет адаптеров TAP-Windows
- Скачать драйвер адаптера TAP-Windows
Что такое адаптеры TAP-Windows
TAP-Windows обеспечивает функциональность виртуального устройства TAP в ОС Windows. Он устанавливается в папку C: Program Files TAP-Windows и требуется для работы программного обеспечения VPN.
Устройства TAP – это устройства ядра виртуальной сети, полностью поддерживаемые программным обеспечением и не поддерживаемые аппаратными сетевыми адаптерами. Драйверы TAP используются для работы устройств TAP и имеют низкоуровневую поддержку ядра для туннелирования Ethernet.
Вам не нужно устанавливать TAP-окна отдельно, так как ваши установщики VPN включают их и устанавливают автоматически вместе с программным обеспечением VPN.
Драйвер TAP-Windows бывает двух типов:
- NDIS 6 (TAP-windows6, версия 9.21.x) для Windows 10/8/7/Vista.
- Драйвер NDIS 5 (TAP-windows, версия 9.9.x) для Windows XP.
Иногда вы можете столкнуться с проблемами , вызванными этим драйвером. Давайте посмотрим на некоторые из них.
Адаптеры TAP-Windows в этой системе в настоящее время используются
Если вы видите это сообщение или у вашего программного обеспечения VPN возникают проблемы с запуском, вы можете перезапустить адаптер TAP и посмотреть, поможет ли это. Для этого откройте Панель управления> Центр управления сетями и общим доступом> Нажмите «Изменить параметры адаптера», чтобы открыть «Сетевые подключения».
Вы увидите, что одно из локальных подключений будет иметь имя TAP-Windows Adapter . Щелкните правой кнопкой мыши по нему и выберите Отключить . Через несколько секунд снова щелкните его правой кнопкой мыши и выберите Включить . Теперь попробуйте подключиться снова и посмотреть, работает ли он.
Если у вас возникают другие проблемы с запуском вашего программного обеспечения VPN, я предлагаю вам открыть панель управления и оттуда либо восстановить , либо удалить и переустановить программное обеспечение VPN и посмотреть. Во время ремонта/установки будут установлены драйверы TAP.
Если вы хотите удалить, отключить или обновить TAP-Windows, из меню WinX Windows 10, откройте Диспетчер устройств и разверните Адаптеры, вы увидите Адаптер TAP-Windows v9.
Щелкните правой кнопкой мыши на нем, и вам предложат варианты обновить, отключить или удалить драйвер.
В этой системе нет адаптеров TAP-Windows
Если ваше программное обеспечение VPN не находит этот драйвер установленным на вашем компьютере, вы можете получить сообщение «В этом системном сообщении об ошибке отсутствуют адаптеры TAP-Windows». Затем вам нужно будет загрузить его настройки и установить драйвер.
Скачать драйвер адаптера TAP-Windows
Чтобы загрузить файл драйвера TAP-Windows, посетите openvpn.net. Прокрутите вниз, и вы увидите их ссылки для скачивания.
Запустите его установщик. После завершения установки драйвера перезагрузите компьютер и проверьте.
Если ваше Интернет-соединение перестает работать, вы можете удалить этот адаптер и посмотреть, поможет ли это вам. Если это не так, возможно, вам нужно удалить и переустановить последнюю версию этого драйвера заново .
Читать дальше : VPN не работает в Windows 10.
Содержание
- Что такое адаптеры TAP-Windows
- Как исправить проблемы с TAP-Windows
- Перезагрузите адаптер TAP-Windows
- Переустановите адаптер
- Создайте новый адаптер TAP-Windows
Прежде всего, мы собираемся объяснить, что такое адаптеры TAP-Windows. Когда мы идем в диспетчер устройств и вводим сетевые адаптеры, мы видим нашу карту Wi-Fi или карту Ethernet, а также другие, которые у нас есть. Это физические карты, которые установлены в нашем оборудовании. Но мы также можем установить виртуальные адаптеры. То есть TAP-Окна .
Поэтому можно сказать, что TAP-Windows адаптер — это виртуальный сетевой адаптер который существует в системе Windows. Его можно использовать для различных задач, в зависимости от конкретных характеристик программного обеспечения.
Обычно они связаны с установкой и использованием VPN инструменты , а также установка программ для изменения сетевых настроек. Поэтому они тесно связаны с правильным функционированием виртуальной частной сети. В случае возникновения проблем, если он не включен правильно, у нас могут возникнуть сбои с нашим VPN.
Многие пользователи замечают, что при использовании VPN в Windows устанавливается что-то под названием TAP-Windows V9. Это может вызвать проблемы при использовании VPN или при обычном подключении.
Этот виртуальный адаптер позволяет VPN подключаться к вашим серверам. По крайней мере, на бумаге пользователям не нужно прикасаться ни к одному из этих компонентов. Им просто нужно оставить все как есть, и все. Но иногда возникают проблемы.
Как исправить проблемы с TAP-Windows
Как мы говорим, иногда возникают проблемы и TAP-Windows плохо работает , это не позволяет нам использовать VPN в обычном режиме или даже нарушать наше сетевое соединение. К счастью, у нас есть ряд простых действий, которые мы можем выполнить.
Перезагрузите адаптер TAP-Windows
Один из первых шагов, которые мы можем сделать, — это перезапустить TAP-Окна адаптер . Иногда с помощью этого небольшого шага мы можем решить ошибки, которые влияют на наше соединение.
Для этого мы должны щелкнуть правой кнопкой мыши значок подключения в правом нижнем углу и выбрать «Открыть настройки сети и Интернета».
Здесь мы должны ввести параметры изменения адаптера. Там мы увидим значок адаптера TAP-Windows, и мы должны щелкнуть второй кнопкой над ним, мы нажимаем «Деактивировать», и мы повторно активируем его позже. Таким образом он перезапускается.
Переустановите адаптер
Другой вариант, который мы также можем принять во внимание, если предыдущий шаг не решил проблему, — это переустановите адаптер . Первым шагом будет удаление программного обеспечения VPN, которое мы используем, и его повторная установка. Как только мы сделаем этот процесс, мы должны перезагрузить компьютер.
Если это по-прежнему не дает решения, мы переустановим адаптер TAP-Windows. Для этого щелкаем правой кнопкой мыши по кнопке Пуск и открываем Диспетчер устройств. Мы идем в Cеть адаптеры, и когда мы покажем это, он появится. Мы должны щелкнуть правой кнопкой мыши по адаптеру и нажать «Удалить».
Позже мы запускаем VPN, и он может попросить нас снова установить адаптер TAP-Windows. Мы также можем скачать и установить его вручную.
Создайте новый адаптер TAP-Windows
Последним решением было бы создать новый TAP-Окна адаптер . Это происходит, когда мы подключаемся к новой VPN.
В конечном счете, это шаги, которые мы должны предпринять в случае, если у нас возникнут проблемы с использованием VPN в Windows, и ошибка связана с адаптером TAP-Windows. Мы можем повторно включить его, переустановить или создать новый, чтобы увидеть, можно ли легко решить эту проблему.
Unfortunately, none of the suggestions worked.
Got the same issue, here is my experience.
1. Running Windows 7, Ultimate edition, x64;
2. OpenVPN 2.5.3 gets installed fine;
however, setupapi.dev.log contains following:
sig: {_VERIFY_FILE_SIGNATURE} 15:18:46.274
sig: Key = oemvista.inf
sig: FilePath = c:program filestap-windowsdriveroemvista.inf
sig: Catalog = c:program filestap-windowsdrivertap0901.cat
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 15:18:46.331
sig: {_VERIFY_FILE_SIGNATURE} 15:18:46.331
sig: Key = oemvista.inf
sig: FilePath = c:program filestap-windowsdriveroemvista.inf
sig: Catalog = c:program filestap-windowsdrivertap0901.cat
sig: Success: File is signed in Authenticode(tm) catalog.
sig: Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 15:18:46.351
(same applies to wintun)
So tap driver isn’t being recognized by the system (go to device manager/check network section/see tap driver with yellow triangle on the icon:
«This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)»
3. To resolve the tap driver challenges, tried:
3.1 Full system cleanup (delete all the drivers, openvpn installs, tap installer/reinstalled everything w/ and w/o tap installer)
(i still do wander why other drivers may interfere with the install from openvpn, but that’s a diff story)
3.2 bcedit experiments & windows reboot with «disable driver signature enforcement»
3.3 manually imported certificates (via certmgr & mmc snap in for the local computer; to root & trusted publisher)
3.4 signed driver myself & used self-signed certificate
As an experiment, took clean windows 7 x64 sp1 — installed openvpn — has challenges too, works only under «disable driver signature enforcement».
But at least — tap driver is recognized as a driver — and is loaded properly if one chooses «disable driver signature»; so it sorta works.
~~~
After all the experiments, this is what i came down to:
There seem to be two issues that the latest OpenVPN installer has;
and latest tap driver installer has;
(and they seem to have it (at least) for the past ~8-10 releases (went as far as 9.9 with tap installer; and 2.0 with openvpn))
a) Challenge one: digital signature. Technically, one can bypass it by either experimenting bcedits; enabling test mode; or by loading via F8/disable driver signature. Who’s at fault — Microsoft, who started enforcing driver signatures; that’s annoying exercise to go through, a lot of projects out there choose not to do it;
b) Challenge two: busted certificate chain.
(that’s the one is unable to overcome).
Something is screwed up with certificates associated with openvpn/tap installer.
And not with the certificate itself — the one that’s assigned to it; it’s good and legit; but specifically with the intermediate certificate: the one that (in theory) you could get from the digisign guys.
Funny enough, Microsoft has exactly the same challenges with one of their .NET library installs: and to resolve it, they have provided combined — proper — certificate — that you can install yourself and make it work.
But with OpenVPN — we do not have (direct) access to combined (and verified!) certificate (yes, i tried to get it exported/imported; including chain of certs; didn’t work. tried to go to the source — digi sign website — to grab intermediate cert — no good either)
So cert challenges combined with digital signature challenges — and entire application becomes useless.
Direction that (in theory) could work:
If one updates registry; and adds following record to the driver:
«ComponentId» with the value «tap0901»:
It makes «Network card» to be visible to openVPN app;
So error from «hey, you have no tap devices out there»:
Turns into «hey, you have tap device there, but it’s busy».
(chances are, OpenVPN queries registry directly, bypassing Windows API; which is why it makes a difference)
Therefore if one manages to mimic «properly enabled driver» through regedits — it might actually work, and provide solution to all those people who have troubles. I’ll keep digging this direction, but if someone with a bit more experience could assist — help would be very much appreciated.
Alternative, is to provide chained certificate for the software (that’s question to openvpn devs) that’s been properly validated and considered to be valid by Microsoft.
That way, digital signature can be overrulled with bcedits/and/or/F8/disable driver signature enforcement):
And certs is legit:
And we’d be good.
Third alternative (unlikely) — is to include proper certificate & proper digital signature in the future releases of openvpn:
But while first one should be easy; getting proper signature in place doesn’t seem to look too good.
~~
any other suggestions/comments/possible ways to resolve it — will seriously appreciate some help here.
For now it doesn’t look too promising.
Столкнулся с неожиданной проблемой при установке клиента популярной реализации vpn. Не устанавливался openvpn клиент на Windows 10, выдавая ошибку установки TAP интерфейса: «An error occurred installing the TAP device driver«.
Ошибка установки openvpn на Windows 10 выглядела следующим образом. Инсталятор после выбора дефолтных настроек задумывается на несколько минут и в итоге выдает ошибку:
При этом сам клиент openvpn успешно устанавливается. Можно запустить GIU, но ясное дело, подключиться к серверу openvpn не получится, так как в системе не появляется TAP адаптера. В интернете нашел много советов по данной проблеме, но мне ни один не помог. Перечислю их, может вам поможет что-то из этого:
- Запустить скрипт на добавление TAP интерфейса — C:Program FilesTAP-Windowsbinaddtap.bat. У меня он так же не отрабатывал. Висел несколько минут, потом выдавал ошибку.
- Зайти в Пуск -> TAP Windows -> Add a new TAP virtual ethernet adapter. Это тоже не помогло.
- Повторить установку openvpn с выключенным антивирусом или защитником windows.
Два первых действия нужно выполнять от администратора. С помощью них можно добавить несколько tap адаптеров в систему, чтобы одновременно поднимать несколько openvpn туннелей.
После того, как ничего из предложенного не подошло, я крепко призадумался. Openvpn я использую постоянно. Ставил его на разные системы десятки раз и всегда все проходило успешно, либо проблема быстро решалась. Тут быстрого и простого решения не получалось.
Помогло в итоге вот что. Я открыл диспетчер устройств и посмотрел на сетевые адаптеры. В списке был TAP-Windows Adapter V9, что намекало на то, что все должно работать. Но не работало. В панели управления в списке адаптеров TAP адаптера не было.
Я включил отображение скрытых устройств и увидел там же в сетевых адаптерах неизвестное устройство (unknown device). Открыл у него вкладку Сведения. Путь к экземпляру устройства был следующий — ROOTNET000. Я нажал обновить драйвер для этого устройства и указал, что он должен быть найден автоматически. После этого устройство получило название TAP-Windows Adapter V9 #2 и в панели управления появился TAP адаптер.
После этого Openvpn заработал. Я смог подключиться к серверу и организовать туннель. После того, как я удалил openvpn на этой же системе и установил заново, все прошло без ошибок с первого раза. Появился только один TAP-Windows Adapter V9. Проверил еще на парочке тестовых виртуальных машин. Тоже все прошло без ошибок, так что не смог собрать актуальные скрины по проблеме, а сразу их не сделал.
Если решение не поможет, то обратите внимание на следующее, берите бубен и танцуйте:
Драйвер для TAP адаптера должен быть в директории C:WindowsSystem32DriverStoreFileRepositoryoemvista.inf_amd64_*. В конце могут быть разные символы. На той системе, где был глюк, были созданы 2 подобных директории с разными символами на конце. Когда проблем нет — только одна.
https://github.com/midnight47/
Unfortunately, none of the suggestions worked.
Got the same issue, here is my experience.
1. Running Windows 7, Ultimate edition, x64;
2. OpenVPN 2.5.3 gets installed fine;
however, setupapi.dev.log contains following:
sig: {_VERIFY_FILE_SIGNATURE} 15:18:46.274
sig: Key = oemvista.inf
sig: FilePath = c:program filestap-windowsdriveroemvista.inf
sig: Catalog = c:program filestap-windowsdrivertap0901.cat
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 15:18:46.331
sig: {_VERIFY_FILE_SIGNATURE} 15:18:46.331
sig: Key = oemvista.inf
sig: FilePath = c:program filestap-windowsdriveroemvista.inf
sig: Catalog = c:program filestap-windowsdrivertap0901.cat
sig: Success: File is signed in Authenticode(tm) catalog.
sig: Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 15:18:46.351
(same applies to wintun)
So tap driver isn’t being recognized by the system (go to device manager/check network section/see tap driver with yellow triangle on the icon:
«This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)»
3. To resolve the tap driver challenges, tried:
3.1 Full system cleanup (delete all the drivers, openvpn installs, tap installer/reinstalled everything w/ and w/o tap installer)
(i still do wander why other drivers may interfere with the install from openvpn, but that’s a diff story)
3.2 bcedit experiments & windows reboot with «disable driver signature enforcement»
3.3 manually imported certificates (via certmgr & mmc snap in for the local computer; to root & trusted publisher)
3.4 signed driver myself & used self-signed certificate
As an experiment, took clean windows 7 x64 sp1 — installed openvpn — has challenges too, works only under «disable driver signature enforcement».
But at least — tap driver is recognized as a driver — and is loaded properly if one chooses «disable driver signature»; so it sorta works.
~~~
After all the experiments, this is what i came down to:
There seem to be two issues that the latest OpenVPN installer has;
and latest tap driver installer has;
(and they seem to have it (at least) for the past ~8-10 releases (went as far as 9.9 with tap installer; and 2.0 with openvpn))
a) Challenge one: digital signature. Technically, one can bypass it by either experimenting bcedits; enabling test mode; or by loading via F8/disable driver signature. Who’s at fault — Microsoft, who started enforcing driver signatures; that’s annoying exercise to go through, a lot of projects out there choose not to do it;
b) Challenge two: busted certificate chain.
(that’s the one is unable to overcome).
Something is screwed up with certificates associated with openvpn/tap installer.
And not with the certificate itself — the one that’s assigned to it; it’s good and legit; but specifically with the intermediate certificate: the one that (in theory) you could get from the digisign guys.
Funny enough, Microsoft has exactly the same challenges with one of their .NET library installs: and to resolve it, they have provided combined — proper — certificate — that you can install yourself and make it work.
But with OpenVPN — we do not have (direct) access to combined (and verified!) certificate (yes, i tried to get it exported/imported; including chain of certs; didn’t work. tried to go to the source — digi sign website — to grab intermediate cert — no good either)
So cert challenges combined with digital signature challenges — and entire application becomes useless.
Direction that (in theory) could work:
If one updates registry; and adds following record to the driver:
«ComponentId» with the value «tap0901»:
It makes «Network card» to be visible to openVPN app;
So error from «hey, you have no tap devices out there»:
Turns into «hey, you have tap device there, but it’s busy».
(chances are, OpenVPN queries registry directly, bypassing Windows API; which is why it makes a difference)
Therefore if one manages to mimic «properly enabled driver» through regedits — it might actually work, and provide solution to all those people who have troubles. I’ll keep digging this direction, but if someone with a bit more experience could assist — help would be very much appreciated.
Alternative, is to provide chained certificate for the software (that’s question to openvpn devs) that’s been properly validated and considered to be valid by Microsoft.
That way, digital signature can be overrulled with bcedits/and/or/F8/disable driver signature enforcement):
And certs is legit:
And we’d be good.
Third alternative (unlikely) — is to include proper certificate & proper digital signature in the future releases of openvpn:
But while first one should be easy; getting proper signature in place doesn’t seem to look too good.
~~
any other suggestions/comments/possible ways to resolve it — will seriously appreciate some help here.
For now it doesn’t look too promising.
OpenVPN Support Forum
Community Support Forum
TAP installer failed on Windows 10
TAP installer failed on Windows 10
Post by hermy9 » Sun Nov 27, 2016 2:40 pm
Hi, I hope that I am at the right place.
Installing Openvpn 2.3.13 failed on win10 with this error message, after two successful installations on other win10 systems.
«An error occurred installing the TAP device driver.»
Installing TAP separately fails with the same error message. In addition, the log shows this sequence at the end:
«Updating drivers for tap0901 from C:Program FilesTAP-WindowsdriverOemVista.inf.
UpdateDriverForPlugAndPlayDevices failed, GetLastError = -536870330
tapinstall.exe failed.
tapinstall.exe returned: 2
tapinstall cumulative status: 2
Created uninstaller: C:Program FilesTAP-WindowsIninstall.exe
Completed»
What is going wrong here? What does the error code mean?
I tried several things:
— Openvpn connection to my external server is not possible
— Avira Services deactivated
— Windows firewall deactivated
— reboot
The error code cannot be found with Google.
Re: TAP installer failed on Windows 10
Post by TinCanTech » Mon Nov 28, 2016 1:59 pm
«Add new TAP Virtual ethernet adapter» -> Run as administrator
Re: TAP installer failed on Windows 10
Post by hermy9 » Mon Nov 28, 2016 10:18 pm
Re: TAP installer failed on Windows 10
Post by hermy9 » Sun Dec 04, 2016 8:31 am
In the meantime, I spent hours and tried a lot of things, no success up to now.
I noted that the driver is not in windows registry. Based on
https://support.vpnsecure.me/articles/g . ters-found
I see 13 entries in registry:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlClass<4d36e972-e325-11ce-bfc1-08002be10318>xxxx
where
xxxx = 0000 . 0012
None of them can be attributed to TAP-Windows Adapter V9. I followed the instruction given by the link above (which is not very clear), with no success.
On my other win10 system, I see 17 entries, and entry 0015 can be attributed to the TAP driver. There, all works fine.
Other attempts (reboot, windows secure mode, clean registry with ccleaner . ) were unsuccessful as well.
So, my question is still the same. What is going wrong when installing the TAP driver?
Last lines of C:WindowsINFsetupapi.dev.log follow here, after having done this:
— uninstalling TAP and Openvpn using uninstall.exe for both
— cleaning c:BenutzerAdministratorAppDataLocalTemp
Re: TAP installer failed on Windows 10
Post by Renske » Tue Oct 17, 2017 2:00 pm
I have the same problem installing the TAP driver. I get the same error messages as mentioned by hermy9. It appears to be some problem with certificates:
From setupapi.dev.log:
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
I tried uninstalling, rebooting and installing (as administrator) several times, both OpenVPN and TAP separately, but I can’t get it to work. My colleagues have exactly the same computer and they don’t have any problems.
hermy9, did you ever manage to solve this problem? Does anyone else have any suggestions on what to try?
TinCanTech, where should I right-click for the option that you mentioned?
Re: TAP installer failed on Windows 10
Post by TinCanTech » Tue Oct 17, 2017 4:59 pm
Windows Menu -> Tap Windows -> Add or Remove Tap Adapter
Must be run as administrator.
Re: TAP installer failed on Windows 10
Post by Renske » Thu Oct 19, 2017 7:36 am
Thanks for your reply TinCanTech. Unfortunately it is not working. I ran it as administrator, but I get the following error message:
«C:Windowssystem32>rem Add a new TAP virtual ethernet adapter
C:Windowssystem32>»C:Program FilesTAP-Windowsbintapinstall.exe» install «C:Program FilesTAP-WindowsdriverOemVista.inf» tap0901
Device node created. Install is complete when drivers are installed.
Updating drivers for tap0901 from C:Program FilesTAP-WindowsdriverOemVista.inf.
UpdateDriverForPlugAndPlayDevices failed, GetLastError=-536870330
tapinstall.exe failed.»
Do you have any other suggestions on what I could try?
Re: TAP installer failed on Windows 10
Post by TinCanTech » Thu Oct 19, 2017 10:52 am
This bug has never been properly diagnosed — You may find some information here:
Re: TAP installer failed on Windows 10
Post by kekster » Thu Apr 19, 2018 6:38 am
Re: TAP installer failed on Windows 10
Post by TinCanTech » Thu Apr 19, 2018 11:55 am
Re: TAP installer failed on Windows 10
Post by Renske » Thu Apr 19, 2018 2:17 pm
Re: TAP installer failed on Windows 10
Post by tojieb » Mon May 06, 2019 3:57 am
Re: TAP installer failed on Windows 10 TEMP FIX
Post by unknown » Thu Oct 10, 2019 8:34 am
hey, found a temp workaround for this issue, not sure if it will work for you, but it did for me, here we go.
Steps:
- open control panel > device manager
- scroll down to «Network adapters»
- there should be one that shows as «unknown device», double click on it, head to the «Details» tab, then select the property «Device instance path», this should have a value of «ROOT/NET/0000»
- once you confirm the Infos above, head back to the «Network adapters» tab, and right-click the unknown device, then select «Update driver software», then a new window should open up, select «Search automatically for updated driver software».
you should receive a notification saying that windows found and updated the driver software, and it will no longer show up as an unknown device on the network adapters tab, make sure you restart Open VPN if it was running, and Voila!!
Re: TAP installer failed on Windows 10
Post by adreyfus » Fri Nov 15, 2019 2:15 pm
Same error for me. The solutions proposed above did not work.
But uninstalling Check Point VPN client worked !
Re: TAP installer failed on Windows 10
Post by rejerh » Fri Apr 10, 2020 3:46 am
I am having the same problem on any of the version of TAP I could find (9.21, 9.22, 9.24)
This is very frustrating. Nothing I could find in this thread helped me resolve this issue.
Has anyone found a robust fix?
Re: TAP installer failed on Windows 10
Post by Bantic » Tue Jun 15, 2021 7:50 am
I fixed problem with installing adapter ( this is one of many solution becouse reason may be more then one)
Go to:
Control Panel -> Device Menager -> Networ adapters -> find TAP Windows Open VPN adapter -> delete it
After that intall as administrator TAP Adapter once agian.
Re: TAP installer failed on Windows 10
Post by sid11 » Sun Sep 12, 2021 10:57 pm
Unfortunately, none of the suggestions worked.
Got the same issue, here is my experience.
1. Running Windows 7, Ultimate edition, x64;
2. OpenVPN 2.5.3 gets installed fine;
however, setupapi.dev.log contains following:
sig: <_VERIFY_FILE_SIGNATURE>15:18:46.274
sig: Key = oemvista.inf
sig: FilePath = c:program filestap-windowsdriveroemvista.inf
sig: Catalog = c:program filestap-windowsdrivertap0901.cat
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
sig: <_VERIFY_FILE_SIGNATURE exit(0x800b0109)>15:18:46.331
sig: <_VERIFY_FILE_SIGNATURE>15:18:46.331
sig: Key = oemvista.inf
sig: FilePath = c:program filestap-windowsdriveroemvista.inf
sig: Catalog = c:program filestap-windowsdrivertap0901.cat
sig: Success: File is signed in Authenticode(tm) catalog.
sig: Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
sig: <_VERIFY_FILE_SIGNATURE exit(0xe0000241)>15:18:46.351
(same applies to wintun)
So tap driver isn’t being recognized by the system (go to device manager/check network section/see tap driver with yellow triangle on the icon:
«This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)»
3. To resolve the tap driver challenges, tried:
3.1 Full system cleanup (delete all the drivers, openvpn installs, tap installer/reinstalled everything w/ and w/o tap installer)
(i still do wander why other drivers may interfere with the install from openvpn, but that’s a diff story)
3.2 bcedit experiments & windows reboot with «disable driver signature enforcement»
3.3 manually imported certificates (via certmgr & mmc snap in for the local computer; to root & trusted publisher)
3.4 signed driver myself & used self-signed certificate
As an experiment, took clean windows 7 x64 sp1 — installed openvpn — has challenges too, works only under «disable driver signature enforcement».
But at least — tap driver is recognized as a driver — and is loaded properly if one chooses «disable driver signature»; so it sorta works.
After all the experiments, this is what i came down to:
There seem to be two issues that the latest OpenVPN installer has;
and latest tap driver installer has;
(and they seem to have it (at least) for the past
8-10 releases (went as far as 9.9 with tap installer; and 2.0 with openvpn))
a) Challenge one: digital signature. Technically, one can bypass it by either experimenting bcedits; enabling test mode; or by loading via F8/disable driver signature. Who’s at fault — Microsoft, who started enforcing driver signatures; that’s annoying exercise to go through, a lot of projects out there choose not to do it;
b) Challenge two: busted certificate chain.
(that’s the one is unable to overcome).
Something is screwed up with certificates associated with openvpn/tap installer.
And not with the certificate itself — the one that’s assigned to it; it’s good and legit; but specifically with the intermediate certificate: the one that (in theory) you could get from the digisign guys.
Funny enough, Microsoft has exactly the same challenges with one of their .NET library installs: and to resolve it, they have provided combined — proper — certificate — that you can install yourself and make it work.
But with OpenVPN — we do not have (direct) access to combined (and verified!) certificate (yes, i tried to get it exported/imported; including chain of certs; didn’t work. tried to go to the source — digi sign website — to grab intermediate cert — no good either)
So cert challenges combined with digital signature challenges — and entire application becomes useless.
Direction that (in theory) could work:
If one updates registry; and adds following record to the driver:
«ComponentId» with the value «tap0901»:
It makes «Network card» to be visible to openVPN app;
So error from «hey, you have no tap devices out there»:
Turns into «hey, you have tap device there, but it’s busy».
(chances are, OpenVPN queries registry directly, bypassing Windows API; which is why it makes a difference)
Therefore if one manages to mimic «properly enabled driver» through regedits — it might actually work, and provide solution to all those people who have troubles. I’ll keep digging this direction, but if someone with a bit more experience could assist — help would be very much appreciated.
Alternative, is to provide chained certificate for the software (that’s question to openvpn devs) that’s been properly validated and considered to be valid by Microsoft.
That way, digital signature can be overrulled with bcedits/and/or/F8/disable driver signature enforcement):
And certs is legit:
And we’d be good.
Third alternative (unlikely) — is to include proper certificate & proper digital signature in the future releases of openvpn:
But while first one should be easy; getting proper signature in place doesn’t seem to look too good.
any other suggestions/comments/possible ways to resolve it — will seriously appreciate some help here.
Источник
OpenVPN Support Forum
Community Support Forum
Installing TAP driver on Windows x64 fails [solved]
Installing TAP driver on Windows x64 fails [solved]
Post by sjoller » Mon Dec 27, 2010 11:27 am
I’m having trouble installing OpenVPN — the TAP driver simply refuses to install.
I’ve tried 5 different versions of the installer — including v2.1 RC19 which, according to a Google search, seems to be everyones solution.
I’ve tried v2.1.3, which supposedly should have the driver signing solved, v2.1.1, v2.1.4 and even v2.2 beta5 — all run as administrator.
I’ve tried running the installers in compability mode set to Vista, aswell.
I’ve tried downloading the x64 driver (tap0801), from openvpn.se, and installing it manually (from a dos prompt, run as administrator, from a destination folder that isn’t named with troublesome characters like space), and between the installs, i’ve even made sure to uninstall the «unknown» TAP network adaptor, the installations leaves behind.
I’ve tried extracting the driver (tap0901) from the installer and manually install it, using same procedure as above.
. I’m fresh out of ideas on how to get OpenVPN running on Windows 7 Ultimate x64, please help.
Regards
Mads Jensen
Re: TAP driver on Windows x64
Post by gladiatr72 » Mon Dec 27, 2010 5:21 pm
I’m not a Windows Guy(tm), but what sort of errors are being emitted when the installation fails?
After the error, is there anything left in the installation target directory?
Check if the following path exists and contains any files: (I think) C:program files (x86)openvpnbin
Specifically, I’m looking for the tapinstall.exe binary. If it doesn’t it might be getting cleaned up if you exit the installer. If this is the case, try running the installation again but not exiting the installer after it pukes.
If you can get an admin CLI with the tapinstall binary present, from openvpnbin, run the following command and post the output:
tapinstall install ..driveroemwin2k.inf tap0901
Re: TAP driver on Windows x64
Post by sjoller » Tue Dec 28, 2010 9:38 pm
Thanks for replying.
After a looong time trying to install the TAP driver, the installation pops an error message saying that «An error occured installing the TAP device driver». After accepting this, the installation finishes withour further errors.
This is what is logged:
As you might have guessed from above, everything besides the driver is installed as it should. Manually running the tabinstall as you describe, gives me yet another «Unknown device» in Network adapters, but fails.
I sometimes find that Windows have a hard time accepting paths containing spaces (when installing from the DOS prompt), which is why I initially tried to place the driver files in a properly named folder, at the very root of my system drive and install it manually from there — but to no avail.
Today, I tried to install v2.1.4 on a Windows 7 x64 box at work, and it installed flawlessly. The two boxes have pretty much the same software on them, but varies in hardware. I don’t think it’s a hardware problem, so the only major difference I can think of, is that I’m running Ultimate at home, and the work box has a OEM Home Premium.
Regards
Mads Jensen
Re: TAP driver on Windows x64
Post by sjoller » Tue Dec 28, 2010 10:50 pm
I tried to update the driver using Windows device manager, and it told me that the driver file was locked due to being used by another process. Googling for a solution to this problem yielded no solution (quelle surprise), but the the universal Windows problem fixer solution (A.K.A. reboot) released the lock on the file, and I was then able to install the driver with success.
I feel a little silly for not trying this in the first place, but atleast thing are working for me again.
Regards
Mads Jensen.
Re: Installing TAP driver on Windows x64 fails [solved]
Post by Goykie » Thu Oct 06, 2011 9:50 am
The new OpenVPN versions work on 64 bit.
Uninstall all Open VPN. Restart PC. Follow link http://openvpn.net/index.php/open-source/downloads.html and install the newest version. (I installed version 2.1.4 and it works)
Btw when you uninstall you don’t have to delete your config folders.
Re: Installing TAP driver on Windows x64 fails [solved]
Post by unkim » Sat Apr 14, 2012 4:34 pm
i have the same problem of the tap adapter in win7.
but!
i have 2 computers both with win7 (one is 100%legal bought in europe, and the other one is bought is china so who knows. )
curiously, i dont have any problem installing the adapter on the chinese one, but i have it in the legal one.
so must to be a software issue right?
my laptop asus A53S is the one which dont allow me to install the adapter.
thanks in advance!
ps: why the thread shows solved??
Re: Installing TAP driver on Windows x64 fails [solved]
Post by tazz602 » Wed Oct 03, 2012 3:27 pm
I don’t know why this was marked as solved because no one answered the question.
The issue is simple — you need to run the Add TAP as Administrator — right click on the menu option and select «Run as Administrator» and it should work.
Re: Installing TAP driver on Windows x64 fails [solved]
Post by razvezlo » Tue Jan 08, 2013 12:20 am
maybe — will be fixed / changed in further releases, but — for now:
Источник
Содержание
- OpenVPN Support Forum
- Installing TAP driver on Windows x64 fails [solved]
- Installing TAP driver on Windows x64 fails [solved]
- Re: TAP driver on Windows x64
- Re: TAP driver on Windows x64
- Re: TAP driver on Windows x64
- Re: Installing TAP driver on Windows x64 fails [solved]
- Re: Installing TAP driver on Windows x64 fails [solved]
- Re: Installing TAP driver on Windows x64 fails [solved]
- Re: Installing TAP driver on Windows x64 fails [solved]
- OpenVPN Support Forum
- Error occurred Installing TAP driver
- Error occurred Installing TAP driver
- Centos
- OpenVPN Support Forum
- TAP installer failed on Windows 10 1709 with 2.4.6
- TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
OpenVPN Support Forum
Community Support Forum
Installing TAP driver on Windows x64 fails [solved]
Installing TAP driver on Windows x64 fails [solved]
Post by sjoller » Mon Dec 27, 2010 11:27 am
I’m having trouble installing OpenVPN — the TAP driver simply refuses to install.
I’ve tried 5 different versions of the installer — including v2.1 RC19 which, according to a Google search, seems to be everyones solution.
I’ve tried v2.1.3, which supposedly should have the driver signing solved, v2.1.1, v2.1.4 and even v2.2 beta5 — all run as administrator.
I’ve tried running the installers in compability mode set to Vista, aswell.
I’ve tried downloading the x64 driver (tap0801), from openvpn.se, and installing it manually (from a dos prompt, run as administrator, from a destination folder that isn’t named with troublesome characters like space), and between the installs, i’ve even made sure to uninstall the «unknown» TAP network adaptor, the installations leaves behind.
I’ve tried extracting the driver (tap0901) from the installer and manually install it, using same procedure as above.
. I’m fresh out of ideas on how to get OpenVPN running on Windows 7 Ultimate x64, please help.
Regards
Mads Jensen
Re: TAP driver on Windows x64
Post by gladiatr72 » Mon Dec 27, 2010 5:21 pm
I’m not a Windows Guy(tm), but what sort of errors are being emitted when the installation fails?
After the error, is there anything left in the installation target directory?
Check if the following path exists and contains any files: (I think) C:program files (x86)openvpnbin
Specifically, I’m looking for the tapinstall.exe binary. If it doesn’t it might be getting cleaned up if you exit the installer. If this is the case, try running the installation again but not exiting the installer after it pukes.
If you can get an admin CLI with the tapinstall binary present, from openvpnbin, run the following command and post the output:
tapinstall install ..driveroemwin2k.inf tap0901
Re: TAP driver on Windows x64
Post by sjoller » Tue Dec 28, 2010 9:38 pm
Thanks for replying.
After a looong time trying to install the TAP driver, the installation pops an error message saying that «An error occured installing the TAP device driver». After accepting this, the installation finishes withour further errors.
This is what is logged:
As you might have guessed from above, everything besides the driver is installed as it should. Manually running the tabinstall as you describe, gives me yet another «Unknown device» in Network adapters, but fails.
I sometimes find that Windows have a hard time accepting paths containing spaces (when installing from the DOS prompt), which is why I initially tried to place the driver files in a properly named folder, at the very root of my system drive and install it manually from there — but to no avail.
Today, I tried to install v2.1.4 on a Windows 7 x64 box at work, and it installed flawlessly. The two boxes have pretty much the same software on them, but varies in hardware. I don’t think it’s a hardware problem, so the only major difference I can think of, is that I’m running Ultimate at home, and the work box has a OEM Home Premium.
Regards
Mads Jensen
Re: TAP driver on Windows x64
Post by sjoller » Tue Dec 28, 2010 10:50 pm
I tried to update the driver using Windows device manager, and it told me that the driver file was locked due to being used by another process. Googling for a solution to this problem yielded no solution (quelle surprise), but the the universal Windows problem fixer solution (A.K.A. reboot) released the lock on the file, and I was then able to install the driver with success.
I feel a little silly for not trying this in the first place, but atleast thing are working for me again.
Regards
Mads Jensen.
Re: Installing TAP driver on Windows x64 fails [solved]
Post by Goykie » Thu Oct 06, 2011 9:50 am
The new OpenVPN versions work on 64 bit.
Uninstall all Open VPN. Restart PC. Follow link http://openvpn.net/index.php/open-source/downloads.html and install the newest version. (I installed version 2.1.4 and it works)
Btw when you uninstall you don’t have to delete your config folders.
Re: Installing TAP driver on Windows x64 fails [solved]
Post by unkim » Sat Apr 14, 2012 4:34 pm
i have the same problem of the tap adapter in win7.
but!
i have 2 computers both with win7 (one is 100%legal bought in europe, and the other one is bought is china so who knows. )
curiously, i dont have any problem installing the adapter on the chinese one, but i have it in the legal one.
so must to be a software issue right?
my laptop asus A53S is the one which dont allow me to install the adapter.
thanks in advance!
ps: why the thread shows solved??
Re: Installing TAP driver on Windows x64 fails [solved]
Post by tazz602 » Wed Oct 03, 2012 3:27 pm
I don’t know why this was marked as solved because no one answered the question.
The issue is simple — you need to run the Add TAP as Administrator — right click on the menu option and select «Run as Administrator» and it should work.
Re: Installing TAP driver on Windows x64 fails [solved]
Post by razvezlo » Tue Jan 08, 2013 12:20 am
maybe — will be fixed / changed in further releases, but — for now:
Источник
OpenVPN Support Forum
Community Support Forum
Error occurred Installing TAP driver
Post by HardOtaku12 » Thu Jan 16, 2020 11:54 am
I always get this problem I have tried many different ways to fix this. but None worked!
when I try to install OpenVPN -2.4.8-I602-Win7,(I use windows 7 because i have Windows 8.1) , I always gets this error, after,
Caching service states
Stopping OpenVPN services.
Output folder: C:Program FilesOpenVPNbin
Extract: openvpn.exe
Output folder: C:Program FilesOpenVPNdoc
Extract: INSTALL-win32.txt
Extract: openvpn.8.html
Output folder: C:Program FilesOpenVPNbin
Extract: openvpnserv.exe
Output folder: C:Program FilesOpenVPNconfig
Output folder: C:Program FilesOpenVPNsample-config
Extract: sample.ovpn
Extract: client.ovpn
Extract: server.ovpn
Create folder: C:Program FilesOpenVPNlog
Installing OpenVPN Interactive Service.
Installing OpenVPN Legacy Service.
Output folder: C:UsersPCADMI
1AppDataLocalTemp
Extract: tap-windows.exe
Installing TAP (may need confirmation). rem Add a new TAP virtual ethernet adapter
C:Program FilesTAP-Windowsbin>»C:Program FilesTAP-Windowsbintapinstall.ex
e» install «C:Program FilesTAP-WindowsdriverOemVista.inf» tap0901
tapinstall.exe failed.
C:Program FilesTAP-Windowsbin>pause
Press any key to continue . . .
I have tried many ways in fixing this like,
editing Regedit, booting in Safe mode, and etc.
Please reply if you know the answer to my problem!! , btw I install TAP driver so I can install VPN’s
Источник
Centos
Столкнулся с неожиданной проблемой при установке клиента популярной реализации vpn. Не устанавливался openvpn клиент на Windows 10, выдавая ошибку установки TAP интерфейса: «An error occurred installing the TAP device driver«.
Ошибка установки openvpn на Windows 10 выглядела следующим образом. Инсталятор после выбора дефолтных настроек задумывается на несколько минут и в итоге выдает ошибку:
При этом сам клиент openvpn успешно устанавливается. Можно запустить GIU , но ясное дело, подключиться к серверу openvpn не получится, так как в системе не появляется TAP адаптера. В интернете нашел много советов по данной проблеме, но мне ни один не помог. Перечислю их, может вам поможет что-то из этого:
- Запустить скрипт на добавление TAP интерфейса — C:Program FilesTAP-Windowsbinaddtap.bat. У меня он так же не отрабатывал. Висел несколько минут, потом выдавал ошибку.
- Зайти в Пуск -> TAP Windows ->Add a new TAP virtual ethernet adapter. Это тоже не помогло.
- Повторить установку openvpn с выключенным антивирусом или защитником windows.
Два первых действия нужно выполнять от администратора. С помощью них можно добавить несколько tap адаптеров в систему, чтобы одновременно поднимать несколько openvpn туннелей.
После того, как ничего из предложенного не подошло, я крепко призадумался. Openvpn я использую постоянно. Ставил его на разные системы десятки раз и всегда все проходило успешно, либо проблема быстро решалась. Тут быстрого и простого решения не получалось.
Помогло в итоге вот что. Я открыл диспетчер устройств и посмотрел на сетевые адаптеры. В списке был TAP-Windows Adapter V9 , что намекало на то, что все должно работать. Но не работало. В панели управления в списке адаптеров TAP адаптера не было.
Я включил отображение скрытых устройств и увидел там же в сетевых адаптерах неизвестное устройство (unknown device). Открыл у него вкладку Сведения. Путь к экземпляру устройства был следующий — ROOT NET 000. Я нажал обновить драйвер для этого устройства и указал, что он должен быть найден автоматически. После этого устройство получило название TAP-Windows Adapter V9 #2 и в панели управления появился TAP адаптер.
После этого Openvpn заработал. Я смог подключиться к серверу и организовать туннель. После того, как я удалил openvpn на этой же системе и установил заново, все прошло без ошибок с первого раза. Появился только один TAP-Windows Adapter V9 . Проверил еще на парочке тестовых виртуальных машин. Тоже все прошло без ошибок, так что не смог собрать актуальные скрины по проблеме, а сразу их не сделал.
Источник
OpenVPN Support Forum
Community Support Forum
TAP installer failed on Windows 10 1709 with 2.4.6
TAP installer failed on Windows 10 1709 with 2.4.6
Post by Hugo1 » Wed Apr 25, 2018 7:07 pm
Installed OpenVP 2.4.6
«An error occurred installing the TAP device driver.»
Windows:
Device-Manager (Error-Code 52)
Please Help me.
Thanks
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by Tom7320 » Wed Apr 25, 2018 8:35 pm
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.
Is there anything else I coud try?
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by mhab12 » Wed Apr 25, 2018 11:39 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by Tom7320 » Thu Apr 26, 2018 7:02 am
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.
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by samuli » Thu Apr 26, 2018 3:45 pm
You’re almost certainly having the same issue as here. If you can, please post your setupapi.dev.log files to that ticket so that we can be sure.
The easiest way to work around this problem is to install tap-windows6 9.21.2 from here while we figure out the proper solution.
—
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by samuli » Thu Apr 26, 2018 7:02 pm
—
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by Tom7320 » Thu Apr 26, 2018 7:10 pm
You’re almost certainly having the same issue as here. If you can, please post your setupapi.dev.log files to that ticket so that we can be sure.
The easiest way to work around this problem is to install tap-windows6 9.21.2 from here while we figure out the proper solution.
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by Tom7320 » Thu Apr 26, 2018 7:20 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by mhab12 » Thu Apr 26, 2018 7:56 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by samuli » Fri Apr 27, 2018 6:52 am
—
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by Tom7320 » Fri Apr 27, 2018 7:11 am
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by Tom7320 » Wed May 02, 2018 4:55 am
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by funmaker » Sun Jul 08, 2018 1:20 am
This worked for me:
open cmd prompt via Start Menu, ‘Windows System’, right click on CMD (DOS prompt), More, then select Run as Administrator
on a command line type:
bcdedit.exe /set nointegritychecks on
This turns off integrity checking of unsigned driver — allows unsigned drivers to be installed
— run / install your software, openVPN TAP software
Test and then run the following to turn integrity checking back on
bcdedit.exe /set nointegritychecks off
This is a permanent fix, not temporary for this session.
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by kfnoho » Fri Sep 21, 2018 8:45 pm
I hopefully tried the last suggested solution. Sigh. It failed again. Here are the contents of the Installation Window:
We are running on a 64-bit system.
Output folder: C:Program FilesTAP-Windowsbin
Extract: tapinstall.exe. 100%
Output folder: C:Program FilesTAP-Windowsdriver
Extract: OemVista.inf. 100%
Extract: tap0901.cat. 100%
Extract: tap0901.sys. 100%
Delete file: C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-WindowsUtilitiesAdd a new TAP virtual ethernet adapter.lnk
Delete file: C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-WindowsUtilitiesDelete ALL TAP virtual ethernet adapters.lnk
Remove folder: C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-WindowsUtilities
Remove folder: C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-Windows
Create folder: C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-WindowsUtilities
Create shortcut: C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-WindowsUtilitiesAdd a new TAP virtual ethernet adapter.lnk
Create shortcut: C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-WindowsUtilitiesDelete ALL TAP virtual ethernet adapters.lnk
Output folder: C:Program FilesTAP-Windows
Extract: license.txt. 100%
Extract: icon.ico. 100%
tapinstall.exe hwids returned: 0
TAP update (tap0901) (May require confirmation)
Updating drivers for tap0901 from C:Program FilesTAP-WindowsdriverOemVista.inf.
UpdateDriverForPlugAndPlayDevices failed, GetLastError=1460
tapinstall.exe failed.
tapinstall.exe returned: 2
tapinstall.exe cumulative status: 2
Created uninstaller: C:Program FilesTAP-WindowsUninstall.exe
Completed
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by ghost887 » Wed Sep 26, 2018 9:40 am
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by ENG900PM » Tue Oct 09, 2018 10:04 am
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.
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by ENG900PM » Tue Oct 09, 2018 10:52 am
I just solved the problem I was having. Although re-reading this post you may be having a different problem.
Anyway on my OpenVPN client machine I ran this command «As Administrator»:
C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-WindowsUtilitiesAdd a new TAP virtual ethernet adapter.lnk
I was trying to run it on my OpenVPN server machine. However it already had a properly functioning TAP virtual ethernet adapter.
Maybe this helps.
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by brenakvpn » Tue Nov 06, 2018 7:09 pm
This is happening for me too. Disabling SecureBoot isn’t really an option for me.
I’ve uninstalled and re-installed multiple times under different scenarios.
I’ve tried it with SecureBoot disabled.
I’ve tried it with SecureBoot disabled and driver integrity check turned off.
I’ve ran it as administrator.
I’ve tried to manually install.
Nothing works. It always locks up, and times out about 4 minutes later.
I only have windows defender for AV. Its a new laptop with a fresh install of windows 10 version 1803 Build 17134.345
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by burntoc » Tue Dec 04, 2018 5:39 am
This worked for me:
open cmd prompt via Start Menu, ‘Windows System’, right click on CMD (DOS prompt), More, then select Run as Administrator
on a command line type:
bcdedit.exe /set nointegritychecks on
This turns off integrity checking of unsigned driver — allows unsigned drivers to be installed
— run / install your software, openVPN TAP software
Test and then run the following to turn integrity checking back on
bcdedit.exe /set nointegritychecks off
This is a permanent fix, not temporary for this session.
Источник
Содержание
- Centos
- Почему не устанавливается драйвер для penvpn(tap-windows)?
- OpenVPN Support Forum
- TAP installer failed on Windows 10
- TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10 TEMP FIX
- Re: TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10
- Re: TAP installer failed on Windows 10
- OpenVPN Support Forum
- TAP installer failed on Windows 10 1709 with 2.4.6
- TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
- Re: TAP installer failed on Windows 10 1709 with 2.4.6
Centos
Столкнулся с неожиданной проблемой при установке клиента популярной реализации vpn. Не устанавливался openvpn клиент на Windows 10, выдавая ошибку установки TAP интерфейса: «An error occurred installing the TAP device driver«.
Ошибка установки openvpn на Windows 10 выглядела следующим образом. Инсталятор после выбора дефолтных настроек задумывается на несколько минут и в итоге выдает ошибку:
Два первых действия нужно выполнять от администратора. С помощью них можно добавить несколько tap адаптеров в систему, чтобы одновременно поднимать несколько openvpn туннелей.
После того, как ничего из предложенного не подошло, я крепко призадумался. Openvpn я использую постоянно. Ставил его на разные системы десятки раз и всегда все проходило успешно, либо проблема быстро решалась. Тут быстрого и простого решения не получалось.
Я включил отображение скрытых устройств и увидел там же в сетевых адаптерах неизвестное устройство (unknown device). Открыл у него вкладку Сведения. Путь к экземпляру устройства был следующий — ROOT NET 000. Я нажал обновить драйвер для этого устройства и указал, что он должен быть найден автоматически. После этого устройство получило название TAP-Windows Adapter V9 #2 и в панели управления появился TAP адаптер.
Источник
Почему не устанавливается драйвер для penvpn(tap-windows)?
Пытаюсь на windows 7 поставить openvpn client, при установке возникает ошибка «error occurred installing the TAP device driver»
Лог установщика:
We are running on a 64-bit system.
Output folder: C:Program FilesTAP-Windowsbin
Extract: devcon.exe. 100%
Output folder: C:Program FilesTAP-Windowsdriver
Extract: OemWin2k.inf. 100%
Extract: tap0901.cat. 100%
Extract: tap0901.sys. 100%
Output folder: C:Program FilesTAP-Windows
Extract: license.txt. 100%
Extract: icon.ico. 100%
devcon.exe hwids returned: 0
TAP install (tap0901) (May require confirmation)
Device node created. Install is complete when drivers are installed.
Updating drivers for tap0901 from C:Program FilesTAP-WindowsdriverOemWin2k.inf.
devcon.exe failed.
devcon.exe returned: 2
devcon.exe cumulative status: 2
Created uninstaller: C:Program FilesTAP-WindowsUninstall.exe
Completed
Предложите как это можно решить(само собой без переустановки винды), где можно посмотреть причину(где логи, Лебовски?).
Т.е. похоже все дело из-за подписи. Надо подумать как заставить драйвер работать в обычном режиме(в нем подпись проверяется, драйвер соответственно не работает и TAP адаптер среди сетевых интерфейсов в центре управления сетями пропал). Вроде можно самим подписать.
[HKEY_LOCAL_MACHINESYSTEMControlSet001ControlNetwork<4d36e972-e325-11ce-bfc1-08002be10318><54e4a266-cf20-4c30-9a05-a7fb94045197>Connection]
«DefaultNameResourceId»=dword:0000070a
«DefaultNameIndex»=dword:00000003
«Name»=»Подключение по локальной сети 3»
«PnpInstanceID»=»ROOTNET000»
«MediaSubType»=dword:00000000
Источник
OpenVPN Support Forum
Community Support Forum
TAP installer failed on Windows 10
TAP installer failed on Windows 10
Post by hermy9 » Sun Nov 27, 2016 2:40 pm
Hi, I hope that I am at the right place.
Installing Openvpn 2.3.13 failed on win10 with this error message, after two successful installations on other win10 systems.
«An error occurred installing the TAP device driver.»
Installing TAP separately fails with the same error message. In addition, the log shows this sequence at the end:
What is going wrong here? What does the error code mean?
I tried several things:
— Openvpn connection to my external server is not possible
— Avira Services deactivated
— Windows firewall deactivated
— reboot
The error code cannot be found with Google.
Re: TAP installer failed on Windows 10
Post by TinCanTech » Mon Nov 28, 2016 1:59 pm
Re: TAP installer failed on Windows 10
Post by hermy9 » Mon Nov 28, 2016 10:18 pm
Re: TAP installer failed on Windows 10
Post by hermy9 » Sun Dec 04, 2016 8:31 am
In the meantime, I spent hours and tried a lot of things, no success up to now.
None of them can be attributed to TAP-Windows Adapter V9. I followed the instruction given by the link above (which is not very clear), with no success.
On my other win10 system, I see 17 entries, and entry 0015 can be attributed to the TAP driver. There, all works fine.
So, my question is still the same. What is going wrong when installing the TAP driver?
Last lines of C:WindowsINFsetupapi.dev.log follow here, after having done this:
— uninstalling TAP and Openvpn using uninstall.exe for both
— cleaning c:BenutzerAdministratorAppDataLocalTemp
Re: TAP installer failed on Windows 10
Post by Renske » Tue Oct 17, 2017 2:00 pm
I have the same problem installing the TAP driver. I get the same error messages as mentioned by hermy9. It appears to be some problem with certificates:
From setupapi.dev.log:
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
I tried uninstalling, rebooting and installing (as administrator) several times, both OpenVPN and TAP separately, but I can’t get it to work. My colleagues have exactly the same computer and they don’t have any problems.
hermy9, did you ever manage to solve this problem? Does anyone else have any suggestions on what to try?
TinCanTech, where should I right-click for the option that you mentioned?
Re: TAP installer failed on Windows 10
Post by TinCanTech » Tue Oct 17, 2017 4:59 pm
Must be run as administrator.
Re: TAP installer failed on Windows 10
Post by Renske » Thu Oct 19, 2017 7:36 am
Thanks for your reply TinCanTech. Unfortunately it is not working. I ran it as administrator, but I get the following error message:
«C:Windowssystem32>rem Add a new TAP virtual ethernet adapter
C:Windowssystem32>»C:Program FilesTAP-Windowsbintapinstall.exe» install «C:Program FilesTAP-WindowsdriverOemVista.inf» tap0901
Device node created. Install is complete when drivers are installed.
Updating drivers for tap0901 from C:Program FilesTAP-WindowsdriverOemVista.inf.
UpdateDriverForPlugAndPlayDevices failed, GetLastError=-536870330
tapinstall.exe failed.»
Do you have any other suggestions on what I could try?
Re: TAP installer failed on Windows 10
Post by TinCanTech » Thu Oct 19, 2017 10:52 am
Re: TAP installer failed on Windows 10
Post by kekster » Thu Apr 19, 2018 6:38 am
Re: TAP installer failed on Windows 10
Post by TinCanTech » Thu Apr 19, 2018 11:55 am
Re: TAP installer failed on Windows 10
Post by Renske » Thu Apr 19, 2018 2:17 pm
Re: TAP installer failed on Windows 10
Post by tojieb » Mon May 06, 2019 3:57 am
Re: TAP installer failed on Windows 10 TEMP FIX
Post by unknown » Thu Oct 10, 2019 8:34 am
hey, found a temp workaround for this issue, not sure if it will work for you, but it did for me, here we go.
you should receive a notification saying that windows found and updated the driver software, and it will no longer show up as an unknown device on the network adapters tab, make sure you restart Open VPN if it was running, and Voila!!
Re: TAP installer failed on Windows 10
Post by adreyfus » Fri Nov 15, 2019 2:15 pm
Same error for me. The solutions proposed above did not work.
Re: TAP installer failed on Windows 10
Post by rejerh » Fri Apr 10, 2020 3:46 am
I am having the same problem on any of the version of TAP I could find (9.21, 9.22, 9.24)
This is very frustrating. Nothing I could find in this thread helped me resolve this issue.
Has anyone found a robust fix?
Re: TAP installer failed on Windows 10
Post by Bantic » Tue Jun 15, 2022 7:50 am
I fixed problem with installing adapter ( this is one of many solution becouse reason may be more then one)
After that intall as administrator TAP Adapter once agian.
Re: TAP installer failed on Windows 10
Post by sid11 » Sun Sep 12, 2022 10:57 pm
Unfortunately, none of the suggestions worked.
Got the same issue, here is my experience.
1. Running Windows 7, Ultimate edition, x64;
2. OpenVPN 2.5.3 gets installed fine;
however, setupapi.dev.log contains following:
sig: <_verify_file_signature>15:18:46.274
sig: Key = oemvista.inf
sig: FilePath = c:program filestap-windowsdriveroemvista.inf
sig: Catalog = c:program filestap-windowsdrivertap0901.cat
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
sig: <_verify_file_signature exit(0x800b0109)>15:18:46.331
sig: <_verify_file_signature>15:18:46.331
sig: Key = oemvista.inf
sig: FilePath = c:program filestap-windowsdriveroemvista.inf
sig: Catalog = c:program filestap-windowsdrivertap0901.cat
sig: Success: File is signed in Authenticode(tm) catalog.
sig: Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
sig: <_verify_file_signature exit(0xe0000241)>15:18:46.351
(same applies to wintun)
So tap driver isn’t being recognized by the system (go to device manager/check network section/see tap driver with yellow triangle on the icon:
«This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)»
3. To resolve the tap driver challenges, tried:
3.1 Full system cleanup (delete all the drivers, openvpn installs, tap installer/reinstalled everything w/ and w/o tap installer)
(i still do wander why other drivers may interfere with the install from openvpn, but that’s a diff story)
3.2 bcedit experiments & windows reboot with «disable driver signature enforcement»
3.3 manually imported certificates (via certmgr & mmc snap in for the local computer; to root & trusted publisher)
3.4 signed driver myself & used self-signed certificate
After all the experiments, this is what i came down to:
There seem to be two issues that the latest OpenVPN installer has;
and latest tap driver installer has;
(and they seem to have it (at least) for the past
8-10 releases (went as far as 9.9 with tap installer; and 2.0 with openvpn))
Direction that (in theory) could work:
If one updates registry; and adds following record to the driver:
«ComponentId» with the value «tap0901»:
It makes «Network card» to be visible to openVPN app;
So error from «hey, you have no tap devices out there»:
Turns into «hey, you have tap device there, but it’s busy».
(chances are, OpenVPN queries registry directly, bypassing Windows API; which is why it makes a difference)
Alternative, is to provide chained certificate for the software (that’s question to openvpn devs) that’s been properly validated and considered to be valid by Microsoft.
That way, digital signature can be overrulled with bcedits/and/or/F8/disable driver signature enforcement):
And certs is legit:
And we’d be good.
Источник
Ошибка установки openvpn на Windows 10 выглядела следующим образом. Инсталлятор после выбора дефолтных настроек задумывается на несколько минут и в итоге выдает ошибку:
При этом сам клиент openvpn успешно устанавливается. Можно запустить GIU, но ясное дело, подключиться к серверу openvpn не получится, так как в системе не появляется TAP адаптера. В интернете нашел много советов по данной проблеме, но мне ни один не помог. Перечислю их, может вам поможет что-то из этого:
Два первых действия нужно выполнять от администратора. С помощью них можно добавить несколько tap адаптеров в систему, чтобы одновременно поднимать несколько openvpn туннелей.
После того, как ничего из предложенного не подошло, я крепко призадумался. Openvpn я использую постоянно. Ставил его на разные системы десятки раз и всегда все проходило успешно, либо проблема быстро решалась. Тут быстрого и простого решения не получалось.
Помогло в итоге вот что. Я открыл диспетчер устройств и посмотрел на сетевые адаптеры. В списке был TAP-Windows Adapter V9, что намекало на то, что все должно работать. Но не работало. В панели управления в списке адаптеров TAP адаптера не было.
После этого Openvpn заработал. Я смог подключиться к серверу и организовать туннель. После того, как я удалил openvpn на этой же системе и установил заново, все прошло без ошибок с первого раза. Появился только один TAP-Windows Adapter V9. Проверил еще на парочке тестовых виртуальных машин. Тоже все прошло без ошибок, так что не смог собрать актуальные скрины по проблеме, а сразу их не сделал.
Надеюсь моя инфа будет кому-нибудь полезной при разборе такой же ошибки при установке openvpn client на Windows 10. Я в русскоязычном интернете не видел этой информации. Моя статья по установке и настройке openvpn сервера.
Источник
OpenVPN Support Forum
Community Support Forum
TAP installer failed on Windows 10 1709 with 2.4.6
TAP installer failed on Windows 10 1709 with 2.4.6
Post by Hugo1 » Wed Apr 25, 2018 7:07 pm
Installed OpenVP 2.4.6
«An error occurred installing the TAP device driver.»
Windows:
Device-Manager (Error-Code 52)
Please Help me.
Thanks
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by Tom7320 » Wed Apr 25, 2018 8:35 pm
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.
Is there anything else I coud try?
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by mhab12 » Wed Apr 25, 2018 11:39 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by Tom7320 » Thu Apr 26, 2018 7:02 am
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.
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by samuli » Thu Apr 26, 2018 3:45 pm
You’re almost certainly having the same issue as here. If you can, please post your setupapi.dev.log files to that ticket so that we can be sure.
The easiest way to work around this problem is to install tap-windows6 9.21.2 from here while we figure out the proper solution.
—
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by samuli » Thu Apr 26, 2018 7:02 pm
—
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by Tom7320 » Thu Apr 26, 2018 7:10 pm
You’re almost certainly having the same issue as here. If you can, please post your setupapi.dev.log files to that ticket so that we can be sure.
The easiest way to work around this problem is to install tap-windows6 9.21.2 from here while we figure out the proper solution.
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by Tom7320 » Thu Apr 26, 2018 7:20 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by mhab12 » Thu Apr 26, 2018 7:56 pm
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by samuli » Fri Apr 27, 2018 6:52 am
—
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by Tom7320 » Fri Apr 27, 2018 7:11 am
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by Tom7320 » Wed May 02, 2018 4:55 am
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by funmaker » Sun Jul 08, 2018 1:20 am
This worked for me:
open cmd prompt via Start Menu, ‘Windows System’, right click on CMD (DOS prompt), More, then select Run as Administrator
on a command line type:
bcdedit.exe /set nointegritychecks on
Test and then run the following to turn integrity checking back on
bcdedit.exe /set nointegritychecks off
This is a permanent fix, not temporary for this session.
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by kfnoho » Fri Sep 21, 2018 8:45 pm
I hopefully tried the last suggested solution. Sigh. It failed again. Here are the contents of the Installation Window:
We are running on a 64-bit system.
Output folder: C:Program FilesTAP-Windowsbin
Extract: tapinstall.exe. 100%
Output folder: C:Program FilesTAP-Windowsdriver
Extract: OemVista.inf. 100%
Extract: tap0901.cat. 100%
Extract: tap0901.sys. 100%
Delete file: C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-WindowsUtilitiesAdd a new TAP virtual ethernet adapter.lnk
Delete file: C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-WindowsUtilitiesDelete ALL TAP virtual ethernet adapters.lnk
Remove folder: C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-WindowsUtilities
Remove folder: C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-Windows
Create folder: C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-WindowsUtilities
Create shortcut: C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-WindowsUtilitiesAdd a new TAP virtual ethernet adapter.lnk
Create shortcut: C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-WindowsUtilitiesDelete ALL TAP virtual ethernet adapters.lnk
Output folder: C:Program FilesTAP-Windows
Extract: license.txt. 100%
Extract: icon.ico. 100%
tapinstall.exe hwids returned: 0
TAP update (tap0901) (May require confirmation)
Updating drivers for tap0901 from C:Program FilesTAP-WindowsdriverOemVista.inf.
UpdateDriverForPlugAndPlayDevices failed, GetLastError=1460
tapinstall.exe failed.
tapinstall.exe returned: 2
tapinstall.exe cumulative status: 2
Created uninstaller: C:Program FilesTAP-WindowsUninstall.exe
Completed
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by ghost887 » Wed Sep 26, 2018 9:40 am
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by ENG900PM » Tue Oct 09, 2018 10:04 am
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.
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by ENG900PM » Tue Oct 09, 2018 10:52 am
I just solved the problem I was having. Although re-reading this post you may be having a different problem.
Anyway on my OpenVPN client machine I ran this command «As Administrator»:
C:ProgramDataMicrosoftWindowsStart MenuProgramsTAP-WindowsUtilitiesAdd a new TAP virtual ethernet adapter.lnk
I was trying to run it on my OpenVPN server machine. However it already had a properly functioning TAP virtual ethernet adapter.
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by brenakvpn » Tue Nov 06, 2018 7:09 pm
This is happening for me too. Disabling SecureBoot isn’t really an option for me.
I’ve uninstalled and re-installed multiple times under different scenarios.
I’ve tried it with SecureBoot disabled.
I’ve tried it with SecureBoot disabled and driver integrity check turned off.
I’ve ran it as administrator.
I’ve tried to manually install.
Nothing works. It always locks up, and times out about 4 minutes later.
I only have windows defender for AV. Its a new laptop with a fresh install of windows 10 version 1803 Build 17134.345
Re: TAP installer failed on Windows 10 1709 with 2.4.6
Post by burntoc » Tue Dec 04, 2018 5:39 am
This worked for me:
open cmd prompt via Start Menu, ‘Windows System’, right click on CMD (DOS prompt), More, then select Run as Administrator
on a command line type:
bcdedit.exe /set nointegritychecks on
Test and then run the following to turn integrity checking back on
bcdedit.exe /set nointegritychecks off
This is a permanent fix, not temporary for this session.
Источник
Go to Windscribe
r/Windscribe
Windscribe is a VPN desktop application and VPN/proxy browser extension that work together to block ads, trackers, restore access to blocked content and help you safeguard your privacy online. windscribe.com
Members
Online
•
«An error occurred installing the TAP device driver: 2» how to fix?
I’ve just got the «An error occurred installing the TAP device driver: 2» message while updating windscribe but the app deleted itself instead and while trying to fresh install i keep getting the same message at around 55% installed, does anyone know how to fix it?
Адаптер TAP-Windows — это сетевой драйвер, с помощью которого службы VPN могут позволить вашему компьютеру подключаться к серверам VPN. К сожалению, при подключении к VPN вы можете получить сообщение об ошибке:
В этой системе не установлены адаптеры TAP-Windows.
Подобно Все адаптеры TAP-Windows в этой системе в настоящее время используются. ошибка, это не критическая ошибка, и в сообщении точно указывается, что не так с подключением.
Вы можете устранить эту проблему с драйвером TAP в три этапа. В руководстве по устранению неполадок перечисляются эти этапы и объясняется, как их выполнять.
- Перезагрузите адаптер TAP-Windows.
- Переустановите драйверы TAP-Windows.
- Создайте новый адаптер TAP-Windows.
Ниже приведено полное руководство. Я советую вам следовать инструкциям в том порядке, в котором я их здесь перечислил.
1]Перезагрузите адаптер TAP-Windows.
Рекомендуемый способ исправить эту ошибку драйвера TAP — перезапустить адаптер TAP. Для этого выполните следующие действия:
Щелкните правой кнопкой мыши значок сети на панели задач и выберите Откройте настройки сети и Интернета.
Найдите адаптер TAP на этом экране. Они называются по-разному в зависимости от VPN, поэтому вы можете искать только адаптер или соединение с КРАН в его описании.
Щелкните правой кнопкой мыши TAP и нажмите Запрещать вариант.
После отключения сетевого адаптера снова щелкните его правой кнопкой мыши и переименуйте.
2]Переустановите драйверы TAP-Windows.
Если вы перезапускаете сетевой адаптер TAP и по-прежнему получаете сообщение об ошибке, вам следует переустановить драйверы TAP. Сделать это можно несколькими способами.
Во-первых, вы можете удалить программное обеспечение VPN и переустановить его снова. Убедитесь, что вы перезагрузили компьютер после удаления VPN.
Когда машина снова включится, установите программное обеспечение VPN, и установка, скорее всего, будет идти с драйверами TAP.
нажмите Клавиша Windows + R комбинация, тип devmgmt.msc в диалоговом окне «Выполнить» и нажмите ENTER.
В диспетчере устройств разверните Сетевые адаптеры раздел и найдите адаптер TAP-Windows, указанный под ним.
Щелкните драйвер правой кнопкой мыши и выберите Удалить устройство вариант.
Завершите процесс удаления, следуя инструкциям на экране.
После удаления драйвера запустите свой VPN-клиент, и он может попросить вас установить отсутствующие сетевые драйверы TAP.
Некоторые VPN сообщают вам только об отсутствии драйвера. В этом случае вам необходимо загрузить драйвер из Интернета или загрузить последнюю версию VPN-клиента.
Вы также можете загрузить программное обеспечение драйвера TAP-Windows и вручную установить его на свой компьютер. Если вы не знаете, где скачать драйверы или даже как их использовать, это руководство станет отличной отправной точкой.
3]Создайте новый адаптер TAP-Windows
Windows сообщает, что не может найти адаптеры TAP-Windows в вашей системе. Самый простой способ — создать новый адаптер TAP-Windows.
Windows создает новый адаптер TAP-Windows, когда вы создаете гипермашину или подключаетесь к службе VPN.
Также обратите внимание, что у вас может быть активен только один адаптер TAP-Windows одновременно.