You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In normal terminal application like Windows terminal, can correctly read user path or system path, but sshx cannot instead.
Try other way
I tried pwsh instead of fish, I got a new problem:
Process terminated. The type initializer for 'System.Management.Automation.Runspaces.InitialSessionState' threw an exception.
at System.Environment.FailFast(System.String, System.Exception)
at Microsoft.PowerShell.UnmanagedPSEntry.Start(System.String[], Int32)
at Microsoft.PowerShell.ManagedPSEntry.Main(System.String[])
System.TypeInitializationException: The type initializer for 'System.Management.Automation.Runspaces.InitialSessionState' threw an exception.
---> System.ComponentModel.Win32Exception (126): The specified module could not be found.
at System.Management.Automation.Internal.SecuritySupport.GetSaferPolicy(String path, SafeHandle handle)
at System.Management.Automation.Security.SystemPolicy.TestSaferPolicy(String testPathScript, String testPathModule)
at System.Management.Automation.Security.SystemPolicy.GetAppLockerPolicy(String path, SafeHandle handle)
at System.Management.Automation.Security.SystemPolicy.GetLockdownPolicy(String path, SafeHandle handle)
at System.Management.Automation.Security.SystemPolicy.GetSystemLockdownPolicy()
at System.Management.Automation.Runspaces.InitialSessionState..cctor()
--- End of inner exception stack trace ---
at System.Management.Automation.Runspaces.InitialSessionState.CreateDefault2()
at Microsoft.PowerShell.UnmanagedPSEntry.Start(String[] args, Int32 argc)
And I tried cmd instead, telling me cannot find executable application on the path.
The text was updated successfully, but these errors were encountered:
The point I want to convey is that all of these terminals have the problem of not inheriting Windows system environment variables.
PowerShell is actually more problematic, but I don't use it very often.
Description
In normal terminal application like Windows terminal, can correctly read user path or system path, but sshx cannot instead.
Try other way
I tried
pwsh
instead offish
, I got a new problem:And I tried
cmd
instead, telling me cannot find executable application on the path.The text was updated successfully, but these errors were encountered: