Persistent Universe stuck loading after a party or ship-bed logout
Tracked since 22 Aug 2026 · Last researched 28 Aug 2026
Problem
Persistent Universe entry is stuck on the loading screen after you leave while in a party, run into trouble forming a party, or log out in a ship bed.
CIG still lists this infinite loading screen in Alpha 4.10.x, but it has not announced a fix, said which hotfix introduced it, or published success rates for these steps.
Applies to Alpha 4.10.0 LIVE · Current
Best current action
Try the listed network checks once
Try the listed network checks once. If you left aboard a ship that is still accessible to a friend, use that option instead. Use Character Repair only after the network and system checks, the friend option when it applies, and an Issue Council report because it cannot be reversed.
CIG lists these low-impact checks for this problem. Because there is no Alpha 4.10 success rate, try them once rather than repeating them.
What to do
- Power-cycle the home modem or router.
- Temporarily change VPN state; if using NordVPN, disable Web Protection.
- Close unrelated programs before one retry.
Power cycling briefly interrupts the local connection. Changing VPN state or Web Protection also changes the network security path until you restore the prior setting.
Another option
If you left aboard a ship with a friend and that ship is still accessible to them in game
Have your friend destroy the still-present ship
Use this only if you left aboard a ship that your friend can still access in the same game.
What to do
- Confirm the ship is still present in the friend's game.
- Ask the friend to destroy the ship.
This destroys the ship. No independent Alpha 4.10 report shows whether this succeeds or fails.
Diagnostic checks
These checks can identify the affected state, but they are not fixes.
Check the system and storage requirements
This can reveal a problem with the local system or storage requirements, but it will not fix a problem with the account or game servers.
What to check
- Confirm the computer meets Star Citizen's minimum requirements, especially storage-drive specifications and free space.
Report the unresolved loading state
Record what triggered the loading screen and which steps failed before considering Character Repair. An Issue Council report helps CIG investigate but does not restore access.
What to check
- Record the steps that led to the loading state and every workaround attempted.
- Add the findings to Issue Council report STARC-57517.
If lower-impact paths fail
Escalation
Use Character Repair only as a last resort
CIG says Character Repair may be needed for some infinite loading screens, but there are no current results for this party-or-bed-logout case. Older reports include success, failure, and the problem returning.
What to do
- Attempt the known workarounds first.
- Report the problem and reproduction steps through Issue Council.
- Open Account Dashboard > Settings > Character Repair and start the repair.
- Do not interact with the account and wait at least one hour before logging back in.
First check the system requirements, try the network checks once, use the friend-and-ship option if it applies, and file the Issue Council report. Character Repair cannot be stopped or reversed and locks game access while it runs. It may not clear the loading screen; items already missing stay lost and cannot be recovered by Support, and older players also reported missing Personal Hangars or hangar contents.
What's not worth trying
Do not treat a fixed wait as a repair
A fixed 15-minute wait is not supported as a recovery step. One older player with a named error regained access later, but nothing showed that waiting, rather than the shard recovering on its own, caused it.
Avoid ship-bed logout if this keeps recurring
CIG recommends avoiding the trigger when this error happens frequently. This is prevention, not recovery for an already-stuck character.
Related
Build status
CIG still lists Infinite Loading Screen in Alpha 4.10.x and has not published a hotfix that resolves it.
Known Issue Continues · LIVE
Boundaries and evidence
Use this page only when the loading screen does not end in a named login error and is not better explained by a broad service disruption, shard lock, or recent game-server crash. Those cases look similar but may need different steps.
Alpha 4.10.0 had been LIVE for roughly two days when this page was updated. No independent Alpha 4.10 result was available for any step.
Recent player reports mostly concerned named errors, shard locks, outages, or a different network-related loading problem, not this exact party-or-bed-logout trigger.
No usable report currently shows whether any step works for this exact incident, including reports on Spectrum, Issue Council, closed social communities, videos, and streams.
If the loading attempt ends in 64006 or 64010, use the separate 64006/64010 spawn-resolver incident instead.
Data sources
RSI Known Issues · RSI Support · RSI Status · Reddit