Powershell scripting permissions

[smellhole]

Hi it's me again.

This time I have a weird problem with launching powershell and scripting.

I made a shortcut for powershell on my desktop. I then dragged and dropped said shortcut to the freecommander toolbar I set up for it.



The shortcut on the desktop opens up powershell just fine, since I long ago enabled scripting (I use powershell a lot).



The same shortcut on the freecommander toolbar is not so dandy.



Any idea why this is?

Thanks.

[smellhole]

I was noodling around with this and discovered that the same error results when powershell is launched from anywhere within freecommander.

Weird.

[Forez]

Maybe this has something to do along the lines with my issue: https://freecommander.com/forum/viewtop ... 281#p35281
?

Something to do with the fact that there are two powershell.exe files on the system drive of Window 10?

C:\Windows\System32\WindowsPowerShell\v1.0

C:\Windows\SysWOW64\WindowsPowerShell\v1.0



O maybe you just have to disable all of Windows security features; starting with UAC?

[horst.epp]

This is no problem of FC.
I can run Powershell.exe from any dir in my system.
Using FreeCommander XE 2021 Build 841 64-bit donor

[Forez]

Maybe it has something to do with User Account Control?

Or you accidentally blocked PowerShell in FreeCommander with your HIPS software?