Hi
> > The sha1sums of the two versions of the file are:
> > =====
> > $ sha1sum *{program,system32}*tap09*
> > 42189b6a1b8c736397113bfc2283f5e1e1a44e8e
> failed_program-files_tap0901.sys
> > [the 39,920-byte file]
> > 841a86f416a882b0743fd6d9c9f29baf3ed06b6a
> failed_system32-drivers_tap0901.sys
> > [the 30,720-byte file]
> > =====
> >
> >
> > So.. do you recognize this 30,720-byte file at all, or have any ideas
> > where it might have originated from?
>
> It occurred to me that even though we don't need to install OpenVPN on a
> Windows 7 box I could go ahead and download the Win7 installer and
> see if the embedded TAP driver files match the ones included there.
>
> Short answer: yes, the mystery files are exactly the same as the ones in
> that installer.
> So, that doesn't really tell us how those driver files got installed on
> the box before OpenVPN was ever installed -- but at least it tells us
> exactly which files were involved....
>
Is it possible that the user might have mistakenly installed the windows 7
version of 2.4.8 on this machine before the reset? The fact that the
offending .sys file and inf came back via the ~BT folder seems to indicate
it
was saved by the reset process and then copied back in.
It could be that the process was not really a factory reset (not sure
whether you
already said otherwise) or the factory version has some program that
distributes
this driver with the same inf file. Though it would sound strange to
distribute a
a cross-signed driver with Windows 10, there are some old flavours
of Windows 10 where such a driver works, iirc.
Can you check whether the offending .sys is in use by any devices?
driverquery utility
may in windows 10 probably help.
The two versions using identical inf file is what makes it hard to fix it
by just
reinstalling the correct Windows 10 release.
Selva
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
