BustedLoops
Loops health
ISSUEkeycard printertimer displaycontested zonessecurity keycards

Keycard printer timer is stuck at 00:00

Tracked since 8 Sept 2026 · Last researched 8 Sept 2026

Problem

A maintenance or security keycard printer shows 00:00 and the timer does not move, so you cannot see how long printing or its cooldown has left.

RSI still lists this display problem for the current LIVE release. It does not say which Alpha 4.10.x hotfix is affected or how often the recovery works.

Applies to Alpha 4.10.x LIVE; base client build 4.10.0-LIVE.12519617; exact affected hotfix unresolved · Current

Best current action

Force quit with Alt+F4, then log back in

RSI says logging back in should restore the proper cooldown display. There is no independent Alpha 4.10.x test or success rate, so this is the best current step rather than a guaranteed fix.

This is RSI's current fix for the exact 00:00 timer display. One player reported the timer returning after the same relog in 2025, but that older result does not prove it works in the current build.

What to do

  1. Force quit Star Citizen with Alt+F4.
  2. Log back into Star Citizen.
Limited SupportLow riskRSI still gives this step for Alpha 4.10.x LIVE, without naming the affected hotfix or a success rate.

Other options

Fallback: wait out the hidden cooldown

One older player discussion says the cooldown kept running behind the frozen display and the printer could produce a card when it finished. No current Alpha 4.10.x result confirms this, and it will not repair the timer display.

Steps

  1. Stay in the session and wait for the printer's normal cooldown to finish.
  2. Try the printer again after the cooldown should have elapsed.
UnverifiedLow riskUnverified fallback based on one July 2025 discussion; the remaining cooldown and exact printer type were not established.

Boundaries and evidence

Use this page when the printer's timer itself is frozen at 00:00. A greyed-out print button, no interaction prompt, or a printer that still will not print after its cooldown is a different failure and may not respond to these steps.

No independent Alpha 4.10.x player test confirms that relogging restores the timer.

RSI does not identify the exact affected hotfix, the failure rate, or an incident-specific Issue Council history.

The only independent relog success and wait report came from one uncontrolled July 2025 discussion.

Data sources

RSI Known Issues · RSI Status · Reddit