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
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'.
sto: {Setup Import Driver Package - exit (0x00000000)} HH:MM:SS.sss
dvi: Searching for hardware ID(s):
dvi: tap0901
dvi: Class GUID of device changed to:
{4d36e972-e325-11ce-bfc1-08002be10318}.
dvi: {Plug and Play Service: Device Install for ROOT\NET\0000}
- dvi: Driver INF Path: C:\windows\INF\oem128.inf
+ dvi: Driver INF Path: C:\WINDOWS\INF\oem43.inf
dvi: Driver Node Name:
oemvista.inf:3beb73aff103cc24:tap0901.ndi:9.24.2.601:tap0901,
dvi: Driver Store Path:
C:\windows\System32\DriverStore\FileRepository\oemvista.inf_amd64_6d4bec28a2ef0cdf\oemvista.inf
dvi: Searching for hardware ID(s):
@@ -141,7 +80,7 @@
dvi: Existing files modified, may need to
restart related services.
sto: {Configure Driver Package: exit(0x00000bc3)}
dvi: Restart required for any devices using this
driver.
- dvi: Install Device: Configuring device
(oem128.inf:tap0901,tap0901.ndi). HH:MM:SS.sss
+ dvi: Install Device: Configuring device
(oem43.inf:tap0901,tap0901.ndi). HH:MM:SS.sss
dvi: Install Device: Configuring device
completed. HH:MM:SS.sss
dvi: Device Status: 0x01802001, Problem: 0x0
(0x00000000)
dvi: {Restarting Devices} HH:MM:SS.sss
@@ -154,10 +93,10 @@
dvi: {Core Device Install - exit(0x00000000)} HH:MM:SS.sss
dvi: Waiting for device post-install to complete. HH:MM:SS.sss
dvi: Device post-install completed. HH:MM:SS.sss
- dvi: Device Status: 0x0180200B, Problem: 0x0 (0x00000000)
+! dvi: Device Status: 0x01802401, Problem: 0x34 (0xC0000428)
ump: {Plug and Play Service: Device Install exit(00000000)}
ndv: {Update Device Driver - exit(00000000)}
ndv: {Install Related Drivers} HH:MM:SS.sss
ndv: {Install Related Drivers: exit(0x00000000)} HH:MM:SS.sss
-<<< Section end 2020/03/13 HH:MM:SS.sss
+<<< Section end 2020/03/27 HH:MM:SS.sss
<<< [Exit status: SUCCESS]
=====
However, the computer on which this installation failed actually had a
"factory reset" of Windows done (due to seemingly unrelated-to-OpenVPN
crashes) on 3/26, so it seems strange that
oemvista.inf_amd64_6d4bec28a2ef0cdf\oemvista.inf is found to be "already
imported" on that machine but not on the other one. (And I don't see
any previous occurence of the string "6d4be" or "tap" or anything
obviously related anywhere earlier in the full setupapi log file on that
machine.)
On both of these systems, the OpenVPN installation was done using the
openvpn-install-2.4.8-i602-Win10.exe installer, and they rare both
unning the same release of Windows:
"_succeeded" machine:
Edition: Windows 10 Pro
Version: 1909
Installed on 12/04/2019
OS build 18363.720
"_failed" machine:
Edition: Windows 10 Pro
version: 1909
Installation: 03/26/2020
OS Build: 18363.720
Let me know if I can provide any additional information.
Thanks.
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
