Not able to start SQL Services using SQL Server 2022 and when only TLS 1.3 protocol is enabled

Hi,
I am also facing the same issue, not able to start SQL Services (SQL Server and SQL Server Agent ) using SQL Server 2022 and when only TLS 1.3 protocol is enabled.

Used the following links for setup installation.
https://learn.microsoft.com/en-us/sql/relational-databases/security/networking/tls-1-3?view=sql-server-ver16
https://learn.microsoft.com/en-us/sql/relational-databases/security/networking/connect-with-strict-encryption?view=sql-server-ver16

ODBC Driver for SQL Server version 18.2.2.1 OLE DB Driver for SQL Server version 19.3.1.0

I have installed ODBC and OLE Db driver with SQL server 2022 CU6 (16.x)
https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate6

Followed the below link to configure SQL Server Database Engine for encrypting connections:
https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-sql-server-encryption?view=sql-server-ver16


Error log:
Error: 26011, Severity: 16, State: 1.
The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x139f, status code 0x80. Reason: Unable to initialize SSL support. The group or resource is not in the correct state to perform the requested operation.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x139f, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The group or resource is not in the correct state to perform the requested operation.
Error: 17826, Severity: 18, State: 3.
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
Error: 17120, Severity: 16, State: 1.
SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.