Windows PowerShell 5.1 and remote sessions

Most organizations run both PowerShells and will for years. DetentShell makes that official: a persistent Windows PowerShell 5.1 session opens in a tab beside PowerShell 7, so the legacy module and the new tooling live in one window. Remote administration goes over WinRM, the transport IT already governs and audits — the tool adds a workbench around your existing remoting policy, not a new pathway through it.

File > New Windows PowerShell 5.1 Session starts an out-of-process 5.1 with streaming output and durable state; the menu item disables itself where 5.1 isn’t installed. The engine picker is disabled inside 5.1 sessions since every run there is 5.1. Start-Job works natively in 5.1; the hosted 7 engine points you at the bundled Start-ThreadJob instead. Remote tabs (Ctrl+Shift+R) are Enter-PSSession-style over WinRM; the tab title carries user@computer permanently, and the credential dialog keeps the password as a SecureString from the first keystroke. A dead 5.1 child process reports itself in plain English until you open a fresh session.

Windows PowerShell 5.1 is the older PowerShell that still ships with Windows, and some scripts and modules only work there. DetentShell lets you open it as its own tab, so you don’t have to choose. The tab’s title tells you which PowerShell you’re in. For working on another computer, a remote tab connects over the network, and its title always shows which machine you’re on — worth a glance before anything important.

Remote activity rides the organization’s governed WinRM channel with its existing audit trail, and the tab’s always-visible user@computer title keeps it clear which machine a command is going to.