Skip to main content

One post tagged with "ciV-75"

View All Tags
MissedRemote accessUX / messaging

Radar / Saracen AR: pre-installed Windows RDC no longer prevents app access (retest contradicts April 19); block fires without UX guidance

RadarBetSaracen
radarsaracen-arrdpwindows-10windows-11

Source. May 26, 2026 weekly sync.
Ticket. CIV-75: Saracen AR — Radar Verify app retest, full competitor validation.

What we tested​

Retest, since May 19, 2026, of how Radar behaves on Bet Saracen Arkansas when the Remote Desktop Connection (RDC) client is merely present on the Windows host — i.e. installed but not actively driving a remote session.

Setup:

  • Windows 10, with RDC pre-installed, later upgraded in-place to Windows 11.
  • No active remote-desktop session at the time of testing.

What happened​

  • ✗ Presence of RDC is no longer enough to block the app. This contradicts the April 19 finding, which had previously recorded pre-installed RDC as sufficient grounds for Radar to refuse access.
  • ✗ The system does block access whenever the app is launched, even with no remote session running in the background.
  • ✗ Block fires with no explanatory error. Users see no recovery guidance — they cannot wager and they cannot tell why.

Why it matters​

Two distinct issues stacked on one another:

  1. Detection regression. The April 19 baseline (presence of RDC blocks the app) no longer holds — a measurable loosening of Radar's posture between cycles. Worth confirming whether this is intentional or a regression.
  2. UX-as-compliance failure. Even when the block fires, it does so silently. A legitimate user with RDC installed on their PC (a common configuration in any IT-managed environment) is permanently locked out with no signal as to what is wrong. This is significant UX friction and a customer-support amplifier.

Cross-reference​

Radar profile → · May 26 weekly sync →