BustedLoops
Loops health
ISSUERSI LauncherError 5014Installation

RSI Launcher install or Verify fails with Error 5014

Tracked since 14 Sept 2026 · Last researched 14 Sept 2026

Problem

Star Citizen installation or file verification fails with RSI Launcher Error 5014 under Launcher 2.17.0. The current game family is Alpha 4.10 LIVE.

CIG's current 50XX support page does not list 5014 or define its cause. Exact-code reports come from one current discussion and disagree about storage, registry, download-limit, and VPN changes.

Applies to Alpha 4.10 LIVE / RSI Launcher 2.17.0; official build authority identifies 4.10.0-live.12519617 · Current

Best current action

Restart the RSI Launcher once before changing settings

Fully close the launcher, including its system-tray process, reopen it, and retry once. This is CIG's lowest-impact general 50XX step, not a proven Error 5014 fix. If 5014 returns, use log.log to select a matching path, storage, or network route instead of cycling generic fixes.

CIG recommends a complete launcher restart for general 50XX failures. No source confirms that it fixes 5014 specifically, but it is the least disruptive action before the cause is known.

What to do

  1. Exit Star Citizen and the RSI Launcher.
  2. Check the Windows system tray and close any remaining RSI Launcher instance.
  3. Open the launcher, sign in, and retry the interrupted install or verification once.
Limited SupportLow riskRSI Launcher 2.17.0 with Alpha 4.10 LIVE; general 50XX guidance rather than an exact 5014 result

Another option

If the Game Library Folder does not match the intended Star Citizen folder

Correct a mismatched Game Library Folder

CIG includes the library path in its Windows installation checks. Change it only when the launcher visibly points somewhere other than the intended game folder.

What to do

  1. Open RSI Launcher Settings and select Games.
  2. Compare the selected channel's Game Library Folder with the intended Star Citizen installation folder.
  3. If they differ, enter the intended folder and apply the change.
  4. Retry the interrupted install or verification once.

First confirm that the displayed Game Library Folder actually differs from the intended location.

Limited SupportLow riskCurrent Windows installation guidance; no exact 5014 success is documented

If the failed target is M.2 NVMe and a separate compatible SSD has enough space

Try a separate non-NVMe SSD

One player in the current exact-5014 discussion reported that moving the install from an M.2 NVMe drive to a conventional SSD worked. There is no independent repeat or known success rate.

What to do

  1. Choose a separate SSD with enough free space.
  2. Set that drive as the RSI Launcher Game Library Folder.
  3. Start the installation again.

A separate compatible SSD with sufficient free space must be available. This can consume substantial storage and may require a full new download.

Moderate SupportMedium riskOne Launcher 2.17.0 exact-code report; limited to systems with an alternate SSD

If log.log shows repeated download retries or files already in use near the failure

Limit concurrent downloads and download speed

One current participant with mixed 50XX failures reported success with ten concurrent downloads and a 5,000 KB/s cap when the log showed retries and files already in use. Exact 5014 applicability is not confirmed.

What to do

  1. Use this route only when log.log shows repeated download retries or files already in use.
  2. Open RSI Launcher Settings and select Download.
  3. Set concurrent downloads to 10 and the speed limit to 5,000 KB/s.
  4. Retry the download once.

Check the launcher log first and use this only for matching retry or file-lock entries. The download will run more slowly while these limits are active.

Moderate SupportLow To Medium riskLauncher 2.17.0 discussion; mixed 50XX report rather than an independent exact-5014 repeat

If log.log points to a network-path or repeated-download failure rather than storage or permissions

Make one trusted-VPN retry for a network-path failure

The current exact-code discussion contains one VPN success and one mixed-50XX failure. That conflict supports a single test only when the launcher log points to the network path.

What to do

  1. Use this route only when log.log shows a network or repeated-download failure.
  2. Connect to a trusted VPN endpoint.
  3. Retry the interrupted download once.
  4. Disconnect the VPN after the installation finishes.

Use a trusted VPN only after the launcher log shows a matching network or repeated-download failure. The download passes through the VPN provider and may be slower.

Limited SupportLow To Medium riskLauncher 2.17.0 exact-code discussion with conflicting outcomes

Diagnostic checks

These checks can identify the affected state, but they are not fixes.

Read log.log after one fresh failure

The launcher log can expose the lower-level install, file, permission, or network error hidden behind the general code. That detail is more useful than trying every suggestion.

What to check

  1. Reproduce Error 5014 once and note the time.
  2. Press Windows+R and open %appdata%\rsilauncher\logs.
  3. Open log.log and read the newest entries around the noted time.
  4. Keep the log for RSI Support; do not post the full file publicly.

The full log can contain system or account context. Share it only with RSI Support staff.

Limited SupportLow To Medium riskCurrent RSI Launcher support procedure

