iRacing
iRacing is already running / simulator failed to close
An iRacing process that remains after leaving a session can cause an already-running message. Check for a genuinely stale process and the applicable Logitech integrations.
Checks and expected results
Before you repair it
- Confirm the session has ended and inspect Task Manager for the remaining simulator process.
- Record the wheel model and whether TrueForce or Logitech lighting integration is in use.
- Close the simulator and back up app.ini before the supported integration-disable test.
How to confirm the result
Start and exit a test session, then confirm the simulator process closes and the next launch succeeds. Compare wheel features with the previous settings.
Repair limits and when to stop
Disabling TrueForce and lighting changes those features during the test. It is not a reason to interrupt a running race, and it does not prove that every leftover process is a Logitech fault.
How PitMedic recognizes it
iRacing reports the simulator is already running or a stale simulator process remains after exit.
Signals PitMedic may recognize
iRacing is already runningsim is already runningtrueForceEnabledenableLogitechLEDPlease close the simulator
Built-in response
Back up app.ini and disable both TrueForce and Logitech hardware-lighting integrations, matching iRacing's documented workarounds for simulator shutdown/stale-process conflicts.
Verification sources
PitMedic prioritizes vendor documentation and labels community findings separately.
- iRacing is already running messageiRacing Support · Official sourceOpen source
Official support documents a Logitech G HUB TrueForce conflict and the trueForceEnabled=0 workaround.
- Please close the simulator if you wish to launch a new sessioniRacing Support · Official sourceOpen source
Official support also documents Logitech hardware lighting as a shutdown conflict and recommends enableLogitechLED=0.