The quick answer

What does “checksum failed” mean in Assetto Corsa?

The server compared a required car or track file on your computer with its own copy and found that they are different. Find the affected asset, remove the old local copy, install the exact same archive and version used by the server, and reconnect. If every driver is failing, re-upload or reapply the intended asset on the server, restart it, and test again.

Matching names are not enough. Two folders can have the same name while containing different data, physics, layouts, or updates.

Still configuring content?

Compare your workflow with the guides for adding cars to the server and adding tracks and layouts.

Step 1

Understand what the server is rejecting

Assetto Corsa uses checksums to keep important server and client content consistent. A mismatch can change physics, collisions, timing, or track behavior, so the connection is rejected before the driver enters the session.

Different mod versionThe server has one car or track release and the driver has another.

Files were overwrittenAn update was installed on top of an old copy and left mixed data behind.

Content was editedPhysics, data, track, or extension files were changed after installation.

Wrong track layoutThe selected server layout differs from the one expected by the client package.

Do not bypass the check

Disabling validation only hides the mismatch. It can let drivers use inconsistent content and make later problems much harder to diagnose. Fix the files instead.

Step 2

Identify the car, track, or layout that does not match

Start with the connection error and the server’s active Content selection. The most useful clue is whether the failure affects one person or everyone.

1
Read the full error.
Record any car ID, track ID, layout, or file name shown with “checksum failed.”
2
Check who is affected.
If one driver fails, their local copy is the likely problem. If every driver fails after a change, inspect the server copy first.
3
Review the active session.
Compare the selected Track and every car in Current Entry List with the content the driver installed.
4
Test one variable at a time.
Use a known-good car on the same track, or the same car on a known-good track, to narrow down the mismatch.

Fast diagnosis

One affected driver usually points to a local installation problem. Everyone failing at once usually points to the server package, active selection, or a newly changed requirement. If the lobby has never launched cleanly, work through the complete server setup guide first.

Step 3

Compare the exact content versions

Confirm the source and release of the problem asset. The safest approach is to have the server owner and every driver install from the same original archive or download link.

Compare the internal car or track ID, version number, and layout name when available.
Confirm everyone used the same download source rather than similarly named uploads.
Check whether a league pack, skin pack, or physics update replaced files after installation.
For a multi-car session, verify every selected car—not only the car the affected driver chose.
For a multi-layout circuit, confirm the exact GP, short, drift, or endurance configuration.

Same folder name, different files

Renaming a mod folder or comparing only its display name does not make two installations identical. Replace the content with one known-good package.

Step 4

Clean-reinstall the affected content locally

Installing over the existing mod can leave outdated files behind. Remove the affected copy before installing the known-good archive.

1
Close Assetto Corsa.
Exit the game and stop any active Content Manager launch before changing content files.
2
Back up custom changes.
Save any personal setup or edited files you intentionally want to keep outside the active content folder.
3
Remove the affected installation.
Delete or move the complete car, track, or layout folder so stale files cannot remain.
4
Install the shared archive.
Use the exact package supplied for the server and preserve its folder structure.
5
Do not restore edited data yet.
Test the clean version first. Add optional changes only after the server accepts the connection.

Content Manager users

Confirm the installer is targeting the correct Assetto Corsa installation. A second game library can leave you updating a folder the game is not using.

Step 5

Re-upload or reapply the intended server content

If several drivers fail, make the server copy the known-good source. Open the server’s Content tab and review the active selection before restarting.

1
Verify the Asset Library copy.
Confirm that the intended car or map is present and that its upload finished processing.
2
Replace the wrong version.
Remove the outdated server asset when needed, then upload the same archive distributed to drivers.
3
Rebuild the active selection.
Select the correct map, layout, cars, skins, and entry counts.
4
Press Apply Selection.
Wait for the panel to finish saving and installing the content before restarting.

Step 6

Check the track layout and CSP requirements

A server can use the right track package and still reject clients when the selected layout or extended-physics requirements do not match.

Open Change Map and verify the exact selected layout.
Confirm the layout exists in the package installed by every driver.
Enable extended physics only when the selected car or track requires it.
Set a compatible minimum CSP version and tell drivers which version is required.
Remove optional extensions temporarily if the checksum issue began after adding them.

Change one requirement at a time

Do not replace the track, change the layout, and enable new CSP options in one test. A single controlled change makes the cause much easier to confirm.

Step 7

Restart the server and run a clean connection test

1
Restart after Apply Selection.
Wait until the content operation finishes, then use Restart in the server header.
2
Watch the Console.
Confirm the expected track, layout, and cars load without content errors.
3
Join with a clean client.
Use Join in CM from a computer that has the freshly installed shared archive.
4
Test a second driver.
If the first test succeeds, ask another driver to reinstall from the same source and connect.

The server returns to Online after restarting. Session Details shows the intended track and layout. Every active car comes from the shared version. The test computer has a clean copy from the same archive. The test driver joins without a checksum error. A second driver can complete the same connection test.

Step 8

Use the failure pattern for advanced troubleshooting

What happens	Most likely cause	What to do next
Only one driver fails	Their local car or track copy differs from the server.	Clean-reinstall the named asset from the server owner’s exact archive.
Every driver fails	The server has the wrong package or an incomplete upload.	Replace the server copy, rebuild the selection, apply it, and restart.
The error started after a mod update	Old files remain beside the updated files.	Remove the complete old folder on both sides before reinstalling.
The track works offline but fails online	The server uses different data or another layout.	Compare the exact layout and reinstall one shared track package.
One car fails in a multi-car session	That entry uses a different car version or edited physics.	Remove the car from the entry list to confirm, then replace its package.
The error remains after reinstalling	The copies still came from different sources, or optional files were restored.	Use one untouched archive everywhere and test before adding extensions.
The problem follows a CSP change	Extended physics, extensions, or minimum-version requirements differ.	Align CSP requirements and test with optional extensions disabled.

FAQ

Assetto Corsa checksum failed questions

Can I ignore or disable a checksum failure?

You should not use that as the fix. The check protects the session from mismatched physics and track data. Install identical content on the server and clients instead.

Does the same mod name mean the files match?

No. Different releases and edited packages often use the same display name or folder ID. Use the same untouched archive and version for everyone.

Should I update the server or the players?

Choose the version intended for the event, then install that exact version everywhere. If the server has the correct package, update the affected players; if everyone fails, replace the server copy first.

Can stock Assetto Corsa content fail a checksum?

Yes. Modified, damaged, or incomplete stock files can also differ. Verify the game files through the platform that installed Assetto Corsa, then retest without custom edits.

Why does only one track layout fail?

Layouts can contain their own data and extensions. Confirm the server selected the expected layout and that every driver installed a package containing the same layout files.

Does CM Auto Download fix a checksum mismatch?

CM Auto Download can help drivers find compatible content when configured, but it cannot make two existing versions identical automatically. The driver still needs the exact package used by the server.

Ready to test the fix?

Start with a free 4-player server

Upload the matching car and track packages, apply the setup, and run a clean connection test with the panel shown in this guide.

Start Free Server Browse More Guides