Windows Server 2019 VPN Error 8007042a – Fix After KB4480116 Update

windows-server-2019

I am running Windows Server 2019 datacenter with router and remote access for VPN access. Everything was working fine until I installed the January 8, 2019 update: https://support.microsoft.com/en-us/help/4480116

After the update, I was unable to start the routing and remote access service and got the following error:

I can confirm that after I uninstalled the update, the service was able to start. Anyone else having this problem?

Best Answer

I found temporary solution. NPS service (Network Policy Server) blocks starting RRAS. If you stop NPS, you can start RRAS and after that you can start NPS. If you don't use NPS you can probably disable it. I've changed service settings to start RRAS Automatic and NPS Automatic (Delayed start), but I can't test it now on production server. At least you can start it manually if you are in local network and you don't have to reinstall RRAS to get it work. It was big mistake to install 2019 to the small company. It's the only server so there isn't any older Windows Server.

Related Solutions

Windows Server 2019 – Fix L2TP VPN in RRAS Only Accessible from Internal Interface

The problem was, that there was port-forwarding in NAT-interface. The forwardings must be disabled (although they was to 127.0.0.1).

Windows Server 2019 scheduled tasks must be in future

It seems your error does not have anything in common with the linked question about task must be in the future.

There is something else wrong with your task or your system.

C:\>Err_6.4.5.exe 2147943568
# for decimal -2147023728 / hex 0x80070490
  PEER_E_NOT_FOUND                                               p2p.h
  E_PROP_ID_UNSUPPORTED                                          vfwmsgs.h
# The specified property ID is not supported for the
# specified property set.%0
  WER_E_NOT_FOUND                                                werapi.h
  DRM_E_NOT_FOUND                                                windowsplayready.h
# as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x490
# for decimal 1168 / hex 0x490
  ERROR_NOT_FOUND                                                winerror.h
# Element not found.
# 5 matches found for "2147943568"

So the result seems to be 0x80070490 which translates to "Element not found" errors.

You have to check every step of your task like what actions are performed with what parameters and so on. Also try to start the desired action/command yourself in a cmd box started with the credentials the task is using. PSExec can also help to test the launch of commands as a system user.

Best Answer

Related Solutions

Windows Server 2019 – Fix L2TP VPN in RRAS Only Accessible from Internal Interface

Windows Server 2019 scheduled tasks must be in future

Related Topic