---
title: "No Response from Badge Tap on Thin Client Connected to VDI"
slug: "no-response-from-badge-tap-on-thin-client-connected-to-vdi"
description: "When tapping a badge on a thin client connected to XA running on a VDI, the badge reader beeps but credentials aren't submitted. This is a Troubleshooting article that addresses this issue."
updated: 2022-06-01T19:37:19Z
published: 2022-06-01T19:37:19Z
canonical: "healthcare.rapididentity.com/no-response-from-badge-tap-on-thin-client-connected-to-vdi"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://healthcare.rapididentity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# No Response from Badge Tap on Thin Client Connected to VDI

## No Response from Badge Tap on Thin Client Connected to VDI

When tapping a badge on a thin client connected to XA running on a VDI, the badge reader beeps but credentials aren't submitted.

### PROBLEM

Intermittently a badge tap appears to fail when tapping a badge on a thin client connected to XA running on a VDI.

1. XA Lock screen is visible
2. User taps badge
3. Badge reader beeps
4. For a registered user:
  1. User's credentials are not entered into login prompt
5. For an unregistered user:
  1. User is not prompted to enter credentials

#### OTHER BEHAVIOR:

1. The user can login manually (not using badge)
2. The user can keep trying to login with a badge, and it will work intermittently

### AFFECTS:

All versions of XA 4.11 and 4.12 client.

### ROOT CAUSE: The Hardware poll Interval set too low

On the VDI, the HardwarePollInterval setting is set too low. This does not allow enough time for a response back from badge reader on the thin client.

HKEY_LOCAL_MACHINE\SOFTWARE\HealthCast\ProxCardClient HardwarePollInterval = 500

### RESOLUTION

Try adjusting the HardwarePollInterval registry value on the VDUI until the badge tap is recognized consistently. First adjust it upwards (700, , 800, etc. but no higher than 1200). The increase in time will help prevent the software from making a request to the badge reader before the current request returns.

After changing the value, restart the HCI ProxCard Client Service on the workstation so that it picks up the new HardwarePollInterval value.

## Related

- [Badges Not Registered When Pointing to XA 4.11.x Server](/badges-not-registered-when-pointing-to-xa-411x-server.md)
- [Badge Tap Fails After Installing or Upgrading XA Client](/badge-tap-fails-after-installing-or-upgrading-xa-client.md)
- [Ignore New Badge - Currently Processing an Existing Badge Tap](/ignore-new-badge-currently-processing-an-existing-badge-tap.md)