On Thu, Apr 02, 2020 at 10:03:40 +0300, Samuli Seppänen wrote:
> Hi,
>
> Il 02/04/20 08:33, Nathan Stratton Treadway ha scritto:
> > On Wed, Apr 01, 2020 at 11:14:08 -0400, Nathan Stratton Treadway wrote:
> >> I should be able to get the setupapi.dev.log files from both of the
> >> machines if that would be helpful.
> >
> > I extracted the section of the setupapi.dev.log files related to the
> > TAP-Windows installation from each of the systems in question, and then
> > to try to spot the funtional differences between the two, I ran the
> > following commands to mask off the timestamps contained within the log:
> >
> > $ sed "s/10:50:03\..../HH:MM:SS.sss/g" setupapi_TAP-Windows_succeeded.log
> > > setupapi_TAP-Windows_succeeded.log_cleaned
> > $ sed "s/11:09:33\..../HH:MM:SS.sss/g" setupapi_TAP-Windows_failed.log >
> > setupapi_TAP-Windows_failed.log_cleaned
> >
> > and then compared the two "_cleaned" files:
> >
> > =====
> > $ diff -ui setupapi_TAP-Windows_{succeeded,failed}.log_cleaned
> > --- setupapi_TAP-Windows_succeeded.log_cleaned 2020-04-02
> > 00:18:12.000000000 -0400
> > +++ setupapi_TAP-Windows_failed.log_cleaned 2020-04-02 00:19:09.000000000
> > -0400
> > @@ -1,5 +1,5 @@
> > >>> [Device Install (UpdateDriverForPlugAndPlayDevices) - tap0901]
> > ->>> Section start 2020/03/13 HH:MM:SS.sss
> > +>>> Section start 2020/03/27 HH:MM:SS.sss
> > cmd: "C:\Program Files\TAP-Windows\bin\tapinstall.exe" install
> > "C:\Program Files\TAP-Windows\driver\OemVista.inf" tap0901
> > ndv: INF path: C:\Program Files\TAP-Windows\driver\OemVista.inf
> > ndv: Install flags: 0x00000001
> > @@ -9,19 +9,13 @@
> > dvi: {Build Driver List} HH:MM:SS.sss
> > dvi: Searching for hardware ID(s):
> > dvi: tap0901
> > - sig: {_VERIFY_FILE_SIGNATURE} HH:MM:SS.sss
> > - sig: Key = oemvista.inf
> > - sig: FilePath = c:\program
> > files\tap-windows\driver\oemvista.inf
> > - sig: Catalog = c:\program
> > files\tap-windows\driver\tap0901.cat
> > - sig: Success: File is signed in catalog.
> > - sig: {_VERIFY_FILE_SIGNATURE exit(0x00000000)} HH:MM:SS.sss
> > dvi: Created Driver Node:
> > dvi: HardwareID - tap0901
> > dvi: InfName - c:\program
> > files\tap-windows\driver\oemvista.inf
> > dvi: DevDesc - TAP-Windows Adapter V9
> > dvi: Section - tap0901.ndi
> > dvi: Rank - 0x00ff0000
> > - dvi: Signer Score - WHQL
> > + dvi: Signer Score - Authenticode
>
> Your problem seems to be the same as Ralf's (see my other email). The
> NSIS installer chose to install the Windows 7 version of tap-windows6 on
> this Windows 10 instance, and that will not work.
>
> WHQL = attestation signed
> Authenticode = cross-signed
Sorry, I don't know much about NSIS operation: is tap-windows6 driver
included in the openvpn-install-2.4.8-i602-Win10.exe installer?
>
> > dvi: DrvDate - 09/27/2019
> > dvi: Version - 9.24.2.601
> > dvi: {Build Driver List - exit(0x00000000)} HH:MM:SS.sss
> > @@ -40,70 +34,15 @@
> > ndv: Inf Name - oemvista.inf
> > ndv: Driver Date - 09/27/2019
> > ndv: Driver Version - 9.24.2.601
> > + ndv: Driver package
> > 'C:\WINDOWS\System32\DriverStore\FileRepository\oemvista.inf_amd64_6d4bec28a2ef0cdf\oemvista.inf'
> > is already imported.
> > sto: {Setup Import Driver Package: c:\program
> > files\tap-windows\driver\oemvista.inf} HH:MM:SS.sss
> > - inf: Provider: TAP-Windows Provider V9
> > - inf: Class GUID: {4d36e972-e325-11ce-bfc1-08002be10318}
> > - inf: Driver Version: 09/27/2019,9.24.2.601
> > - inf: Catalog File: tap0901.cat
> > - sto: {Copy Driver Package: c:\program
> > files\tap-windows\driver\oemvista.inf} HH:MM:SS.sss
> > - sto: Driver Package = c:\program
> > files\tap-windows\driver\oemvista.inf
> > - sto: Flags = 0x00000007
> > [... skipping the copying of all the driver files, etc...]
> > - sto: {DRIVERSTORE IMPORT END} HH:MM:SS.sss
> > - dvi: Flushed all driver package files to
> > disk. Time = 16 ms
> > - sig: Installed catalog 'tap0901.cat' as
> > 'oem128.cat'.
> > - sto: {DRIVERSTORE IMPORT END: exit(0x00000000)}
> > HH:MM:SS.sss
> > - sto: {Core Driver Package Import: exit(0x00000000)}
> > HH:MM:SS.sss
> > - sto: {Stage Driver Package: exit(0x00000000)} HH:MM:SS.sss
> > + sto: Driver package already imported as 'oem43.inf'.
Do these two "alrleady imported" lines in the _failed file indicate that
the installer didn't actually install the Windows 7 versison, but rather
concluded for some reason that the package in question was already
installed, or something like that?
Note that the logs from both machines included the lines saying "Driver
Version - 9.24.2.601", which I assume means they are both looking at the
tap9 oemvista.inf file?
Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
