Startup crash troubleshooting
If FF14 crashes on launch, first identify which layer failed: XIVLauncher, the FFXIV game client, or a patch and version check. Then use the least destructive diagnostic order before reinstalling or deleting folders.
An FFXIV launcher crashing on startup is not automatically the same problem as the FFXIV client crashing after you press Play. If XIVLauncher disappears before the login handoff, start with processes, the official release, system time, security software, and launcher logs. If the game window appears and then closes, move to graphics drivers, overlays, and the game client. If you see a patch or boot-version message instead of a crash, use the dedicated error guide instead.
The safest first pass is reversible: confirm that the service is not under maintenance, close every XIVLauncher and FFXIV process, verify the release source, restart Windows, and test once with overlays and recently changed plugins isolated. Do not blindly erase the game, patch, or launcher folders just because a forum post suggests a cleanup shortcut.
| What you see | Likely boundary | Start here | Do not confuse it with |
|---|---|---|---|
| XIVLauncher closes before login or Play appears | Launcher process or startup dependency | Check duplicate processes, release source, clock, security software, and launcher logs | A game-client crash after handoff |
| The FFXIV window opens, then closes or freezes | Game client, GPU driver, overlay, or display path | Disable overlays, update or roll back the graphics driver, and compare a clean launch | A launcher download error |
| A boot-version or version-check message appears | Network, time, service, or launcher update check | Use the boot-version error guide and verify status before reinstalling | A silent process crash |
| A patch file cannot download or the installer reports an error | Storage, permissions, network, or patch service | Use the patch-files guide and preserve files until a supported cleanup is confirmed | A crash on launch |
| Only a plugin-enabled launch fails after a game patch | Dalamud or a plugin compatibility issue | Disable plugins and test the base launcher or client | Proof that the whole launcher installation is corrupt |
Start with the boundary
The phrase ff14 crashing on launch covers several different handoffs. XIVLauncher may close while it is reading its configuration, the official game client may crash after the launcher starts it, or a version check may stop the process with a visible error. The fix that helps one layer can make another layer harder to diagnose.
Watch the last thing that appeared, not only the fact that the window vanished. A launcher that closes before a game window exists points toward launcher state, Windows security controls, or a dependency. A game window that reaches the title screen points toward the client, graphics path, or overlay. A named patch or boot error belongs to a targeted error workflow.
This page uses editorial concept diagrams to show those boundaries. They are not official XIVLauncher screenshots and do not represent a real crash report.
Use the first failing checkpoint
A short controlled test is more useful than repeating a reinstall. Start with no duplicate processes, no overlay, and no recently changed plugin. If the launcher still closes before any game window, keep the investigation on the launcher and Windows boundary. If it reaches the game and then crashes, move the investigation to the client and graphics path.
Change one variable at a time and keep a note of the result. For example, compare a normal network with an alternate trusted network, or compare a plugin-disabled launch with the normal launch. When two changes happen together, you cannot tell which one fixed the crash or which one hid the real cause.
The flow is intentionally conservative because a clean launch is evidence. It is not a promise that one step works for every system, and it does not replace the current official FAQ or release notes.
A stale installer, an interrupted update, and a real startup crash can produce similar search results. Check the official release page and the launcher version first. If the visible message says that XIVLauncher was not able to check the boot version, use the dedicated boot-version guide. If the message says that patch files cannot be downloaded, use the patch-files guide. Those pages cover network, storage, permissions, and service checks in more detail.
If there is no message and the launcher process simply vanishes, record whether a Windows event or security product alert appeared. A quarantined file, a blocked child process, or a missing runtime can explain a silent exit. Use the official download page to compare the source, but do not assume downloading another copy fixes a client or plugin crash.
The same boundary applies to Steam. Steam can launch the game client, while XIVLauncher, Proton, an overlay, or a plugin can be the layer that fails. Follow the Steam Deck and Linux guide for platform setup, then use this page only for the crash checkpoint that remains after the platform is working.
| Setup | Useful first comparison | Avoid assuming |
|---|---|---|
| Windows standalone | Test the official launcher with duplicate processes, overlays, and plugins closed | A crash proves the game folder must be deleted |
| Windows through Steam | Compare the same client path with Steam overlay and other hooks disabled | Steam is always the failing component |
| Steam Deck or Linux | Follow the official platform setup, then compare game mode, desktop mode, Proton, and plugin state | A Windows AppData path applies to the active Proton prefix |
| Dalamud-enabled launch | Test the base launcher/client before restoring plugins | A post-patch plugin failure means the launcher is corrupted |
Separate the layers
XIVLauncher starts a flow; it does not make every later crash a launcher crash. The FFXIV client has its own graphics, account, and display state. Dalamud and individual plugins add another layer that can change after a game patch. Use the last visible handoff to decide which support guidance applies.
A useful test is to remove optional layers temporarily: no overlay, no reshade-style hook, no recently updated plugin, and a normal display configuration. If the base game reaches the expected screen, restore optional components one at a time and stop when the crash returns.
This concept diagram is a plain editorial explanation, not a capture of a real process tree or an official diagnostic tool.
Deleting a game folder, patch cache, launcher configuration, or plugin directory can remove useful logs and reset a working path without identifying the cause. It can also make a patch-download problem look like a new installation problem. Never treat a random answer to what folder should I erase to solve the unable to download error on FFXIV launcher as a universal fix.
Keep a backup or a copy of relevant logs, note the path and error first, and use a cleanup step only when the current official FAQ or a trusted project instruction names the exact target and explains what will be recreated. If your issue is a patch download error, use the dedicated patch-files page instead of this startup-crash page.
Support becomes much faster when the report says which process closed first. Include the platform, whether you use standalone or Steam, whether the game window appeared, whether the crash happens before or after login, the last visible text, and whether a plugin-disabled test changes the result.
Add the approximate time, Windows or Linux distribution, GPU and driver version, display or overlay changes, and the release version you tested. Redact account names, tokens, full home paths, IP addresses, and unfiltered logs. A short description of the first failing checkpoint is more useful than a large unstructured dump.
For official source and support links, use the download guide, the general troubleshooting page, the targeted boot-version or patch-files pages, and the maintained Goatcorp FAQ. If the issue remains unclear, ask in the official support route with the evidence above rather than downloading an unknown crash fixer.
The cause can be a duplicate process, stale or blocked launcher file, incorrect system time, security software, an overlay, a recent plugin, or a game-client failure after handoff. First note whether XIVLauncher closes before a game window appears, then follow the matching boundary instead of reinstalling everything.
Compare a clean launch with Steam and other overlays disabled, confirm the platform and game path, and check whether the game window appears before closing. Steam, XIVLauncher, Proton, the client, and plugins can be separate layers, so keep the test narrow and use the Steam Deck/Linux guide for platform setup.
No. XIVLauncher can close before it hands off to the game, while the FFXIV client can crash after its window opens. A patch or boot-version error is another category. The last visible handoff tells you which page and support path to use.
A plugin or Dalamud update can affect a plugin-enabled launch, especially after an FFXIV patch. Disable optional plugins and test the base launcher or client first. Restore plugins one at a time and check current project guidance before removing files.
Not as a first step. Deletion can remove logs, reset paths, and hide whether the original problem was a patch error, a plugin, or security software. Preserve evidence and use a precisely documented cleanup instruction only when the official FAQ or trusted project guidance calls for it.
A boot-version problem normally shows a named version-check message rather than silently closing. Follow the boot-version error guide for time, service, network, and security checks. If there is no message and the process disappears, continue with the startup-crash triage here.
Record the first process that closed, the last visible message, the time, platform, launcher release, client or driver changes, overlay state, and plugin-disabled result. Share only redacted logs and never include passwords, tokens, private paths, or account identifiers.
Use the official Goatcorp FFXIVQuickLauncher GitHub Releases page or the maintained official entry point. The site's last verified check on 2026-07-30 found 7.0.20 from 2025-12-06, but you should verify the current release before calling an installer latest.