Gosh, the mentioned issue must be resolved immediately! Something like that should never happened in the first place, and the Windows app developers should get a feedback that they have made a trivial mistake – utilizing a keyboard shortcut that is already taken by the operating system for localization purposes. Seriously, guys, it’s a 101 kind of embarrassing mistake and no serious software company can make it and keep their image intact. C’mon guys… Shame on you, really. Besides, what has been indicated as a "solution" in this thread is not a solution, but a workaround. PS: I'm also canceling my subscription until this problem is going to be taken seriously. User Zbigniew is right that there must be consequences.