Based upon this context menu, I would think CTRL+F would bring up the find dialog but it doesn't. Why not? How do I bring up the find dialog from the keyboard?

I do see the shortcut has a '-' not a '+' in the label. I'm not sure if that means something or not.

right click options

  • Worth pointing out none of the keyboard shortcuts work I am going to guess they are not suppose to. With the current version of Powershell on Windows 7 the keyboard shortcuts are not offered.
    – Ramhound
    Commented Oct 17, 2017 at 21:16
  • Not even CTRL-V? I thought that one still worked. Commented Oct 17, 2017 at 21:25

3 Answers 3


The menu should be updated to remove the shortcuts listed for Mark and Find. They don't work as expected. Paste and Select All work with the respective keyboard shortcuts listed.

You can access Find via the keyboard with Alt+Space+E followed by F.

  • 6
    Or they should make the shortcuts work again :) I've submitted a Feedback Hub Request. Commented Oct 19, 2017 at 18:45
  • Correct link to Feedback Hub Request, my bad. Wonder where the correct GitHub repo is to file it there? 🤔 Commented Jul 18, 2019 at 18:23
  • Still not fixed. Thanks ob... Microsoft.
    – Unknow0059
    Commented May 14 at 4:05

In Powershell / Windows 11, the solution proposed by @Omkar Neogi in the comments, worked for me:


  • Doesn't work on Windows 10.
    – Unknow0059
    Commented May 14 at 4:06

PM for Windows Console here.

This is a known limitation of how PowerShell and Console interact. Console supports several input modes including Processed and VT input.

In Processed mode, Console traps some reserved key chords to perform local actions like Break (CTRL+C), Find CTRL+F, Command History (F7) etc.

In VT mode, Console converts all keys/chords into VT Sequences and passes them straight through to the connected shell/app.

PowerShell sets Console in VT mode in order to maintain a higher degree of compatibility with *NIX-like tools, etc. Alas, this means that when using PowerShell, Find won't work in Console.

Console's primary responsibility is to maintain backward compatibility, which results in us rarely making any UX changes to Console lest we break something/someone.

However, we're actively building the new Windows Terminal which provides FAR more powerful, flexible, and configurable command-line user experience. In Windows Terminal, if you declare a key mapping in your settings, your key mappings take precedence and allow you to override default behaviors.

If you're running Windows 10 1903 or later, then we STRONGLY encourage you to evaluate and migrate to using Windows Terminal wherever possible.

  • 5
    do ctrl shift f in windows terminal. Commented Feb 9, 2021 at 17:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .