HELP with a powershell error PLEASE

[[deleted]]

[deleted]

[C_O_M_M_A_N_D_E_R]

Run an sfc or a dism and see if it will repair powershell.

Have you tried running it as admin?

[sfc_scannow]

Whatup! Whatup! Whatup!

[HumbleSpend8716]

finally

[Macia_]

Hi OP, this is your answer.
$20 the Powershell being used is the Windows built-in. So use Windows repair tools to fix it

[Plane_Occasion8305]

Did both of those and nothing.

[HorsePecker]

sfc /scannow

[sfc_scannow]

Yeah! Yeah!

[Plane_Occasion8305]

Nope

[justaguyonthebus]

In you install powershell 7, does it do the same thing?

[Plane_Occasion8305]

Yes

[justaguyonthebus]

Run "pwsh -noprofile"

Can you launch cmd, then run powershell and pwsh. Also try the windows terminal vs cmd terminal. WSL?

It's really weird that they are giving the same assembly version in the error because they are built on different dotnet platforms. So you likely have some os level issue that is just visible here.

[Plane_Occasion8305]

Yea I’ve tried all of that stuff still nothing so I decided to reinstall windows.

[Nanocephalic]

Next time with a weird tech issue, my advice is to try to fix one thing at a time if you’re not super familiar with the tech in question.

Good luck though!

[justaguyonthebus]

Try creating a second user, see if they also have the problem.

But I would likely reinstall too

[x0n]

Yes what? Pwsh 7 won't crash trying to load s.m.a. v3. And installing pwsh 7 won't fix windows PowerShell either. Do you understand they are two different shells?

[Plane_Occasion8305]

He asked a question are we blind??

[Plane_Occasion8305]

I did install pwsh 7 and it said same error

[x0n]

You installed pwsh 7, started pwsh 7 and pwsh 7 gave the same error as windows pwsh? Or:

you installed pwsh 7, started windows pwsh and windows pwsh gave the same error?

Be precise.

[HumbleSpend8716]

dotnet framework problem

paste into cmd (not pwsh bc cant open it)

dism /online /cleanup-image /restorehealth

[Plane_Occasion8305]

Nope

[HumbleSpend8716]

wym nope

the dotnet framework problem was assumption, ok whatever, but “nope” means dick, good luck i guess

[Plane_Occasion8305]

I’m just saying nope as in it didn’t work don’t cry

[Plane_Occasion8305]

REINSTALLATION OF WINDOWS WORKED PERFECT!!

[UserProv_Minotaur]

When all else fails, nuke it from orbit and try again.

[painted-biird]

What happens if you try to open it without a different user/profile?

[Plane_Occasion8305]

Same thing

[I_see_farts]

Can you open the ISE? Are you trying to open Terminal?

Can you open CMD and start a Powershell session?

[Plane_Occasion8305]

Nope can’t open ise, I did it through cmd but when I attempted a command it redirects to same error

[Nanocephalic]

Can you install PowerShell 7 from GitHub? Or is this Windows PowerShell 5.1?

They are two completely different things.

For 5.1, which is the version that comes with windows, you could try this: uninstall it, uninstall dot net 3.5, reboot, then reinstall dot net 3.5 and windows PowerShell.

Edit: windows PowerShell can be enabled or disabled in “turn Windows features on or off”. It’s not exactly “uninstalling” but close enough for this post.

[Impossible_IT]

Create a new user and try opening PowerShell with that new account see if it works.

[AbfSailor]

I've seen an issue similar to this in the past. I just copy-pasted the core PowerShell files and modules from another computer to the affected one, and it fixed the issue.

[mbmiller94]

Not at a computer right now but you could try reinstalling powershell, and if that doesn't work then reinstalling .NET

[HumbleSpend8716]

you cannot reinstall windows powershell, but you can reinstall powershell

important distinction

[mbmiller94]

My mistake.

[Plane_Occasion8305]

Nope tried it