Hi,

Il 01/11/19 23:40, Ton van Vliet ha scritto:
> Thanks for the info.
> 
> A quick reply for now:
> 
> On 01-11-19 19:28, Samuli Seppänen wrote:
>> Hi,
>>
>> Il 01/11/19 18:58, Ton van Vliet ha scritto:
>>> Hi,
>>>
>>> A sincere 'Thank You' to all developers for their continuous work done
>>> on OpenVPN !
>>>
>>> Both the 2.4.8-I601-Win7 and 2.4.8-I602-Win7 executables fail with 'An
>>> error occurred installing the TAP device drivers.'
>> What operating system are you running exactly?
> 
> This installation is on Win7 Home Premium (SP1)

Ok.

>>
>>> After running the 2.4.8 installer, all of my (named) TAP devices had
>>> disappeared (I have more than one!)
>>>
>>> Reinstalling the previous 2.4.7-Win7 version (twice) brought them all
>>> back to life again.
>>>
>>> Is there a way I can get more detailed information about what could be
>>> causing this. It is the first time that I encounter this error.
>> Yes there is:
>>
>> <https://community.openvpn.net/openvpn/wiki/ManagingWindowsTAPDrivers>
>>
>> In particular check C:\Windows\inf\setupapi.dev.log. It contains
>> installation logs for Windows drivers in general, not just tap-windows6.
>> It generally gives a pretty good idea of the problem. It should not have
>> any sensitive information in it so you can post the relevant lines here.
> 
> In the relevant sections are quite a few error lines starting with '!',
> but these are present in both the 2.4.7 and 2.4.8 install (most of them
> are related to failing verification)
> 
> Except for the following lines, which are only present in the 2.4.8 install
> 
> !    dvi:                          Device 'ROOT\NET\0021' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> !    dvi:                          Device 'ROOT\NET\0012' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> !    dvi:                          Device 'ROOT\NET\0009' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> !    dvi:                          Device 'ROOT\NET\0004' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> !    dvi:                          Device 'ROOT\NET\0005' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> !    dvi:                          Device 'ROOT\NET\0011' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> !    dvi:                          Device 'ROOT\NET\0002' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> !    dvi:                          Device 'ROOT\NET\0013' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> 
> and the following line, which occurs multiple times (for each TAP device)
> 
> !!!  dvi:                     Device not started: Device has problem:
> 0x0a: CM_PROB_FAILED_START.
> 
> Does that help, or is more information needed to get a clue?

Hi,

I've never seen this particular problem. I'm not sure what "Device <n>
required reboot" means. Does it suggest rebooting the computer? Maybe
worth a shot if you did not do it already.

If reboot does not help I recommend wiping all traces of tap-windows6
from the computer and then installing 2.4.8-I602-Win7. The process I use
during testing is this:

1) Uninstall tap-windows6
2) Remove traces of tap-windows6 from driver store

   Clone or download (as zip):

   <https://github.com/mattock/tap-windows-scripts>

   Launch a Powershell session as an Administrator. Then

   cd tap-windows-scripts
   ./Remove-Tapwindows.ps1

   This will display you the tap-windows6 drivers it would remove from
   the driver store, something like this:

     Would remove oem<x>.inf
     Would remove oem<y>.inf

   In your case there would probably be many of these lines. They all
   should start with "oem".

   To actually remove the drivers add -Yes parameter:

  ./Remove-Tapwindows.ps1 -Yes

  After this there are no traces of tap-windows6 on your computer.

3) Install 2.4.8-I602-Win7 and see if the problem is gone

--

Let me know if this resolves the problem.

