FIX: Remote Access rasgreeng.dll failed to initialize (Event 20063)

If the VPN Server incoming connections doesn’t work, because the Remote Access protocols rasgreeng.dll & IKEv2 failed to initialize, continue reading below to fix the problem.

Problem in details. After setting up Windows 10 as a VPN server, clients cannot connect to the VPN server because after entering the credentials, the connection is dropped without any obvious reason. When this happens, the following two errors are logged on the VPN server.

• Remote Access Connection Manager failed to start because the Protocol engine [rasgreeng.dll] failed to initialize. The specified module could not be found. (Event ID: 20063)

• Remote Access Connection Manager failed to start because the Protocol engine [IKEv2] failed to initialize. The request is not supported.(Event ID: 20063)

How to FIX: Remote Access Connection Manager failed to start: rasgreeng.dll & IKEv2 failed to initialize on Windows 10 (Event ID 20063).

To fix the Event ID 20063 in Remote Access Connection Manager, perform the below steps:

1. On the VPN Server, open the Windows Services control panel: To do that:

1. 1. Press Windows + R keys to open the run command box.
   2. In the Search box, type: services.msc  & click OK.

2. In Services, double click to open the Remote Access Auto Connection Manager service.

3. Set the Startup type to Automatic and click Apply.

4. Then Start the service and click OK or restart the PC.

5. Try to connect to the VPN server from the clients. The problem should be resolved.*

* Note: If the problem is not fixed, apply the following steps.

1. Ensure that the following services on the VPN server are up and running:

• DCOM Server Process Launcher (DcomLaunch)
• Plug and Play (PlugPlay)
• Remote Access Connection Manager (RasMan)
• Remote Procedure Call (RPC) (RpcSs)
• RPC Endpoint Mapper (RpcEptMapper)
• Secure Socket Tunneling Protocol Service (SstpSvc)
• Telephony (TapiSrv)

2. Repair the Windows system files, by running the following commands (in order) in Admin Command Prompt and then reboot your PC:

• DISM /Online /Cleanup-Image /StartComponentCleanup
• DISM.exe /Online /Cleanup-image /Restorehealth
• sfc /scannow

That’s all folks! Did it work for you?
Please leave a comment in the comment section below or even better: like and share this blog post in the social networks to help spread the word about this solution.

If this article was useful for you, please consider supporting us by making a donation. Even $1 can a make a huge difference for us.