RunAsTI.reg feature to optionally open Terminal doesn't open ANY console with Build 26100 LTSC/IoT with manually installed Terminal

[espanafly]

== Feature that's broken ==

After installing the Terminal app into Windows 11 build 26100 LTSC/IoT and choosing "PowerShell / Terminal" from the context menu, nothing happens. Neither the Terminal or a PowerShell console opens.

== What's supposed to happen ==

As of 2022.04.07, RunAsTI.reg has a "Use-Terminal-if-installed" feature which is supposed to open the Terminal if it's installed.

== "Work-around" (regression) ==

Remove the 2022.04.07 "Use-Terminal-if-installed" feature
After performing the regression step, choosing "PowerShell / Terminal" opens the PowerShell console even if the Terminal is installed

== How to perform the work-around ==

Use @he3als pull request version: Capitalise TrustedInstaller & PowerShell for RunAsTI

Alternative Kludge regression approach

This alternative regression, also works, but @he3als pull request version is a proper solution and also fixes some typos.

==== modify line 113 ===
-- From: ---
"31"=" $env:wt='powershell'; dir "$env:ProgramFiles\WindowsApps\Microsoft.WindowsTerminal*\wt.exe" -rec|% {$env:wt='"'+$.FullName+'" "-d ."'}"
--- to ---
"31"=" $env:wt='powershell'; {$env:wt='"'+$.FullName+'" "-d ."'}"