> 
>> Samuli
>>
>>> -- 
>>> Ton
>>>
>>> On 31-10-19 13:04, Samuli Seppänen wrote:
>>>> Hi,
>>>>
>>>> We recently found out that the code signing certificate the 2.4.8
>>>> Windows installers use expired a couple of weeks ago. I will get a new
>>>> certificate today evening (~6 hours) and push out new installers.
>>>>
>>>> This problem only seems to affect the prompt you get when you
>>>> double-click on the installer executable. You probably see "Unknown
>>>> publisher" there. Besides that Windows seems to be perfectly happy with
>>>> the executables and libraries. That is the main reason why a problem
>>>> such as this was able to slip through testing.
>>>>
>>>> Samuli
>>>>
>>>> Il 31/10/19 12:27, Samuli Seppänen ha scritto:
>>>>> The OpenVPN community project team is proud to release OpenVPN
>>>>> 2.4.8. It
>>>>> can be downloaded from here:
>>>>>
>>>>> <https://openvpn.net/community-downloads/>
>>>>>
>>>>> This is primarily a maintenance release with bugfixes and
>>>>> improvements.
>>>>> The Windows installers (I601) have several improvements compared to
>>>>> the
>>>>> previous release:
>>>>>
>>>>> * New tap-windows6 driver (9.24.2) which fixes some suspend and resume
>>>>> issues
>>>>> * Latest OpenVPN-GUI
>>>>> * Considerable performance boost due to new compiler optimization
>>>>> flags
>>>>>
>>>>> A summary of all included changes is available here:
>>>>>
>>>>> <https://github.com/OpenVPN/openvpn/blob/release/2.4/Changes.rst>
>>>>>
>>>>> A full list of changes is available here:
>>>>>
>>>>> <https://community.openvpn.net/openvpn/wiki/ChangesInOpenvpn24>
>>>>>
>>>>> Please note that LibreSSL is not a supported crypto backend. We accept
>>>>> patches and we do test on OpenBSD 6.0 which comes with LibreSSL,
>>>>> but if
>>>>> newer versions of LibreSSL break API compatibility we do not take
>>>>> responsibility to fix that.
>>>>>
>>>>> Also note that  Windows installers have been built with NSIS version
>>>>> that has been patched against several NSIS installer code execution
>>>>> and
>>>>> privilege escalation problems:
>>>>>
>>>>> <https://community.openvpn.net/openvpn/wiki/NSISBug1125>
>>>>>
>>>>> Based on our testing, though, older Windows versions such as Windows 7
>>>>> might not benefit from these fixes. We thus strongly encourage you to
>>>>> always move NSIS installers to a non-user-writeable location before
>>>>> running them. Our long-term plan is to migrate to using MSI installers
>>>>> instead.
>>>>>
>>>>> Compared to OpenVPN 2.3 this is a major update with a large number of
>>>>> new features, improvements and fixes. Some of the major features are
>>>>> AEAD (GCM) cipher and Elliptic Curve DH key exchange support, improved
>>>>> IPv4/IPv6 dual stack support and more seamless connection migration
>>>>> when
>>>>> client's IP address changes (Peer-ID). Also, the new --tls-crypt
>>>>> feature
>>>>> can be used to increase users' connection privacy.
>>>>>
>>>>> OpenVPN GUI bundled with the Windows installer has a large number
>>>>> of new
>>>>> features compared to the one bundled with OpenVPN 2.3. One of major
>>>>> features is the ability to run OpenVPN GUI without administrator
>>>>> privileges.
>>>>>
>>>>> For full details, look here:
>>>>>
>>>>> <https://community.openvpn.net/openvpn/wiki/ChangesInOpenvpn24>
>>>>>
>>>>> The new OpenVPN GUI features are documented here:
>>>>>
>>>>> <https://github.com/OpenVPN/openvpn-gui>
>>>>>
>>>>> Please note that OpenVPN 2.4 installers will not work on Windows XP.
>>>>>
>>>>> For generic help use these support channels:
>>>>>
>>>>> Official documentation:
>>>>> <http://openvpn.net/index.php/open-source/documentation/howto.html>
>>>>> Wiki: <https://community.openvpn.net>
>>>>> Forums: <https://forums.openvpn.net>
>>>>> User mailing list: <http://sourceforge.net/mail/?group_id=48978>
>>>>> User IRC channel: #openvpn at irc.freenode.net
>>>>>
>>>>> Please report bugs and ask development questions here:
>>>>>
>>>>> Bug tracker and wiki: <https://community.openvpn.net>
>>>>> Developer mailing list: <http://sourceforge.net/mail/?group_id=48978>
>>>>> Developer IRC channel: #openvpn-devel at irc.freenode.net (requires
>>>>> Freenode registration)
>>>>>
>>>>>
>>>>> Samuli
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Openvpn-devel mailing list
>>>>> Openvpn-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>>>>>
>>>>
>>>> _______________________________________________
>>>> Openvpn-devel mailing list
>>>> Openvpn-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>>>
>>>
>>> _______________________________________________
>>> Openvpn-devel mailing list
>>> Openvpn-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>>>
>>
> 


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Reply via email to