Hello Kuile, Ernest ter (ITDS EZ) - KLM,
The issue you are encountering stems from the architectural shift in Windows 11, which now defaults to hosting command-line shells inside the modern Windows Terminal application (wt.exe) rather than the legacy Windows Console Host (conhost.exe). The "Properties" dialog and "QuickEdit Mode" settings you are searching for belong exclusively to the legacy console infrastructure and do not exist within the Windows Terminal interface, which utilizes a different rendering engine and JSON-based configuration profiles. Furthermore, the disparity you notice between PowerShell and Command Prompt (cmd.exe) is technical, not accidental: PowerShell utilizes the PSReadline module to handle input, which enables modern text editor capabilities like Shift+Arrow highlighting. Native cmd.exe relies on archaic standard input processing and does not support inline text highlighting or selection with the keyboard in its raw state.
To perform keyboard-based text selection within a cmd.exe tab in Windows Terminal, you must explicitly invoke the Mark Mode feature, which replaces the mouse-based "QuickEdit" functionality. You can activate this by pressing Ctrl + Shift + M. Once Mark Mode is engaged, you will notice selection handles or a cursor change; use the Arrow keys to navigate to the starting position of the text you wish to capture, then hold Shift and use the Arrow keys to highlight the desired block. Pressing Enter or Ctrl + C will copy the selection to the clipboard and exit the mode. This is the standard, native method for keyboard selection in the Windows 11 Terminal environment.
If you specifically recall being able to highlight text on the input line while typing (identical to how Notepad or PowerShell behaves) without entering a special mode, it is highly probable that your previous environment utilized a third-party readline injector such as Clink. Native cmd.exe has never possessed this capability on its own. Installing a utility like Clink injects the GNU Readline library into the cmd process, which effectively forces the Command Prompt to accept standard editing shortcuts, including Shift+Arrow selection, thereby replicating the behavior you see in PowerShell.
I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!
VP