Gaming

Rockstar Games Launcher

Rockstar Games Launcher stores local Chromium Embedded Framework cache data and launcher logs under the user's LocalAppData profile to speed up sign-in screens, store downloaded web assets, and remember storefront and social features between launches. That cache can include HTTP disk cache entries, cookies, GPU shader and render cache files, and other browser-style temporary data, while the logs record launcher startup, patching, authentication, and connectivity events. Kudu removes those temporary cache and log files without touching installed games, save data, account details, or launcher settings.

Why clean Rockstar Games Launcher?

  • Stale Chromium web cache can leave the sign-in or storefront view stuck on an old page, causing blank panels, endless loading spinners, or buttons that do nothing
  • Invalidated GPU cache after a graphics driver update can break hardware-accelerated launcher rendering, showing black windows, flickering text, or missing images until the cache rebuilds
  • Corrupted cookies or cached session data can trap the launcher in repeated login prompts or Social Club authentication loops even when the account password is correct
  • Outdated cached patch and news assets can make the launcher display incorrect game status, old promotional panels, or failed update checks until fresh files are downloaded
  • A bloated disk cache slows launcher startup because Chromium has to scan and evict old entries, which users notice as a long delay before the window becomes responsive
  • Large accumulated log files consume space in LocalAppData and make troubleshooting harder by burying current errors under old startup, download, and network records
What gets cleaned

Cache paths Kudu targets

Windows

%LocalAppData%/Rockstar Games/Launcher/cache
%LocalAppData%/Rockstar Games/Launcher/logs
Frequently asked

Common questions about Rockstar Games Launcher

Free & open source

Download Kudu and reclaim your disk space.

Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.