Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All powershell versions dont work #17467

Open
leosordai opened this issue Jun 24, 2024 · 2 comments
Open

All powershell versions dont work #17467

leosordai opened this issue Jun 24, 2024 · 2 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-External For issues that are outside this codebase

Comments

@leosordai
Copy link

Windows Terminal version

1.20.11381.0

Windows build number

22000.2538

Other Software

No response

Steps to reproduce

well there really isnt a step to reproduce this because its a personal issue with powershell that others did experience too but they didnt have a solution that worked for me, all i did was open powershell and it just closed immediatly after that

Expected Behavior

I was expecting powershell to open and work completely fine

Actual Behavior

Poweshell from windows opened but it closed immediatly so i tried downloading other versions of powershell like powershell 7 it opened but it said :
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.Management.Automation.PSInvalidCastException: Cannot convert value "C:\PATH_Programs\0" to type "System.UInt32". Error: "The input string 'C:\PATH_Programs\0' was not in a correct format."
---> System.FormatException: The input string 'C:\PATH_Programs\0' was not in a correct format.
at System.Number.ThrowFormatException[TChar](ReadOnlySpan1 value) at System.UInt32.Parse(String s, NumberStyles style, IFormatProvider provider) at System.ComponentModel.UInt32Converter.FromString(String value, NumberFormatInfo formatInfo) at System.ComponentModel.BaseNumberConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value) --- End of inner exception stack trace --- at System.Management.Automation.LanguagePrimitives.ConvertStringToInteger(Object valueToConvert, Type resultType, Boolean recursion, PSObject originalValueToConvert, IFormatProvider formatProvider, TypeTable backupTable) at System.Management.Automation.LanguagePrimitives.ConversionData1.Invoke(Object valueToConvert, Type resultType, Boolean recurse, PSObject originalValueToConvert, IFormatProvider formatProvider, TypeTable backupTable)
at System.Management.Automation.LanguagePrimitives.ConvertTo(Object valueToConvert, Type resultType, Boolean recursion, IFormatProvider formatProvider, TypeTable backupTypeTable)
at System.Management.Automation.LanguagePrimitives.ConvertTo[T](Object valueToConvert)
at System.Management.Automation.Security.SystemPolicy.GetDebugLockdownPolicy(String path)
at System.Management.Automation.Security.SystemPolicy.GetSystemLockdownPolicy()
at System.Management.Automation.Runspaces.InitialSessionState..cctor()
--- End of inner exception stack trace ---

so im really frustrated about this because i tried everything my mind could think of.

@leosordai leosordai added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 24, 2024
@DHowett
Copy link
Member

DHowett commented Jun 24, 2024

I'm sorry, this might be better suited for the PowerShell repository. However, I wonder if your PATH environment variable contains data that PowerShell is unable to parse.

Can you open Command Prompt and run the command path?

@DHowett DHowett added Resolution-External For issues that are outside this codebase Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jun 24, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Jun 28, 2024
@leosordai
Copy link
Author

leosordai commented Jun 28, 2024 via email

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. labels Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-External For issues that are outside this codebase
Projects
None yet
Development

No branches or pull requests

2 participants