Cannot use uppercase if PowerShell is open in Russian keyboard layout

[kvart714]

Steps to reproduce

1. Switch keyboard layout (I use Russian)
2. open Powershell
3. Switch the layout to English
4. Press shift and enter text

Expected behavior

You can enter "UPPERCASE"

Actual behavior

You cannot enter "UPPERCASE", only "lowercase" without shift

Environment data

Windows 10 Pro 1809
Powershell 5.1.17763.771

[iSazonov]

@kvart714 Thanks for your report!

It is a known issue with PSReadline module. As workaround you could unload the module. Also the issue was fixed in latest PSReadline preview version (2.0 Beta.5) and you can install it.

[ghost]

This issue has been marked as answered and has not had any activity for 1 day. It has been closed for housekeeping purposes.

[Suncatcher]

@iSazonov

Also the issue was fixed in latest PSReadline preview version (2.0 Beta.5) and you can install it.

so maybe it is worth moving from preview to the main version? It is already mid-2021 and it is still in preview.
Preview is for testing new and experimental features, and this is a fundamental bug.

[Suncatcher]

@iSazonov by the way even on Preview it is not fully fixed. Only SOME of the letter are typable, the others are not working

[Suncatcher]

And this problem with typing capital letters exists also on classic PS console, not only in new Terminal. Is there a special bug created for console?

[iSazonov]

Is there a special bug created for console?

If you still say about PSReadline there is an issue about the bug in PSReadline repository.

[Suncatcher]

Installed latest 2.2.0 prerelease of PSReadline and the issue seems to be solved. Thanks.

[Suncatcher]

@iSazonov and what is the status of that bug? I cannot find it in PSReadline repo?

[iSazonov]

@Suncatcher It is not clear what you ask if the issue already fixed in preview and stable version.

[OZ1]

@iSazonov Either it does not or my PS is outdated. How can I look up the version of the faulty module? In what version it is fixed?

[iSazonov]

@OZ1 You can find current versions in https://github.com/PowerShell/PSReadLine. Latest preview one is Beta4, stable 2.1.
Use follow command to discover PSRL version installed:

Get-Module PSReadLine | fl

GitHub

GitHub - PowerShell/PSReadLine: A bash inspired readline implementation for PowerShell

A bash inspired readline implementation for PowerShell - GitHub - PowerShell/PSReadLine: A bash inspired readline implementation for PowerShell

[Suncatcher]

It is not clear what you ask if the issue already fixed in preview and stable version.

@iSazonov I have Powershell like below

Major Minor Build Revision
------ ----- ----- --------
5 1 19041 1320

and PSReadLine of version 2.0.0

Name : PSReadline
Path : C:\Program Files\WindowsPowerShell\Modules\PSReadline\2.0.0\PSReadLine.psm1
Description : Great command line editing in the PowerShell console host
ModuleType : Script
Version : 2.0.0
NestedModules : {Microsoft.PowerShell.PSReadLine}
ExportedFunctions : PSConsoleHostReadLine
ExportedCmdlets : {Get-PSReadLineKeyHandler, Get-PSReadLineOption, Remove-PSReadLineKeyHandler,
Set-PSReadLineKeyHandler...}
ExportedVariables :
ExportedAliases :

is it considered stable? I received all dotNet framework updates via Windows update.

[iSazonov]

Latest stable version of PSRL is 2.1.0. I think you should update PSRL manually.

[Suncatcher]

ok, thanks for clarification. And why the latest stable version is not proposed by the automatic update? Is there any policy to adjust to make that happen?

[iSazonov]

You can ask MSFT team on next Community Call (Nov, 18) :-)

[Suncatcher]

ok, I installed latest stable Powershell 7.2.0 and I figured out it loads into PS session several different versions of PSReadLine from different locations

which will have the highest priority in that case, i.e. which one will be used by the current PS session?

[iSazonov]

You are searching available modules. Get-Module show you loaded modules.

[Suncatcher]

thanks

[ognyandim]

One workaround is to turn-off the per-app keyboard selection:

"Start menu" -> Settings -> Find "Typing settings" -> Advanced keyboard settings -> check checkbox "Let me use a different input method for each app window" - Uncheck it.

Found here: https://superuser.com/a/1262197

Super User

Per app input language Windows 10

I've set up so that Windows remembers my input language preference for each app, it works really well (US-English as default with Swedish for some apps) until I close the apps/restart the OS, then it