No issues logged
The log opens on November 19, 2026, at the midnight unlock. The first entry appears the day the first problem clears the two-source bar, and not before.
This page is the problem list for launch night, kept separate from the version log on purpose. The Patch Notes page records what Rockstar changes, update by update. This page records what players hit, problem by problem: what broke, when it was first verified, what its status is right now, and the fix when one exists. It opens for entries on November 19, 2026, the day the game does, because a known-issues list for an unreleased game would be fiction.
There are no known issues, because the game is not out. GTA VI releases Thursday, November 19, 2026, and nothing can be broken in a game nobody can play yet. This tracker activates at launch: from the midnight unlock onward, every problem that clears the bar below gets an entry here with its first-verified time on it. Preload trouble in the meantime is real, common, and already covered: the preload fixes page handles it symptom by symptom, and live service problems are tracked on the server status page.
Two sources, same as everything on this site. An issue earns an entry when Rockstar or a platform holder acknowledges it, or when two independent, named sources report the same failure in the same terms. A pile of social posts about one screenshot is a lead, not an entry. The tracker would rather be an hour late and right than first and wrong, because on launch night a wrong "fix" costs players real time.
Every entry is timestamped and carries one of three statuses.
Entries are never deleted when they resolve. They move status, keep their timestamps, and stay in the log, because "was this ever fixed" is a question players ask for months.
The log opens on November 19, 2026, at the midnight unlock. The first entry appears the day the first problem clears the two-source bar, and not before.
Launch problems are rarely exotic. They cluster in four places, and each one already has a page on this site doing the work, so on the night, start where your symptom lives.
The biggest cluster, and the earliest: the preload never started, there is no download button, or the install runs out of space at the worst moment. The preload fixes page covers each symptom in the order to check it, from the missing download button to not enough space, built from Rockstar's Pre-Load FAQ and official console troubleshooting.
Boxed copies are a download code in a box, on sale since November 12, and code redemption has its own rules: PS5 codes redeem only on accounts in the matching region group, Japanese codes expire 170 days after issuance, and Xbox codes are not region-locked. The editions guide's boxed section has the full rules, and the region-lock Report works through what Rockstar Support confirmed.
A download frozen at one percentage for hours, or a finished install behind a padlock, is usually the store or a licence check rather than the game. The fixes page has both: download stuck, paused or crawling and installed but will not open, including restoring licences on PS5. If the cause turns out to be a platform outage, the server status page is where it will be confirmed.
Xbox One owners play through Xbox Cloud Gaming at Series S settings, and streaming adds its own failure modes: queue times, soft pictures, input delay on a strained connection. Rockstar's own caveat says connection factors may influence performance in ways local play never sees. The cloud streaming Report covers the arrangement and the catch, and the Online and PC page tracks the wider picture.
Server status answers "is the service up" for Rockstar, PlayStation and Xbox, checked by hand against the official pages. This tracker answers "what is broken, for whom, since when, and what fixes it", entry by entry, including problems that are not outages at all, like a licence error or a code that will not redeem.
Patch Notes is the version log: what each update changed, from Rockstar's official notes. This page is the problem log: what players hit. The two cross-link. An issue closes here as "Fixed in patch" with a link to the version entry there that fixed it.
Through the Suggest page, under "Fix or correction", with your platform and the exact error message if there is one. Reports are leads: an entry still needs the two-source bar, but a clear reader report is often the first lead that gets an issue verified.