Clear only the data relevant to a documented symptom, after closing FiveM and saving your settings. Cfx.re specifically names caches.xml for certain component-loading errors. Deleting every FiveM folder is a much broader reinstall-like action.
01 / First check
Find the exact trigger
Cfx.re specifically names caches.xml for certain component-loading errors. Deleting every FiveM folder is a much broader reinstall-like action.
02 / Fix it in order
Four focused checks
Make one change at a time and retest the original symptom.
Record the error first
Write down the exact message and check Cfx.re’s client issue guide. If the error is server-specific, contact that owner first.
Close FiveM
Exit the game and launcher; confirm no FiveM process remains in Task Manager.
Open application data carefully
Use Win+R with %localappdata%\FiveM and inspect the FiveM.app folder. For the documented component error, back up then remove caches.xml if present.
Relaunch and retest
FiveM may rebuild data. If the error remains, follow the matching official issue-specific instructions instead of deleting unknown folders or save data.
03 / Still have questions?
Quick answers
What should I check first?
Cfx.re specifically names caches.xml for certain component-loading errors. Deleting every FiveM folder is a much broader reinstall-like action.
Does this error always have one cause?
No. The same symptom can come from different client, server, or asset conditions. Use the exact message and a repeatable test.
Should I delete all FiveM data?
No. Preserve the error and settings first. Follow only the targeted official instruction that matches your symptom.
When should I contact the server owner?
If the problem happens only on one server or with one server asset, send the owner the steps, time, and exact error.
How do I know the change worked?
Repeat the same test after one change and compare the result. For server changes, check with multiple players on staging.