iRacing
Could not find sim
Could not find sim is a launch failure with several possible causes. Check the launch path, VR tools, and Documents location before choosing a repair.
Checks and expected results
Before you repair it
- Compare a monitor-based test session with VR, if available, and note whether OpenXR Toolkit is installed.
- Compare the UI shortcut target with the location of iRacing.com Helper Service. Both should belong to the intended installation.
- Open the actual Documents folder and inspect the iRacing folder location, including whether OneDrive manages it.
- Record whether Windows beta UTF-8 is enabled and whether the Windows account name uses special characters; follow the linked iRacing guidance for a matching condition.
How to confirm the result
After correcting one confirmed mismatch using vendor guidance, launch the same test session again. Record which change affected the result so unrelated settings can remain intact.
Repair limits and when to stop
This record provides guided diagnosis, not a universal one-click repair. Do not broadly move Documents, disable OneDrive backup, uninstall VR software, or change Windows locale settings without understanding the impact and preserving data.
How PitMedic recognizes it
UI reports Could not find sim; correlate VR/OpenXR Toolkit, duplicate installations, OneDrive Documents path, and Windows UTF-8 beta setting.
Signals PitMedic may recognize
Could not find simOpenXR ToolkitOneDrive
Built-in response
Detect the conflicting condition first; offer only targeted corrective actions. Do not broadly move Documents or uninstall software without approval.
Verification sources
PitMedic prioritizes vendor documentation and labels community findings separately.
- Could not find sim error messageiRacing Support · Official sourceOpen source
Official support lists OpenXR Toolkit, duplicate installs, OneDrive Documents and Windows UTF-8 beta mode as known causes.