Fix: VPN not working after 1709 Update

Fall Creators Update 1709 brought along numerous features for Windows users with enhanced connectivity and additional functionalities. A lot of already broken modules were fixed and released as well. However, users started to see problems with the VPN module when the update was released.

The users were unable to open the in-built VPN application at all or the module was not connecting successfully. This problem usually occurs because of software problems as well as bad internet connectivity.

Solution 1: Changing the Registry

We can try adding a key to the registry “PolicyAgent”. If this method doesn’t work, you can always undo the changes in a reverse manner. Do note that the registry editor is a powerful tool and creating/editing keys that you don’t know about can hamper your computer and make it unusable.

1. Press Windows + R to launch the Run application. Type “regedit” in the dialogue box and press Enter.
2. Once in the registry editor, navigate to the following file path:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent

3. In the required path, right-click on the empty space on the right side of the window and select “New > DWORD”.

4. Name the new word as “AssumeUDPEncapsulationContextOnSendRule”. After creating it, double-click it to open its properties and set its value to “2”. Press Ok to save changes and exit.

5. Reboot your computer and check if the problem got solved.

Solution 2: Reinstalling the VPN package (CMAK)

After an in-place upgrade (from 1703 to 1709), many users reported that their VPN client started working abnormally or refused to work at all. After a lot of complaints, Microsoft officially acknowledged the problem and released a statement that you might have to reinstall the VPN package altogether. This was particularly targeted at CMAK (Connection Manager Administration Kit) VPN’s.

1. Press Windows + S to launch the search bar. Type “features” in the dialogue box and open the first result which comes forth.

2. Once in the features window, navigate through all the entries until you find “RAS Connection Manager Administration Kit (CMAK)”. If you were already using the package, it will most probably be checked. Uncheck it and select “Ok”.

3. Windows will now uninstall the utility. Restart your computer and navigate back to the features window.
4. Check the box (RAS Connection Manager Administration Kit (CMAK)) and press “OK” for the installation to proceed. Once the installation is complete reboot your computer once again and check if the problem is solved.

Solution 3: Cisco VPN after 1709 Update

It is recommended that you uninstall the Cisco VPN client before proceeding with the update. This way repairing the client will be much easier as compared to not installing it before the update. Refer to the following steps on how to properly install and make the client functional.

Note: Appuals has no affiliations with any third-party software documented in this article. All the software is mentioned purely for the ease of access of the users. Perform all tasks at your own risk.

1. Download Sonicwall 64-bit VPN. Make sure that you use the latest version of this client as older versions might not work as expected.
2. Once you are done installing Sonicwall, install the Cisco VPN Use 64-bit if you have a 64-bit operating system and 32-bit if you have 32-bit.

You can easily check this by right-clicking on “This PC” and selecting properties. Once in properties, look beneath the “System” heading and check your system type.

64-bit file download

32-bit file download

Note: If you encounter an error that these exe files cannot run on this operating system, simply extract the exe file using WinRAR (or any similar program) and run the .msi file.

3. Now we will edit the registry to make some changes. Press Windows + R, type “regedit” and press Enter.
4. Once in the registry editor, navigate to the following path:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\CVirtA

5. Now select the display name and modify it accordingly:

• x86 – “@oem8.ifn,%CVirtA_Desc%;Cisco Systems VPN Adapter” to “Cisco Systems VPN Adapter”
• x64 – “@oem8.ifn,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows” to “Cisco Systems VPN Adapter for 64-bit Windows”

6. Once the changes are made, exit the registry and restart your computer. After restarting, check if the problem is fixed.

Solution 4: Requesting your System Administrator to Allow L2TP

After the latest 1709 update, PPTP works as expected but L2TP is giving problems. This can be easily resolved by contacting your system/company administrator and asking them to allow PPTP protocol along with L2TP. This can be easily achieved by using the in-built RAS feature present on Windows 2012 R2 servers. This problem is mostly faced by people when they are trying to connect to their work while not being physically present.