Azure Virtual Desktop - Remote Desktop Web Client - Dead Keys and IME issues in private browser windows

Question

Azure Virtual Desktop - Remote Desktop Web Client - Dead Keys and IME issues in private browser windows

Nikita Kot 0

Hello,

I'm using AVD Remote Desktop Web Client to access AVD VMs on Chromebook device via the Kiosk mode. Chromebook Kiosk mode is running as a private browser window.

When I'm trying to use Chromebook keyboard layouts with dead keys (for ex. Czech QWERTZ layout) dead keys do not work, I'm not able to type ň letter for example (shift + "+" and then "n" results in ň).

When I'm trying to use a normal desktop browser window (non-private Chrome on Windows) the keyboard layout is correctly picked up from my host machine, so if I select Czech layout in my Windows host settings I can type in a AVD VM the same as I can type on my host machine - dead keys work as expected.

I tried disabling/enabling IME in the Web Client connection screen below, but it doesn't fix the problem in the private Chromebook Kiosk window:

when IME is enabled the host (Chromebook) layout is ignored and VM layout is used (so to use Czech QWERTZ with dead keys I have to configure this layout in the VM Windows settings)
when IME is disabled the host (Chromebook) layout is used, but I can't use dead keys, I get a warning notification (screenshot below)

enter image description here Eng:

In-session settings

Select the devices or features that your resource can use.

☑ Keyboard shortcuts (requires full screen)

Alternative keyboard layout — On

Use an Input Method Editor to enter complex characters. You must have an Input Method Editor enabled in your external session. Standard keyboard input may not work properly.

Dropdown: None

Hardware acceleration — On

enter image description here

Eng:

In Private browsing mode, the web client does not support the local Input Method Editor (IME). Turn off IME on your local computer or reconnect to the session in normal browsing mode.

Is there a way to use host keyboard layout Remote Desktop Web Client with dead keys support? I don't understand why Remote Desktop Web Client has that restriction in the private window. I need to use the host keyboard layout with dead keys while keeping the VM Windows layout settings default and ignored.

1 answer

Your answer

Answer 1

Chen Tran 8,220 Independent Advisor

Hello Nikita,

Thank you for posting question on Microsoft Windows Forum!

Based on the issue description as well as the provided screenshots. Well! The possible reason the Remote Desktop Web Client struggles in private mode is that the browser restricts access to certain Input Method Editor (IME) APIs and local storage to prevent "fingerprinting" (where websites identify you based on your unique settings). Since dead keys rely on the browser's ability to buffer a keystroke and wait for the next one, private mode often breaks that "wait and combine" logic to keep the session isolated.

The suggestion here for the potential workaround is to use the Alternative Keyboard Layout Setting. Instead of relying on the IME toggle, look for the Keyboard layout dropdown in the connection settings (before you hit "Connect"). Set it explicitly to Czech (QWERTZ) rather than "None" or "Auto." This tells the Web Client to use a specific mapping table that can sometimes bypass the browser's IME restrictions by manually stitching the dead keys together.

Another suggestion is to change the Keyboard settings in ChromeOS. If you are forced to use the Web Client, try changing the Chromebook's internal keyboard setting to Czech (QWERTZ) - Unicode. Sometimes, using a Unicode-based layout on the host forces the browser to send the finished character as a single input event rather than two separate keystrokes, which the VM will then accept regardless of dead key logic.

The plausible explanation to your query of Why you can't have "Default VM settings + Host Dead Keys" in Private Mode. In fact, Under the current architecture, if the browser is in private mode, it cannot "borrow" the host's dead key logic because the browser does not trust the host enough to share that buffer. You are essentially asking the browser to perform a "stateful" action (remembering the + key) in a "stateless" environment.

Hope the provided information is helpful! If it is. It is appreciated to consider clicking "Accept Answer". Should you have more questions, feel free to leave a message.

Nikita Kot 0 Reputation points

2026-02-16T14:27:42.9466667+00:00

On all other websites (for ex. https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_textarea) dead keys work correctly in the Chromebook Kiosk session. Only AVD Remote Desktop Web Client can't correctly handle the input and shows that "In Private browsing mode, the web client does not support..." notification. So the issue is specific to AVD Remote Desktop Web Client.
Chen Tran 8,220 Reputation points Independent Advisor

