Common Content Manager errors and fixes
Almost every Content Manager error you will see falls into a small number of recurring categories. This guide names the ones people actually run into, explains what causes each, and walks through the fix that resolves it in the great majority of cases.
How to read Content Manager error messages
Content Manager is a stable, mature application, so when errors do appear they almost always trace back to a handful of recurring causes: a missing .NET runtime, a path it cannot find, a Windows security prompt or a firewall blocking the server list. Once you can recognise which category an error belongs to, the fix is usually a small, specific action rather than a full reinstall.
The most common pattern is misdiagnosis: a Windows SmartScreen warning, for example, looks alarming the first time it appears, but it is not an error and not evidence of malware. Similarly, the dreaded "could not load file or assembly" almost always means a missing .NET Framework version, not a corrupt Content Manager install. Treating those correctly saves a great deal of time.
The table below groups the most common errors into four categories, and the sections after it cover each named error in order. If your problem is more general, our main troubleshooting guide covers crashes, sluggish performance and the issues that are not strictly errors at all.
| Category | What it looks like |
|---|---|
| Install errors | The app will not start, or Windows refuses to run it |
| Setup errors | It runs but cannot find Assetto Corsa or shows a missing file |
| Runtime errors | It opens but a feature breaks — server browser, CSP panel, mod indexing |
| Launch errors | Assetto Corsa starts in the default launcher instead of in Content Manager |
The errors you will actually see
"Could not find Assetto Corsa folder" / "Game directory does not exist"
Cause. The launcher has lost the path to your Assetto Corsa install. This happens after a Steam library move, a fresh Windows install, or simply if the app was opened before Assetto Corsa was finished installing.
Fix. Open Settings → Content Manager → General and use the Browse
button to point the app at the Assetto Corsa folder. The default location is
C:\Program Files (x86)\Steam\steamapps\common\assettocorsa, but Steam
libraries can sit anywhere. Save the change and the launcher reindexes content
automatically. If Steam itself does not yet see Assetto Corsa as installed, fix that
first; the launcher can only point at a real install.
"Could not load file or assembly" / .NET Framework error
Cause. The app depends on a .NET Framework runtime that is either missing or older than the build needs. Newer versions of the app assume .NET Framework 4.8, which is not present by default on older Windows installs.
Fix. Download the latest .NET Framework 4.8 from Microsoft, install it, restart Windows, and start Content Manager again. The vast majority of "could not load" errors clear after a clean .NET update. If the error persists, re-download the launcher from the official source — a partial download is the second most common cause.
"Windows protected your PC" SmartScreen prompt
Cause. Windows SmartScreen shows a generic caution for any program that is not widely distributed through the Microsoft Store. Content Manager is a third-party application, so it triggers this prompt on first run. It is not an error and not specific evidence of a problem.
Fix. Choose More info, then Run anyway. As long as the file came from the official source at assettocorsa.club, it is the genuine, clean application. After the first launch, Windows usually remembers the choice and stops showing the prompt.
"Failed to load some data" or stale mod index
Cause. A mod has been added or removed outside the app and the launcher's cached index no longer matches the contents on disk. This is the most common "feature is broken" error after manually copying files into the Assetto Corsa folder.
Fix. Inside the app, click Settings → Content Manager → Content and select Reload all content. The launcher rebuilds its index from disk and the error clears. If a specific mod refuses to load, check that its folder structure matches the standard layout — broken folder structure is the underlying problem in roughly nine cases out of ten.
Online server browser empty or "Cannot retrieve server list"
Cause. The launcher could not reach the lobby service. A firewall or antivirus is the most common culprit, followed by Steam not being signed in and a brief outage of the lobby itself.
Fix. Confirm Steam is running and signed in. Allow Content Manager through Windows Defender Firewall (Settings → Update & Security → Windows Security → Firewall & network protection → Allow an app). Wait a minute and refresh the server list. If servers still do not appear, the lobby is probably briefly unreachable — try again in five minutes.
Assetto Corsa launches in the default launcher, not Content Manager
Cause. The launcher replacement option has not been applied. Steam's Play button still calls the original Kunos launcher, which means Content Manager never gets a chance to start a session.
Fix. Open Settings → Content Manager → Steam Integration and choose Replace original launcher. Click Apply and confirm the prompt. From then on, the Play button in Steam opens Content Manager, and the original launcher stays in place as a fallback in case you ever want it back.
A general checklist
When an error does not fit any of the named cases, the same short checklist clears most of the remainder.
- Re-download Content Manager from the official source. A partial or interrupted download is the single most common hidden cause.
- Run as administrator once. Right-click the executable and choose Run as administrator on the first launch to set permissions correctly.
- Unblock the file in Windows. Right-click → Properties → tick the Unblock box → Apply. Windows sometimes marks a downloaded file as untrusted in a way that breaks specific features.
- Update Windows and your GPU driver. Out-of-date components account for many issues that look like Content Manager bugs but are actually Windows-side.
- Check antivirus quarantine. A false positive can remove files Content Manager needs. Restore the quarantined file and add an exception for the app folder.
If a problem persists after that checklist, our main troubleshooting guide covers crash patterns and CSP-specific failures in more depth.
Content Manager errors — common questions
Why does Content Manager show "could not find Assetto Corsa"?
The launcher has lost the path to the game folder. Open Settings → Content Manager → General and use the Browse button to point it at the Assetto Corsa install directory inside Steam. The path is usually \Steam\steamapps\common\assettocorsa. Save the change and restart the app.
What is the "Could not load file or assembly" error in Content Manager?
It means a required .NET Framework component is missing or out of date. Install the latest .NET Framework 4.8 from Microsoft, restart Windows, and run the app again. The vast majority of "could not load" errors clear after a clean .NET update.
Why does Windows warn me when running Content Manager?
Windows SmartScreen flags any program that is not widely distributed through the Microsoft Store, including Content Manager. It is not an error and not specific evidence of a problem. Choose "More info → Run anyway" on the genuine file from the official source; it is safe to allow.
Why is the online server browser empty in Content Manager?
Either a firewall is blocking the lobby ping, or your account is not signed into Steam, or the official lobby list is briefly unreachable. Confirm Steam is running, allow the app through your firewall, and wait a minute before refreshing. The list normally repopulates within seconds.
Why does Assetto Corsa open in the default launcher instead of Content Manager?
The "replace default launcher" option has not been applied. Open Settings → Content Manager → Steam Integration inside the app and choose Replace original launcher. Steam will then route every Play click through Content Manager. The original launcher stays on your system and can be restored later.
Does reinstalling Content Manager lose my settings?
No. The app is a portable application, so its settings, presets and indexed content paths sit in a configuration folder that survives reinstall. Replacing the .exe with a fresh copy from the official source resets nothing user-facing. Mods stored inside Assetto Corsa are equally untouched.
Still stuck?
Our main troubleshooting guide covers the wider set of problems that are not strictly errors — slow performance, missing cars, crashes during a race. Start there if the named errors above did not help.
Open the troubleshooting guide