OpenVPN Ver 2.6.12 Connectivity Issue with OpenVPN Connect V3

There was an issue with OpenVPN V 2.6.12 logs are mentioned below

Logs:
2024-11-04 11:35:49 Error in cryptoapicert: failed to acquire key. Key not present or is in a legacy token not supported by Windows CNG API: Keyset does not exist (errno=-2146893802)

Troubleshooting:
We face that issue when we have both applications on the same PC. After connecting OpenVPN Connect V3, we will get this error in OpenVPN V 2.6.12.

1. We install the OpenVPN V 2.6.12 and install the certificate.
2. Check the connectivity, and it's connected.
3. Install OpenVPN Connect V3.
4. Create the Profile import configuration, install, and select the certificate for the profile.
5. Check the connectivity for OpenVPN Connect V3, and it's connected.
6. Then disconnect OpenVPN Connect V3 go back to OpenVPN V 2.6.12 and try to connect and we are getting that error.
7. Just delete the certificate from MMC and install it again.
8. Check the connection for OpenVPN V 2.6.12 and its connection.

Note:
We don't have this error while using OpenVPN V 2.4./2.5. with OpenVPN Connect V3.

Start by reproducing the certificate sequence described in the issue: OpenVPN 2.6.12, OpenVPN Connect V3, and the certificate imported through MMC. Then investigate the cryptoapicert failure and the reported Windows CNG error. Done means OpenVPN 2.6.12 reconnects after OpenVPN Connect V3 disconnects without requiring certificate reinstallation.