Windows 10: How to stop powershell 5 from trying to evaluate script syntax before actual script execution?

How to stop powershell 5 from trying to evaluate script syntax before actual script execution?Not sure this is even possible? I have a bit of code that checks the version major number and if it is below 7, the script spawns its-self again using 'pwsh'. This works. Powershell 5 invokes powershell 7, the script runs, all is good. But... there is a gotcha, it just so happens I am using a bit of syntax in my script that is supported in powershell 7 but not 5. Even before powershell 5 tries to execute any script code, it throws errors because of this syntax. For example...PS C:\Automation&g

:)

 

Unable to execute the Powershell scripts on Windows 11

Hi,

I am trying to execute the "Powershell" scripts on Windows 11 which was working great in Windows10.

But, I am unable to execute it on Windows 11.

So, I have tried executing the PS1 script is multiple ways,

1. Right click -> Run Powershell

=> Powershell screen was blinked and gone.

2. Launched the Powershell cmdlet with administrator and navigated to the script file location. Then executed the PS1 file.

=> refer the image for the error when we execute the script.

3. Finally, I tried changing the execution policy using the Powershell cmdlet and I was able to execute my script (which was working in win10).

Here, my question is the same script is working fine with Win10 without changing any policy. Then why it is not working with Win11 .

1. Why it is required to change the policy ?

2. Is it possible to execute the script in win11 without changing the policy ?

3. What would be the root cause ? why is is not allowed ?

4. What is the default execution policy for win 10 and win11 ? how it differs on execution?

Please help me to understand the Powershell behavior and root cause of the problem.

 

Unable to execute the Powershell scripts on Windows 11

In Windows 10, when I execute the PowerShell script, Execution policy is "Undefined" and I could see the "disable" error message .

Even though, I am able to execute the PowerShell script content.

 

Powershell Scripts in the Windows 10 OS and script execution policy of "Allow only Signed scripts"

We have the group policy " Turn on Script execution" enabled and set to "Allow only Signed scripts".

Will this affect the powershell scripts used in the Windows 10 operating System or does windows have something inbuilt that overrides the settings we apply. I'm thinking that it would block even the W10 built in scripts.

An example of what I am talking about are the 246 .ps1 files in the various diagnostic directories in c:\windows\diagnostics\system\ . our diags never come back with issues even when deliberately disabling components before running.

other areas that Powershell scripts live that I have found with a quick search -

C:\Windows\WinSxS\wow64_microsoft.powershell.odatautils_31bf3856ad364e35_10.0.17763.1_none_d60dcab1d9234fab

C:\Program Files (x86)\WindowsPowerShell\Modules\Microsoft.PowerShell.Operation.Validation\1.0.1\Diagnostics\Comprehensive

C:\Program Files\WindowsPowerShell\Modules - various folders in here.

Do we need to sign all powershell scripts that come with the OS?

Does Microsoft have a method of doing this?

Is there a list of script files that come with the OS so we don't just do a sign all approach, then find we have signed malware files.

we could probably configure something in the build task sequence to sign what is there initially. Is there any plan in place for Microsoft to start signing their scripts?

Will this be an ongoing process as updates are applied and files replaced, do we need to have a process in place to sign all PS1 files in the OS?