A newish (Sept) install of win10 Pro 22H2 (OS Build 19045.6466) on new MSI mobo w/ AMD Ryzen 5 5500GT
The native Powershell was working fine for awhile. After a period of time when I didn’t use it, one day I tried to take ownership of a particular file using Shawn Brink‘s context menu script, which uses powershell. It failed with the symptom in the title. I can’t pin down when things might have changed but clearly something did.
Tried running powershell from elevated CMD, with this result:
=======
C:Usersuser1>powershell
‘powershell’ is not recognized as an internal or external command,
operable program or batch file.
C:Usersuser1>C:WindowsSystem32WindowsPowerShellv1.0powershell
Windows PowerShell terminated with the following error:
The type initializer for ‘System.Management.Automation.Utils’ threw an exception.
C:WindowsSystem32WindowsPowerShellv1.0>powershell.exe -Command Get-Process;
Windows PowerShell terminated with the following error:
The type initializer for ‘System.Management.Automation.Utils’ threw an exception.
========= note: the type initializer error message conveys nothing to me =====
Have checked in gpedit for software restriction policies: none
Also have installed Powershell 7. It runs fine.
Am looking for light! Thanks — whawn
