ASOP Retrieve button is greyed out and unavailable
Tracked since 10 Sept 2026 · Last researched 10 Sept 2026
Problem
Your stored ship appears in ASOP, but Retrieve is greyed out and cannot be selected, so the retrieval request never starts.
This still occurs in Alpha 4.10.0 LIVE. A pre-release patch note listed a potential fix, but current player reports show the grey Retrieve state still occurring in LIVE.
Applies to Alpha 4.10.0 LIVE, including rolling 4.10 hotfixes through 2026-09-10 · Current
Best current action
Exit to the main menu and load back in
Relog first. Multiple current Alpha 4.10 reports describe it restoring Retrieve, but other players report failures and frequent recurrence, so treat it as the best current first step rather than a guaranteed or lasting fix.
This is the lowest-impact option with successful reports from more than one current Alpha 4.10 player.
What to do
- Exit to the main menu.
- Load back into the Persistent Universe and check Retrieve again.
Relogging ends your current session. It can fail, may return you to the same shard, and sometimes needs to be repeated after the problem returns.
Another option
If Retrieve is grey at the personal-hangar ASOP and a public lobby ASOP is reachable at the same location
Try the public lobby ASOP
A current Alpha 4.10 player bypassed a grey personal-hangar terminal this way, while another player in the same discussion did not.
What to do
- If Retrieve is grey in the personal hangar, return to the lobby or terminal area.
- Open a public ASOP terminal and try Retrieve once.
Use this only for a terminal-scoped failure; current results are mixed.
If another player at the same location can provide access to their hangar elevator
Use another player's hangar elevator
Current and earlier players report that leaving the lobby through another player's hangar and returning can restore Retrieve, although the problem may return.
What to do
- Join a party with another player at the same location or ask to use their elevator.
- Ride the elevator to that player's hangar.
- Return to the lobby after repositioning and try an ASOP terminal again.
Another player at the same location must give you access to their hangar elevator. This may only restore access temporarily.
If a local medical regeneration point is available, valuable carried items are stored, and the lower-impact recovery options did not restore Retrieve
Last resort: respawn at the local medical facility
One current Alpha 4.10 player reports that a local medical respawn restored Retrieve. Use it only after the lower-impact options because forcing a respawn can put carried items at risk.
What to do
- Store carried items you do not want to risk losing.
- Set the medical facility at the current location as the regeneration point.
- Use Backspace to trigger a respawn there, then return to ASOP.
The current location must have a medical facility that you can set as your regeneration point. Store valuable carried items before continuing. Forcing a respawn can leave carried items behind at your previous location. Recovering them may require returning before another player takes them, and some items may not be recoverable.
Diagnostic checks
These checks can identify the affected state, but they are not fixes.
Report the exact state to Issue Council
CIG asks players to provide detailed reproductions for persistent ship-access problems. A precise report can help the investigation but will not restore Retrieve immediately.
What to check
- Search Issue Council for the grey ASOP Retrieve-control incident.
- Contribute to the closest matching current report with the LIVE build, location, ship state, trigger and every attempted workaround.
- Create a new report only if no current matching report exists.
Preparing a useful report takes time and is not an immediate recovery step.
Other options
Fallback: change shard or region
One current Alpha 4.10 player recovered after changing region, but an earlier player reported that server hopping did not work.
Steps
- Exit to the main menu.
- Select another region or join a friend on another shard.
- Load into the Persistent Universe and check Retrieve.
Changing shard ends the current session and can separate you from your party or activity. The result is uncertain.
Fallback: get a ride to another location
If another player or transport can take you to a different station or landing zone
RSI recommends trying another location for persistent ship-retrieval problems, but no exact Alpha 4.10 execution confirms this route for a disabled Retrieve control.
Steps
- Get a ride from another player to a different station or landing zone.
- Use an ASOP terminal there to retrieve a ship.
You need another player or transport that can reach a different location. The trip leaves your current location and costs travel time without a guaranteed recovery.
Related
Build status
A matching Alpha 4.10 PTU note listed a potential fix, but independent reports show the grey Retrieve state still occurring in Alpha 4.10.0 LIVE.
Alpha 4.10.0 · Known Issue Continues · LIVE
Boundaries and evidence
Use this page only when the ship is listed and Retrieve is disabled before you can make a request. It does not cover a missing Deliver option, the message 'Failed to retrieve vehicle,' a ship missing from the list, or a ship that spawns but is stuck or absent from the hangar.
The matching Issue Council report body, contribution history, official triage, and current resolution state could not be inspected.
Every success or failure result here is an uncontrolled player self-report. No route was independently tested, and no success rate is available.
Player reports usually identify Alpha 4.10 rather than the exact hotfix or shard build. Relogging can fail or restore access only temporarily.
If Deliver itself is missing, use the separate missing Deliver option workaround.
If the terminal accepts the request and then says 'Failed to retrieve vehicle,' use the separate retrieval-failure workaround.
Data sources
RSI Support · RSI Status · Reddit · Specialist Community