Opened 4 months ago

Last modified 4 months ago

#1254 new Bug / Defect

TAP-Windows Adapter V9 on Windows 7 get Code 52 error

Reported by: asantaatnasa Owned by:
Priority: major Milestone:
Component: tap-windows Version: OpenVPN 2.4.8 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:
Cc:

Description

On clean install of Windows Professional ver. 6.1. (build 7601: Service Pack 1) get the Code 52 driver error of TAP-Windows Adapter V9 when installed from openvpn-install-2.4.8-I602-Win7.

Looks like this error is caused by driver signing type(sha256) from openvpn installation package. As mentioned at this forum thread last working version of tap-driver for clean Windows 7 install is 9.21.2, which has double signing: sha1 and sha256. Versions after 9.21.2 has only sha256 signing, and prior versions are signed with sha1.

After installing KB4474419 driver error 52 has been resolved, and TAP driver works fine. KB4474419 introduces SHA-2 code sign support.Looks like this behavior is related to changes in drivers and updates signing of Microsoft products. Additional information can be found at Microsoft support article: 2019 SHA-2 Code Signing Support requirement for Windows and WSUS.

If there is a requirement for update(KB4474419) or other to run OpenVPN on Windows 7, it'll be nice to check this at install time.

Change History (1)

comment:1 Changed 4 months ago by asantaatnasa

Ticket related to #1234. I did not specified that issue occurred at 64-bit Windows.

Last edited 4 months ago by asantaatnasa (previous) (diff)
Note: See TracTickets for help on using tickets.