Well, actually, it seems Enter key works after pressing it a number of times (3-5). CPU usage of and idle SERP client is almost 10%.
Customer is behind firewall and proxy. Could it be that the client tries to connect somewhere and fails? There is nothing interesting regarding this in the log.

It could be that Cisco firewall at the customer site is somehow blocking this even though 8.5 2021-11-02 (build 85420021) had no problems.
They have a web proxy too.
I have tested with 2022-09-20 version and it worked for a few minutes and then stopped responding to key presses (Enter, Ctrl+Enter)
CPU usage for idle SERP client is up to 10%, while on my test installation with the same build is 0,5% or so.

Maybe there is a secret enabler to disable Microsoft Edge WebView2 feature as this is the problem I guess. One PC out of 6 started working normally, nobody knows why, other 5 users cannot work and enter data because of not working Enter, Tab, Ctrl+N,Ctrl+Enter keys as described above.

A problem that repeats on a computer only, it's likely to be an issue strictly connected to that single machine.
Without further details, the best guess that I can have, it's an issue related with the mapping/layout used by the keyboard.
We had lately some issues on Windows only, connected to the arrow keys to move between fields, but the problem described by you seems to be totally unrelated.

I have reported a bug: General>>Esc, TAB, Enter,F2 do not work in Windows
If we are in the restricted enterprise environment (proxy, firewall, VPN) then in versions 2022-09-20 and 2022-11-22 (the ones using Microsoft Edge WebView2) there is


1. A high CPU usage of the Windows client (up to 10%) instead of 0,5% where we have no proxy.
2. Esc, TAB, Enter,Ctrl+Enter, F2 keys do not work and application is very slow, it is impossible to enter data in any
register because paste special, enter, Tab keys do not work.


Extra notes:
Proxy issues with WebView2: https://github.com/MicrosoftEdge/WebView2Feedback/issues/132

It would be very nice to have some enabler file or something to disable WebView2 completely to solve these problems if there is no better solution.

We will check it, though, in the bug report you say there is a problem with Windows updates from December. We have updated the version in 2022-11-18...

Happy to hear that :)