Windows 10: keyboard mapping problem with windows terminal preview

I have been running Windows Terminal Preview for a while now and it works fairly well.


However I have noticed a keyboard mapping problem when I try to use less.exe from a cmd.exe session. When I do something like "less -MN *.txt" the first files comes up nicely. However when I try to use the "less" command ":n" to go to the next file it does not work. Instead of going to the next file I get an error message stating "no previous regular expression". This does not occur when I ran cmd.exe the old fashioned way. I looked at the profiles.json file and nothing in there provided any clues.


Any ideas as to why I am having this keyboard mapping issue ?


Thanks.

:)

 

Keyboard problem in Windows 10

Hi David,

Thank you for posting your query in Microsoft Community.

I suggest you to check if the issue persists when you connect another keyboard to your system.

If the issue is with the keyboard, then suggest you to update the keyboard drivers by following the steps below.

• 
  Press Windows key + X and select
  Device Manager from the list.
  
• 
  Expand ‘Keyboard’ from the list.
  
• 
  Right click on the driver and select ‘update driver software’ and follow the prompts.
  

Hope the information is helpful.

 

I"m having a problem with the keyboard in Windows 10

Hi Robert,

I realize that you are facing issues with the keyboard. I will try to help you with this issue.

• 
  Did you make any changes to the PC prior to this issue?
  

Suggest you to plug in an external keyboard to the laptop to check if that helps.

Further you may also use the onscreen keyboard to check if that helps.

Follow these steps to launch the On-screen keyboard:

• 
  Press Windows key + R to get the run window.
  
• 
  Type “osk” and hit enter to launch the On-screen keyboard and check if this helps.
  

Keep us informed to help you further.

Thank you.

 

Keyboard letters problem

Here are the first two steps you need to take:

• Try a different keyboard (or an external USB keyboard in case of a laptop)
• See if the problem persists with the on-screen keyboard (osk.exe)