New key logger protection issues in W8...

I'm afraid I've been unable to reproduce this, even on a Windows 8 system specifically.  It's likely going to require a remote session with Support to get to the bottom of this, and logs would be helpful.  Could you please open a support case?

@ wrote:
Remote session? Sounds scary! :P
 
Yeah I probably have to open support case if others do not have that. Weird that it does it only with certain characters. It's going to be a bit busy week so it may slip to next week.

Haha, well you're in good hands.  It just means Support logs on to your computer remotely and does more of the troubleshooting for you.  I'm sure the Community will be interested in hearing what happens.  Please let us know!

Indeed, it looks like development is aware of this issue with international keyboard character entry.
 
For anyone who hasn't clicked the link, our V.P. of Development, , chimed in on that linked thread saying:

@ wrote:
I suspect this is indeed a WSA issue. It's difficult to test each type of keyboard especially international ones as well with the keyboard monitoring we have in place. We're going to be investigating this closer and will hopefully have a resolution soon, but we need to be able to solve it without reducing keylogger protection, which is a bit complicated.

Please let me know if any other keystroke combinations don't work correctly or if you're experiencing any other problems as this will help narrow down the issue.

Thanks!

We can track that additional data here as well if anyone has any new information to add to the investigation.

This looks very similar to another reported issue on a Dutch OS. These issues have been documented and provided to development. We'll update again once a solution is available.

For the Dutch customer, installing the English version of WSA resolved his similar issue. That may not always be an option for non-English speakers, so we'll certainly continue working on a solution.