Why Your Keyboard Types Wrong Characters in Citrix or Excel (And How to Fix It)

Published on 2026-11-08 ยท 7 min read ยท By MiniTestLab Engineering Team ยท Category: Keyboards

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Keyboard Tester

Your keyboard hardware is fine; the problem is a layout mismatch between your local Windows session and the remote Citrix session, or a locale override inside Excel's formula engine. When a Citrix Virtual Apps session initializes, it inherits the keyboard layout from the Citrix Workspace client configuration, not necessarily from your physical machine's active input locale, which means the scan codes your membrane or mechanical switches send get remapped by a second layout table the moment they cross the virtual channel. In Excel specifically, a third layer exists: regional settings control which character the formula parser treats as a list separator versus a decimal separator, so a US keyboard on a European-locale server will produce semicolons where you expect commas and periods where you expect nothing at all.

Why This Happens: Scan Codes, Virtual Channels, and Layout Tables

Every key on your keyboard, whether it sits on a Logitech G Pro X with Kailh Box White switches or a $12 rubber-dome office board, sends a hardware scan code to the OS. Windows translates that scan code through the active keyboard layout DLL, for example KBDUS.DLL for US English or KBDGR.DLL for German, to produce a character. That translation happens locally before anything reaches Citrix.

Citrix Workspace then forwards keystrokes over the ICA/HDX virtual channel. On the server side, the VDA (Virtual Delivery Agent) applies its own active keyboard layout to the incoming data. If the server's layout is set to French AZERTY and your local layout is US QWERTY, the letter A on your keycap sends scan code 0x1E, which the server maps to Q. That is the entire mechanism behind citrix keyboard typing wrong characters reports.

Before you touch any Citrix setting, confirm the keyboard itself is not the culprit. Open Keyboard Test in a plain browser tab outside of any remote session and press every key. If characters are wrong there too, you have a hardware or local-OS problem, not a Citrix problem. If every key registers correctly in that tool, proceed below.

Fixing the Layout Mismatch in Citrix Workspace

Citrix Workspace 2209 and later expose keyboard layout sync settings directly in the client. The path depends on your deployment:

  1. Open Citrix Workspace. Click your account avatar, then Advanced Preferences, then Keyboard and Language Bar.
  2. Set Keyboard layout to Sync with client. This tells the VDA to adopt whatever layout your local Windows session is using rather than defaulting to the server's configured locale.
  3. If Sync with client is greyed out, your Citrix administrator has locked it via Citrix Policy. You need them to enable the Client keyboard layout synchronization and IME improvement policy in Citrix Studio or Web Studio, setting it to Support dynamic client keyboard layout synchronization and IME improvement.
  4. After changing the setting, fully disconnect and reconnect the session. A simple screen refresh does not re-initialize the virtual keyboard channel.

For StoreFront-based deployments without the Workspace client, the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Virtual Channels\Keyboard contains a KeyboardLayout value. Setting it to (User Profile) forces client-side sync.

Fixing Wrong Characters in Excel Specifically

Excel keyboard typing wrong characters is a separate problem even when Citrix is involved. Excel's formula parser reads the system list separator and decimal symbol from Windows Region settings, not from the keyboard layout. A server configured for German locale uses a comma as the decimal separator and a semicolon as the list separator. Your US muscle memory types a comma to separate function arguments, but Excel on that server expects a semicolon, so it throws an error or silently produces wrong output.

To check and correct this on the remote server (requires local admin or a call to your admin):

  1. Open Control Panel, then Region, then Additional settings.
  2. Note the values for Decimal symbol and List separator. For a US-style experience, these should be . and , respectively.
  3. Change them to match your expectation and click OK. Excel reads these values at launch, so close and reopen Excel after changing them.

You can also override this inside Excel without touching Windows settings: go to File > Options > Advanced, uncheck Use system separators, and manually set Decimal separator to . and Thousands separator to ,. This is a per-user, per-machine setting stored in HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel\Options under DecimalSeparator and ThousandsSeparator.

Comparison: Common Wrong-Character Scenarios and Their Fixes

