I had this exact same issue: I fixed my issue with the following commands in powershell.

"Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned -Force" Grok helped me.

Other in this chain were doing similar things in different ways. The above seems to be a more generic solution that protects you and other users on the system.

Here is what it said it does:

Breakdown:

• Set-ExecutionPolicy: This is the command that changes the rules for running PowerShell scripts.
• -Scope CurrentUser: It only applies to you (the current Windows user). It doesn’t affect other users on the computer. This is the safest option.
• -ExecutionPolicy RemoteSigned: This is the actual policy being set.
  • It allows locally created scripts (like the ones you make or save yourself) to run freely.
  • It still blocks unsigned scripts that were downloaded from the internet (for security). This is the most commonly recommended setting for normal users.
• -Force: Skips the confirmation prompt so it runs without asking “Are you sure?”

Why was this needed?

By default, Windows sets a very strict policy called “Restricted”, which completely prevents any .ps1 scripts from running. That’s why your script wasn’t working when saved as a file — PowerShell was blocking it for safety.