AltGr+2 will not work whilst being locked down - Win10 MultiApp Edition

Hello,

I am having an issue I have not seen before.

In unlocked condition, I use AltGr+2 to get the @ sign,
but this simply does not work with 2.0.172 (also tried 2.0.173)
of the MultiApp edition on Windows 10.

When attempting AltGr+2 there comes an audible alert, but no input.
(In unlocked mode it works as expected)

Does the MultiApp edition somehow intercept the AltGr+2 combination?

Try holding down the Altgr button a few seconds before pressing the 2.

Inteset S. wrote:

We tried this, but it didn't work.

Now we have a second recent installation that has this particular issue.

(Swedish keyboard layout, in both cases Altgr+2 works in unlocked mode, but not when locked with MultiApp edition...)

Try using the regular Alt button in combination with the number 64 (Alt+64). That's the Alt code for the @ symbol.

Inteset S. wrote:

Verified NOT to work on this system when SecureLockdown is running.

Hermann R. wrote:

Is there a way to get more info for you regarding this?   (debug-logs etc...)
Starting to be a pain-point.  :-(

If the problem could be reproduced, we could troubleshoot it but the AltGr key is working with the wireless keyboards we have. Have you tried a different keyboard? Is it possible to use another key combination to accomplish your need?

Inteset S. wrote:

I have tried with an external USB keyboard with the same result.  (neither AltGR-2 or Alt-64 work)

I will attempt to see if a input locale change will make any difference.

This is weird,  but whereas in a open configuration AltGR+2 works fine, I have to combine it with the right Ctrl-button to make it work in a locked down configuration.

So when locked down, AltGR+(right)Ctrl+2 renders a @, whereas AltGR+2 does nothing.

And this is on two laptops with different brands and different keyboards, but both of them with
Win10 and SecureLockdown MultiApp.

Any idea why it would require that right ctrl-button also to actually make AltGR work as intended?

(Setting input-locale to US English had no effect.)

We'll look into this. Thanks for the investigation and feedback.