Symptom Root Cause Fix Location
Q types as A, W types as Z across all apps Server layout is AZERTY, client is QWERTY Citrix Workspace keyboard sync setting
@ and " are swapped Server is UK English layout, client is US English Citrix Workspace keyboard sync or server layout change
Comma in Excel formula causes error Server region uses semicolon as list separator Windows Region settings or Excel Advanced options on server
Period types as comma in numbers Server decimal separator is a comma (European locale) Windows Region additional settings on server
Numbers row types symbols instead of numbers Num Lock state differs between client and server Press Num Lock; check Citrix policy for Num Lock sync
Wrong characters only in one web app inside Citrix Browser inside session has its own locale override Browser language settings within the remote session

Num Lock, Dead Keys, and Other Edge Cases

If only your number row or numpad is producing wrong output, the Num Lock state on the server may not match your physical keyboard. Citrix does not always synchronize Num Lock state on session reconnect. Press Num Lock once inside the session and test again. If this keeps resetting, ask your admin to enable the Initial Num Lock state policy in Citrix Studio.

Dead key sequences are another trap. On a German or French layout, certain keys are dead keys that wait for a second keystroke to compose a character (for example, the caret accent). If your server layout has dead keys and your local layout does not, you will see delayed or missing characters when typing sequences like ^a. The only reliable fix is full layout synchronization as described above.

If you are troubleshooting a physical keyboard that is behaving oddly even outside remote sessions, use the Keyboard Test tool to isolate which specific keys are misbehaving, then cross-reference with the Mac Keyboard Test if you are on macOS connecting to a Citrix session, since macOS-to-Windows scan code translation adds yet another remapping layer.

Frequently Asked Questions

Why does my keyboard type wrong characters in Citrix Workspace but work fine everywhere else?

The Citrix VDA on the server is applying a different keyboard layout than your local machine. The ICA virtual channel forwards your keystrokes, but the server remaps them through its own active layout. Enable keyboard layout synchronization in Citrix Workspace under Advanced Preferences so the server adopts your local layout instead.

My admin says keyboard sync is already enabled but Citrix is still typing wrong characters. What next?

Check that the VDA version on the server is 2109 or later. Older VDAs do not fully support dynamic layout sync. Also confirm the Citrix policy Client keyboard layout synchronization and IME improvement is set to the dynamic option, not just the basic enabled state. Finally, verify that your local Windows input language is set correctly in Settings, then Time and Language, then Language and Region, then the typing language listed under the taskbar.

Why does Excel type wrong characters even when I am not using Citrix?

Excel's separator characters come from Windows Region settings, not the keyboard layout. If your Windows region is set to a European locale, Excel uses a comma as the decimal separator and a semicolon as the list separator regardless of what keyboard you have. Fix this in Control Panel under Region, Additional settings, or override it inside Excel at File, Options, Advanced, by unchecking Use system separators.

How do I test whether the problem is my keyboard hardware or a software layout issue?

Run the Keyboard Test in a regular browser tab with no remote session active. Press each key and confirm the output matches the keycap label. If characters are correct there, the keyboard hardware is fine and the problem is entirely in the remote session's layout configuration. If characters are wrong in that tool too, you have a local OS layout or hardware issue to resolve first.

The @ symbol and the double-quote key are swapped. Why?

This is the most common symptom of a US versus UK English layout conflict. On a US layout, Shift+2 produces @. On a UK layout, Shift+2 produces double-quote and @ sits on Shift+'. The server is running UK English while your keyboard and local layout are US English. Enabling Citrix keyboard sync resolves this immediately.

Can a firmware issue on my keyboard cause wrong characters in Citrix?

Rarely, but it is possible. Some gaming keyboards with onboard memory store a hardware remapping profile that activates regardless of the OS layout. If your keyboard has companion software like Logitech G HUB or Razer Synapse, open it and check that no key remapping is active in the current profile. A keyboard with no companion software sending wrong scan codes would show up as wrong characters in the Keyboard Test tool outside of any remote session, which is the quickest way to rule this out.

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Keyboard Tester