How to update Content Manager safely
Updating Content Manager is a two-minute job — download the latest executable, swap it into place and relaunch. This guide covers the safe update path, optional backups, keeping Custom Shader Patch in sync, and rolling back if a new build misbehaves.
When and why to update Content Manager
Content Manager updates often. Most releases are small — a fix here, an interface tweak there — and some bring larger improvements to the Custom Shader Patch integration or the online server browser. The launcher itself is small enough that an update is never a major event: download a new copy, replace the file, relaunch. The whole process takes a few minutes.
That said, you do not need to chase every build. Many players update once a month, or whenever a new feature they want is announced, rather than every time a fresh release appears. If your current Content Manager is working well, the safest practice is to note the version, keep a copy of the executable somewhere, and update on your own schedule. The official page at assettocorsa.club always holds the latest release plus recent past builds for rollback purposes.
If you are setting Content Manager up for the first time rather than updating, our download guide walks through the initial install. If you have run into an issue that looks like a bug, the common errors page is the right place to start. Updating is almost never the fix for a problem that is actually misconfiguration.
How to update the launcher — full procedure
Six steps from a stable old build to a verified new one, with a clean rollback path if needed.
-
Check your current Content Manager version
Open the launcher, then go to Settings → About. The version number is shown at the top of that panel. Make a note of it so you can confirm the update later. The same panel also shows the Custom Shader Patch build currently installed.
-
Back up your settings (optional but recommended)
The app is a portable application — your settings live in its configuration folder rather than the Windows registry. Copy the Cfg subfolder somewhere safe before updating. This protects custom presets, server favourites and configuration tweaks if you ever want to roll back.
-
Download the latest Content Manager from the official source
Visit assettocorsa.club and download the current release. The official page always carries the latest build — there is no separate updater installer and no third-party mirror you should use instead.
-
Close the running launcher
Fully exit the launcher before replacing the executable. If the launcher is open, the file is locked and the update will fail with a write error. Right-click the Content Manager system-tray icon and choose Exit if it is hidden there.
-
Replace the launcher executable
Move the new file into the same folder, overwriting the old executable. Because the launcher is portable, no installer step is required — the file is the application. Your settings, presets and the linked Assetto Corsa folder all survive the swap.
-
Launch and verify the new version
Start the launcher again. The first launch indexes content briefly. Once the main view appears, open Settings → About and confirm the version number matches the build you downloaded. If the indexer reports missing data, choose Reload all content and the launcher rebuilds its cache cleanly.
Do I need to update Custom Shader Patch at the same time?
Custom Shader Patch is a separate project with its own release cycle. Updating Content Manager does not change your CSP build, and updating CSP does not require a new Content Manager. The two are loosely coupled, which is exactly what makes the combination reliable in the long term.
That independence is also what lets you experiment safely. If a fresh Content Manager release behaves oddly with the CSP version you are running, switch to a slightly older launcher; if a new CSP build introduces problems on a particular track, roll back the patch through the dedicated CSP section inside the launcher without touching the launcher itself. Both updates are reversible, and neither cascades into the other. Our Custom Shader Patch guide covers the patch's own install and version-switching workflow in detail.
What to do if a launcher update misbehaves
The vast majority of updates pass without incident. If a fresh build does cause a problem — the launcher refuses to start, a feature is missing, the server browser behaves oddly — three steps clear most cases.
- Restart Windows and try again. A stale lock on the previous launcher, an antivirus quarantine in progress, or a partly-flushed cache can each cause a clean update to look broken on the first run.
- Reload all content. Settings → Content Manager → Content → Reload all content rebuilds the cached mod index. Many "missing car" reports clear after a single reload.
- Roll back to the previous build. Replace the new executable with the older copy you kept aside. Your settings, content paths and Custom Shader Patch installation survive intact, so the rollback takes seconds.
If the problem persists across versions, it is almost certainly not the update itself. Our common errors page covers the named issues that explain most of those situations.
Updating the launcher — common questions
How often does Content Manager update?
Content Manager receives updates regularly — typically every few weeks for small fixes, with larger feature releases spaced further apart. The developer x4fab publishes each build at assettocorsa.club. There is no fixed schedule; check the official page when you want the current release.
Does Content Manager update itself automatically?
Yes, Content Manager can notify you of new builds and download them in the background. The toggle lives in Settings → General. Many players turn auto-update on and let the launcher handle it; others prefer manual control over which build is installed.
Will updating the launcher break my mods?
Updating the launcher does not touch your installed mods, settings or Custom Shader Patch build. The executable is replaced; the Assetto Corsa folder and the Content Manager Cfg subfolder are left alone. If a new launcher build genuinely misbehaves, you can roll back to the previous one in seconds.
How do I roll back a Content Manager update?
Keep a copy of the previous executable in a separate folder before updating. To roll back, close the running launcher, move the older executable back into place and start it again. Your settings and content paths are unaffected. Past builds are also archived on the official site.
Should I update Custom Shader Patch at the same time?
CSP and Content Manager are separate projects with separate release cycles, so an update to the launcher does not require a CSP update. The CSP version manager inside the app lets you upgrade CSP independently and roll it back if a new build introduces problems with a specific track or car.
Why did Content Manager fail to update?
The most common cause is the launcher still running when you tried to replace the file — Windows locks the executable while it is open. Exit the launcher fully, including any system-tray icon, then try again. Antivirus or Windows Defender can also intervene; restore the file from quarantine and add an exception.
Get the current Content Manager build
The latest release lives at the official source. CM Hub links you straight to assettocorsa.club, where every fresh build is published.
Open the download guide