KB4497935

When opening games that utilize BattlEye anti-cheat software, the BattlEye UI or game may display one of the following errors:

• “Failed to start BattlEye Service.”

• “Failed to initialize BattlEye Service.”

Some games that use older BattlEye versions are not compatible with Windows 10, version 1903. BattlEye has provided an updated patch for games we know are affected.

For a list of recent games that use BattlEye, go to www.battleye.com/.

Do one or more of the following:

• Verify that your game is up to date with the latest available version. Some game platforms allow you to validate your game files, which can confirm that your installation is fully up to date.

• Restart your system and open the game again.

• Uninstall BattlEye using UninstallBE.exe, and then reopen your game.

• Uninstall and reinstall your game.

For more troubleshooting options, go to www.battleye.com/support/faq/.

Windows Sandbox may fail to start with "ERROR_FILE_NOT_FOUND (0x80070002)" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.

This issue is resolved in KB4512941.

The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” on devices where the diagnostic data level is manually configured to the non-default setting of 0. You may also receive an error in the Application section of Windows Logsin Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”.

This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with or without device tunnel. This does not affect manual only VPN profiles or connections.

This issue is resolved in KB4505903.

Devices connected to a domain that is configured to use MIT Kerberos realms may not start up or may continue to restart after installation of this update. Devices that are domain controllers or domain members are both affected.

If you are not sure if your device is affected, contact your administrator. Advanced users can check if this registry key exists HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\MitRealms or for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos.

This issue is resolved in KB4512941.