Pressing FN key puts @ symbol in pwsh console

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

When I press the Fn (Function) button on the MSI Raider GE76 gamer laptop in Powershell 7.3.4 the key returns an “@” symbol in text output. The Fn Key is used for miscellaneous functions such as, use of the Home,End, Sys Rq keys as well volume up, down and mute; screen brightness up and down; Airplain mode, and all secondary functions on the F-keys.

It’s most annoying due to when I want to press the home or end keys a string of “@” symbols appears till I let go of the Function key. I can press and hold the Function key in Notepad and it acts as expected.

The problem does not occur in the Terminal App that can be downloaded from the Windows Store.

Expected behavior

No output when the key is pressed at all.

Actual behavior

PS> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Error details

no errors

Environment data

Name                           Value
----                           -----
PSVersion                      7.3.4
PSEdition                      Core
GitCommitId                    7.3.4
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visuals

[kilasuit]

I can also repro this on My Lenovo Yoga S730 ( quite an old machine now) so isn’t just due to local machine configuration.

@whitequill please can you change the issue title to Pressing FN key puts @ symbol in pwsh console as that’s more fitting

[microsoft-github-policy-service[bot]]

This issue is closed because it has been marked as requiring repro steps but has not had any activity for 7 days. If you think the issue is still relevant, please reopen and provide your feedback.