FC 26 PC – Denuvo Activation64.dll Error After Steam Update
Hello EA Support,
I am experiencing persistent technical issues with EA SPORTS FC 26 on PC. The game worked normally for approximately 21 hours, including throughout the weekend. The errors appeared during troubleshooting after a Steam client update.
System information:
Game: EA SPORTS FC 26
Platform: Steam and EA app
Operating system: Windows 10 Pro 22H2, 64-bit
Installation path: D:\SteamLibrary\steamapps\common\FC 26
Errors encountered:
- EA AntiCheat/Reflex watchdog error: Windows could not verify the digital signature of a file (0x80070241).
- Hypervisor-related error (0xC035001E).
- Reflex reported a hash mismatch for FC26.exe.
- The game later displayed this error: "The code execution cannot proceed because FAKE/Activation64.dll was not found."
A Denuvo diagnostic ticket was also generated in the game folder.
After a Steam client update, I received an "OpenSteamTool - IPC spec missing" warning. Steam updated again, but the warning continued to appear.
On October 13, 2026, I noticed a FAKE folder in the game's installation directory. I do not remember this folder existing before. It contains Activation64.dll, whose file properties identify it as "EA DRM Helper" and list Electronic Arts, Inc. as the company. I also found anadius.cfg and anadius64.dll in the game directory. I have not established what created these files or whether they are related to the errors.
Troubleshooting performed:
- Reinstalled EA Javelin AntiCheat.
- Verified the game files through Steam.
- Reinstalled the game previously.
- Checked Windows hypervisor and driver-signature settings.
- Checked the digital signature of FC26.exe, which Windows reported as valid.
- Checked the Steam launch options and found a manually entered executable path.
I would like to understand what is causing these errors and how to restore a clean, officially supported installation.
Could EA clarify whether this may involve the game installation, EA AntiCheat, Denuvo activation, or license verification? Is there an official way to identify which component is requesting FAKE/Activation64.dll?
Please let me know which diagnostic logs I should provide.
Thank you.
