Simulator repair

iRacing

Failed CreateProcessAsUser / incompatible Windows compatibility override

Forced administrator or legacy compatibility settings can interfere with iRacing’s supported launch path. Inspect only the executables involved in the failed launch.

Automatic repair availableActiveEvidence reviewed 2026-09-01Guide updated 2026-09-29

Checks and expected results

Before you repair it

  • Capture CreateProcessAsUser or the exact launch error if present.
  • Check Compatibility settings on the actual iRacing executables and compare them with the shortcut paths.
  • Preserve the current settings before removing only the administrator or legacy compatibility overrides implicated by the failure.

How to confirm the result

Relaunch through the usual supported UI path and retry a test session. If the failure is unchanged, retain the before-and-after settings for further diagnosis.

Repair limits and when to stop

This is a targeted compatibility change, not a blanket instruction to run Steam or Windows applications as administrator. Other applications’ compatibility settings remain outside the repair.

How PitMedic recognizes it

Launch log reports CreateProcessAsUser failure or Windows compatibility mode/admin override is applied to iRacing executables.

Signals PitMedic may recognize

  • CreateProcessAsUser
  • compatibility mode
  • RUNASADMIN

Built-in response

Back up AppCompat registry values and remove only Run-as-administrator/legacy Windows compatibility tokens for iRacing executables.

Repair safetyReversible / one-click

Verification sources

PitMedic prioritizes vendor documentation and labels community findings separately.

  • Failed CreateProcessAsUser erroriRacing Support · Official source

    Official guidance recommends removing the Run as administrator compatibility setting from iRacingSim64DX11.exe.

    Open source