On Thu, Apr 02, 2020 at 01:33:11 -0400, Nathan Stratton Treadway wrote:
> =====
> $ 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
> 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 already imported as 'oem43.inf'.
I am still not sure exactly how oem48.inf came to be pre-loaded on this
computer, but at this point it seems like an important question is "how
does Windows decide a driver package is 'already loaded'?"
When I looked around on the machine while the TAP driver was broken, I
believe that the oemvista.inf file that got pre-installed was identical
to the one distributed in the openvpn-install-2.4.8-I602-Win10.exe
file... while obviously the two tap0901.* files were different.
So I'm wondering if Windows just does some sort of file compare on the
.inf files and concludes "no work to do here" if they match?
Whatever the mechinism Windows uses, it seems maybe the .inf files could
to be tweaked in some way between the Win7 and Win10 packages so that if
the wrong one is pre-installed Windows goes ahead and uninstalls that
version rather than leaving it unchanged...
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
