View Single Post
Old 05-26-2021, 03:05 PM
jdev's Avatar
jdev jdev is offline
VanDyke Technical Support
Join Date: Nov 2003
Location: Albuquerque, NM
Posts: 1,099
Local Shell access on Windows is available in SecureCRT 8.7 and newer

Originally Posted by Ketan View Post
My company switched from mac to windows. In Mac and SCRT v7.2.6, CTLR-L got me the local shell session. Is there similar functionality in the Windows SCRT version?
While your organization doing such switching, it may be time to switch to a newer version of SecureCRT since version 7.3.7 hasn't been in active development since Mar, 2016.

While "Local Shell" functionality has been around in SecureCRT for macOS/Linux platforms for some time, it wasn't added to SecureCRT for Windows until version 8.7, and you have to be using a version of the Windows OS which includes a specific console API designed to facilitate such connectivity.

Changes in SecureCRT 8.7 (Beta 1) -- November 20, 2019

New features:
  - Windows: Added support for opening a local shell (CMD or
    PowerShell) session within SecureCRT.  Due to
    Microsoft's Pseudo Console API availability, support for
    this feature is limited to Windows 10 build 1809 and
    Windows Server 2019 or later.
Once you're running a version of SecureCRT 8.7 or newer on Windows 10 build 1809 or newer (or Server 2019 or newer), the the Alt+Shift+L keyboard combination can be used to open a local shell -- or, if you're OK with long-distance mouse travel you can open the File menu and choose Connect Local Shell.
  • By default, the "Local Shell" can be CMD or PowerShell.
  • If you have WSL installed and enabled, you can even use bash as your local shell in SecureCRT for Windows. For example:
SecureCRT will remember the last "Local Shell" you chose when using the Quick Connect, so if you want to change your "Local Shell" shell, open the Quick Connect (Alt+Q), set the protocol to "Local Shell", specify the path to the console application you want to run, and press the [Connect] button (no need to have the Save session option enabled -- in fact, you probably don't want to have it enabled unless you want to create a saved session for that specific local shell and recall it directly from within the Session Manager).
Once you've used Quick Connect to specify a Local Shell, subsequent Alt+Shift+L instantiations will repeat that last local shell launched from inside the Quick Connect window.
You also expressed...
All I want to do is access my desktop so from there I can connect to another network for file transfer, and ssh connection.
If you're looking to connect through a jump host to other machines behind that server, you may want to explore SecureCRT's Dependent Session functionality.

Attached Images
File Type: png SCRT_8.7+_LocalShell_WSL_bash.png (11.7 KB, 1429 views)
Jake Devenport
VanDyke Software
Technical Support
YouTube Channel:
Reply With Quote