Report persistent Error 5014 with the matching context

CIG does not currently map 5014 in its 50XX article. A precise Issue Council contribution can establish reproduction data, but submitting it will not restore the install.

What to check

  1. Search the Launcher project in Issue Council for Error 5014 before creating a report.
  2. Contribute to a matching Open, Confirmed, or Under Investigation report, or create a new report if none matches.
  3. Record RSI Launcher 2.17.0, the LIVE or PTU channel, whether Install or Verify failed, the install drive type, and the relevant log message.
  4. Send the full launcher log only through RSI Support if private diagnostic files are requested.
Limited SupportLow riskPersistent Launcher 2.17.0 failures on LIVE or PTU

Other options

Check the target NVMe volume's physical sector size

If Windows 11 is in use and the failed install target is an NVMe volume

Microsoft documents this read-only check, but a value above 4096 bytes is not proven to cause every Error 5014. Its purpose here is to decide whether the later registry route is even applicable.

Steps

  1. Open an elevated Command Prompt.
  2. Run fsutil fsinfo sectorinfo followed by the target volume, such as D:.
  3. Read PhysicalBytesPerSectorForAtomicity and PhysicalBytesPerSectorForPerformance.
  4. Treat the larger value as the physical sector size; a value above 4096 bytes matches this diagnostic condition.

Run the check against the same volume targeted by the failed installation or verification.

UnverifiedLow riskWindows 11 NVMe diagnostic; not an independently verified Error 5014 cause

Reinstall only after lower-impact routes fail

CIG places full deletion and reinstall last. The only exact-thread recovery that included a reinstall also changed the path, cache files, and registry, so the successful part cannot be isolated.

Steps

  1. Back up any custom mappings or user.cfg files that must be preserved.
  2. Follow CIG's complete launcher and game deletion instructions.
  3. Install the current RSI Launcher from the official download page.
  4. Set the intended Game Library Folder and download Star Citizen again.

Use this only after lower-impact official and log-selected routes have failed. High cost: this removes local launcher and game files, uses substantial time and bandwidth, and can lose custom files that were not backed up.

Limited SupportHigh riskCurrent generic 50XX last resort; no isolated exact-5014 reinstall result

If lower-impact paths fail

Escalation

If Windows 11 and the target NVMe volume reports a physical sector value above 4096 bytes

Escalate to the Windows 11 NVMe sector-size registry change

The setting makes Windows report 4-KB sectors to software when the target NVMe volume exposes a larger physical value. Exact-5014 outcomes conflict, so this is not a general fix.

What to do

  1. Use the sector-size check first and continue only on Windows 11 with an NVMe volume reporting more than 4096 bytes.
  2. Back up the registry or ensure a recovery path is available.
  3. Open Command Prompt as administrator.
  4. Run REG ADD "HKLM\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" /v "ForcedPhysicalSectorSizeInBytes" /t REG_MULTI_SZ /d "* 4095" /f.
  5. Restart Windows.
  6. Retry the Star Citizen installation.

Complete the read-only sector-size check first and continue only when the target NVMe volume reports a value above 4096 bytes. High risk: this changes a machine-wide storage-driver setting and requires a reboot. Back up the registry or have a recovery path ready; an incorrect edit can cause serious problems.

Limited SupportHigh risk

What's not worth trying

Do not treat Clear Launcher Cache as a 5014 fix

UnverifiedLow risk

Clearing the launcher cache is general CIG 50XX guidance, but it did not recover the exact reporter's 5014 failure. Repeated clearing has no exact-code success here.

Do not rely on Run as administrator alone

ContradictedLow To Medium risk

Running the launcher as administrator failed for the exact reporter, and no retained exact-5014 success supports it as a standalone route.

Do not loop Verify after it returns 5014

UnverifiedMedium risk

Verify is general CIG advice for 50XX errors, but the exact incident can occur during Verify itself. Repeating it without a new log-selected change is not a demonstrated recovery.

Boundaries and evidence

This page covers the exact 5014 code during Install or Verify. It does not cover API-denied Error 403 access or assume that advice for another numbered 50XX error applies to 5014.

CIG does not currently name Error 5014, define its lower-level meaning, link an Issue Council ticket, or publish a code-specific fix or success rate.

All exact-code outcomes are from one Launcher 2.17.0 Reddit discussion. No report includes a complete launcher log or the exact Alpha 4.10 hotfix, and no result has an independent repeat.

Storage, registry, reinstall, VPN, and throttling outcomes are mixed or confounded. A coincidental recovery cannot be assigned confidently to one change.

The steps on this page were not independently reproduced. Direct Issue Council details and the full Spectrum announcement were not publicly inspectable.

Data sources

RSI Support · RSI · Issue Council · Reddit · Specialist Community