PitMedic
Support PitMedicHome
Simulator repair

iRacing

iRacing Error 73 / Easy Anti-Cheat failure

iRacing Error 73 is a startup failure associated with the EOS version of Easy Anti-Cheat. PitMedic confirms the error signature before offering iRacing's supported uninstall, reinstall, and repair workflow.

Approval requiredActiveEvidence reviewed 2026-09-01Guide updated 2026-10-09

Checks and expected results

The failure occurs before a normal simulator session begins, so graphics, car, and track resets are unlikely to address it. iRacing also warns that duplicate installations can leave the anti-cheat repair pointed at the wrong simulator path.

Before you repair it

  • Close iRacing before running the anti-cheat repair.
  • Confirm the message explicitly names Error 73, Easy Anti-Cheat, or EOS.
  • Check for more than one iRacing installation and identify the copy you actually launch.
  • Use the Easy Anti-Cheat tools included with that installation rather than an unrelated download.

How to confirm the result

After the EOS Easy Anti-Cheat service is repaired, launch the same iRacing installation again. If Error 73 remains, verify that shortcuts and Steam point to the same installation before repeating the repair.

Repair limits and when to stop

Only explicit matching failure evidence supports this repair. An installation-status probe during an update is not a failed launch. This does not bypass security checks or repair unrelated graphics, car, or track problems.

Manual steps without PitMedic

iRacing links Error 73 to its EOS installation instructions. Use the files bundled with the installed copy you actually launch.

  1. Close the simulator and wait for any iRacing update to finish.
  2. Open the EasyAntiCheat folder inside your iRacing installation. The default direct-install location is C:\Program Files (x86)\iRacing\EasyAntiCheat. For Steam, it is normally under steamapps\common\iRacing\EasyAntiCheat in your Steam library; custom libraries use their own location.
  3. Run InstallEOSAntiCheat.bat from that folder and follow its prompts. If it is missing, consult the official instructions below; do not download a replacement script from another site.
  4. Launch the same iRacing installation again. If Error 73 persists, check whether another installed copy or shortcut points to a different location, then contact iRacing Support with the error screenshot.

Official instructions

How PitMedic recognizes it

Error 73 or explicit EAC/EOS anti-cheat failure near simulator startup.

Signals PitMedic may recognize

  • Error 73
  • Easy Anti-Cheat
  • EOS

Built-in response

Run the supported EOS Easy Anti-Cheat uninstall/reinstall/repair workflow, then verify the sim installation path is unique.

Repair safetySignificant / always ask

Specific evidence survives a saved-finding round trip

Verified automated regression test · 2026-09-28

Test setup

Synthetic findings combined an application fault with a specific service, UI, update-permissions, or Error 73 signature.

Observed result

Capture, serialized history, and independent helper reconstruction selected the corresponding targeted plan, including when the saved recommendation was stale or altered.

What this establishes

This tests plan consistency; it does not execute a service restart, delete a cache, or demonstrate a successful repair on a simulator installation.

Read the test source · View the passing Windows test run

Verification sources

PitMedic prioritizes vendor documentation and labels community findings separately.

  • Error 73 Fatal Error DetectediRacing Support · Official source

    Official guidance says to reinstall the EOS version of EAC and check for multiple iRacing installs.

    Open source