![]() Something is screwed up with certificates associated with openvpn/tap installer.Īnd not with the certificate itself - the one that's assigned to it it's good and legit but specifically with the intermediate certificate: the one that (in theory) you could get from the digisign guys.įunny enough, Microsoft has exactly the same challenges with one of their. Who's at fault - Microsoft, who started enforcing driver signatures that's annoying exercise to go through, a lot of projects out there choose not to do it ī) Challenge two: busted certificate chain. Technically, one can bypass it by either experimenting bcedits enabling test mode or by loading via F8/disable driver signature. ![]() (and they seem to have it (at least) for the past ~8-10 releases (went as far as 9.9 with tap installer and 2.0 with openvpn))Ī) Challenge one: digital signature. There seem to be two issues that the latest OpenVPN installer has (i still do wander why other drivers may interfere with the install from openvpn, but that's a diff story)ģ.2 bcedit experiments & windows reboot with "disable driver signature enforcement"ģ.3 manually imported certificates (via certmgr & mmc snap in for the local computer to root & trusted publisher)ģ.4 signed driver myself & used self-signed certificateĪs an experiment, took clean windows 7 圆4 sp1 - installed openvpn - has challenges too, works only under "disable driver signature enforcement".īut at least - tap driver is recognized as a driver - and is loaded properly if one chooses "disable driver signature" so it sorta works.Īfter all the experiments, this is what i came down to: To resolve the tap driver challenges, tried:ģ.1 Full system cleanup (delete all the drivers, openvpn installs, tap installer/reinstalled everything w/ and w/o tap installer) "This device is not working properly because Windows cannot load the drivers required for this device. ![]() So tap driver isn't being recognized by the system (go to device manager/check network section/see tap driver with yellow triangle on the icon: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\ 15:18:46.351 I noted that the driver is not in windows registry. ![]() In the meantime, I spent hours and tried a lot of things, no success up to now. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |