WHAT I FOUND ON MY PC
2.50 GiB
The configuration file contained 2,684,433,097 bytes. A normal configuration should be tiny by comparison.
%APPDATA%\CitizenFX\fivem.cfg
Root cause
What went wrong
After a FiveM crash, the persistent fivem.cfg file became massively bloated with configuration and saved binding records. FiveM then had to process that file during every launch.
That processing created heavy CPU, memory, and page-fault activity before FiveM could finish initializing its Chromium/NUI interface. The Rockstar Launcher popup was visible during the process, but it was not the underlying cause in the confirmed case.
This is a targeted fix, not a universal cache-clearing recommendation.Check the file size first. If
fivem.cfg is already small, stop here and investigate a different cause.Recognition
Symptoms that matched
Long repeatable delayFiveM stays in the background for roughly 10–20+ minutes.
Works outside FiveMGTA V and Rockstar Launcher start normally by themselves.
Runaway resourcesFiveM subprocesses consume several gigabytes of memory and heavy CPU.
Broken main menuGhosted text, repeated layers, missing cards, or severe NUI corruption.
Started after a crashThe behavior begins suddenly even though the computer previously ran FiveM correctly.
Reinstall did nothingFiveM, GTA V, and Rockstar reinstalls do not change the delay.
Read-only check
Check whether the file is abnormal
Close FiveM normally
Exit FiveM, then open Task Manager and confirm there are no remaining FiveM processes. Do not force-close processes unless the program is genuinely stuck.
FiveM.exe
FiveM_*_GTAProcess.exe
FiveM_ChromeBrowser.exe
FiveM_ROSLauncher.exe
Open the roaming CitizenFX folder
Press Windows + R, paste the following path, and press Enter:
%APPDATA%\CitizenFX
The expanded path is normally C:\Users\<username>\AppData\Roaming\CitizenFX.
Inspect fivem.cfg
Right-click fivem.cfg, select Properties, and check its size. A file measured in hundreds of megabytes or gigabytes is clearly abnormal.
Optional read-only PowerShell check:
Get-Item "$env:APPDATA\CitizenFX\fivem.cfg" |
Select-Object FullName, Length, CreationTime, LastWriteTime
Select-Object FullName, Length, CreationTime, LastWriteTime
Safe recovery
Perform the reversible reset
Warning before making the changeThis can reset FiveM client preferences and custom key bindings. Back up the file instead of permanently deleting it.
Create a backup folder outside CitizenFX
For example, create FiveM-Config-Backup on the Desktop. Do not upload the raw configuration publicly because it can contain personal settings and bindings.
Move only fivem.cfg into the backup
Move %APPDATA%\CitizenFX\fivem.cfg out of the CitizenFX folder and rename the backup to something obvious, such as fivem.cfg.backup.
Do not delete or move the other CitizenFX files. Do not restore the oversized file after the test.
Launch FiveM Production once
Start FiveM normally. It should load with default client settings and create a fresh, small configuration when needed.
Confirm the result
If the menu opens promptly and renders correctly, the oversized configuration was the cause. Reconfigure preferences and keybinds manually rather than copying the old file back.
Decision point
Does this fix apply?
File is huge
Hundreds of MB or multiple GB strongly indicates corruption. Back it up, move it out, and test a fresh launch.
→
File is already small
Do not delete random folders. This specific diagnosis is not confirmed; collect startup logs and process evidence instead.
Verified case
Evidence supporting the diagnosis
| Damaged file | %APPDATA%\CitizenFX\fivem.cfg |
|---|---|
| Measured size | 2,684,433,097 bytes (2.50 GiB) |
| Before reset | Approximately 20-minute delay, multi-gigabyte memory usage, high CPU/page faults, and corrupted NUI. |
| After backup | FiveM passed the Rockstar handoff, created its rendering backbuffer within roughly one minute, and opened normally. |
| Why reinstall failed | The roaming CitizenFX configuration was outside the normal FiveM installation directory and survived reinstalls. |
Avoid collateral damage
What not to do
- ×Do not reinstall GTA V or Rockstar Launcher before checking this single file.
- ×Do not delete the entire CitizenFX folder as the first test.
- ×Do not restore the oversized configuration after FiveM works.
- ×Do not assume every slow startup has this cause; confirm the file size.
- ×Do not publicly share the raw configuration file.
Next steps
If FiveM still does not load
A small fivem.cfg, or no improvement after isolating an oversized one, means a different issue is involved. Preserve the backup and collect:
- The newest
CitizenFX_log*.logfiles from%LOCALAPPDATA%\FiveM\FiveM.app\logs - FiveM subprocess names, memory, CPU usage, and command lines
- Windows Application events for crashes, hangs, Direct3D, DXGI, and display drivers
- The exact GTA V installation path and FiveM
CitizenFX.iniIVPath
Success criteriaFiveM reaches the main menu in a normal amount of time, the menu renders correctly, and resource usage no longer grows uncontrollably.