2026-02-16T20:46:33.92+00:00

Hi Nikita,

Thank you for the extra information!

The possible reason to explain why W3Schools works fine, but not for the AVD Remote Desktop Web Client might come down to how AVD handles keyboard input versus a simple text field.

Most websites just wait for the browser to send a "finished" character (the ň). However, to make a remote Windows session feel responsive, the AVD Web Client tries to capture raw scan codes (the physical location of the keys) to minimize lag. On the other hand, in Chrome Kiosk/Private mode, Google restricts access to the Keyboard.getLayoutMap() API to prevent "browser fingerprinting" (using your unique keyboard setup to track you). Because the AVD client can not "see" your physical layout map in private mode, it can not locally process the sequence of "Dead Key + Character." It defaults to a fail, safe mode that treats every keystroke as an isolated event, which is why your ˇ and n never merge.

The suggestion here is (as I mentioned previously) is to use the Alternative Keyboard Layout Dropdown. Instead of just toggling it "On", you must ensure the specific language is selected in the connection settings before you launch the session. Open the AVD Web Client and click the Gear icon (Settings) or look at the connection prompt. Ensure Alternative keyboard layout is toggled On. In the dropdown menu, explicitly select Czech (QWERTZ). This will force the Web Client to use a pre-defined mapping table stored on the server side, rather than trying to "ask" the Chromebook's browser what the layout is.

Otherwise, If you have control over the Kiosk app configuration, check if you can allow the Microsoft Remote Desktop extension. The dedicated extension has higher permissions than a standard browser tab and might bypass the Private Mode restrictions that block the Keyboard Map API.

Hope the above information is helpful! If it is. It is appreciated to consider clicking "Accept Answer".
Chen Tran 8,220 Reputation points Independent Advisor

2026-02-17T09:00:51.35+00:00

Hi Nikita,

Hope you are doing well!

May I know the latest status of the issue?

Hope the provided information is helpful! If it is. It is appreciated to consider clicking "Accept Answer". Should you have more questions, feel free to leave a message.
Nikita Kot 0 Reputation points

2026-02-17T09:34:42.93+00:00

The suggestion here is (as I mentioned previously) is to use the Alternative Keyboard Layout Dropdown

this doesn't work, the layout I select in this Alternative Keyboard Layout Dropdown is not respected, no matter what layout I choose in this dropdown, even if I select non-latin layout (for example Russian ЙЦУКЕН) and no matter what my Chromebook host layout is - it always seem to respect the layout of the Windows VM (ansi US in my image).

Microsoft Remote Desktop extension

what is it? can't find it
Chen Tran 8,220 Reputation points Independent Advisor

2026-02-17T10:54:08.0333333+00:00
Hi Nikita,

Based on your latest provided information. You can consider to try this workaround to see if it works this time around.

In the AVD Web Client Settings. Turn IME (Input Method Editor) OFF. Using IME in a private window is what triggers that error notification you saw. Then set Alternative Keyboard Layout to OFF. We want the browser to stop trying to interpret the keys. On the Windows VM (The Remote Session). Go to Settings > Time & Language > Language & Region. Add Czech (QWERTZ) to the Windows Guest OS. Ensure the language bar in the bottom right of the remote taskbar shows CES and on your Chromebook. Try to keep your host layout as Czech.

By turning off all the "helpers" in the Web Client, the browser simply sends the raw signal of the keys you press. If your physical fingers press the "dead key" combo and the Remote Windows OS is set to Czech, Windows will catch those raw signals and turn them into a ň itself.

Below article is for your further reference.

https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remote-desktop-web-client
Nikita Kot 0 Reputation points

2026-02-17T14:03:06.9766667+00:00

this also doesn't work, if i disable IME in AVD Web Client Settings I can't use dead keys

the only option to type dead keys which works is - enable IME in AVD Web Client Settings and then add Czech language on the host VM, but I don't want to change VM language settings, I want AVD Web Client to respect my host machine layout with dead keys support

Share via

Azure Virtual Desktop - Remote Desktop Web Client - Dead Keys and IME issues in private browser windows

1 answer

Your answer