PowerShell's capabilities allow you to create scripts by combining multiple commands. The PowerShell script has an extension of .ps1. By default, you will not be allowed to execute a PowerShell script. This is due to the default execution policy setting in PowerShell that prevents the execution of PowerShell scripts. The execution policy determines the conditions under which PowerShell scripts are executed. By default, the execution policy is set to "Restricted", which means that a PowerShell script (.ps1) cannot be executed, but you can still execute individual commands. For example, when the Write-Host "Hello World" command is saved as a PowerShell script (hello.ps1) and executed, you get the following message stating that running scripts is disabled. This is due to the execution policy setting:

PS C:> .hello.ps1
.hello.ps1 : File C:hello.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ .hello.ps1
+ ~~~~~~~~~~~
+ CategoryInfo : SecurityError: (:) [], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess

The execution policy is not a security feature; it's just a control to prevent users from accidentally executing scripts. To display the current execution policy setting, you can use the following command:

PS C:> Get-ExecutionPolicy
Restricted

You can change the execution policy setting using the Set-ExecutionPolicy command (provided you are executing the command as Administrator). In the following example, the execution policy is set to Bypass, which allows the script to run without any restriction. This setting can be useful for your analysis if you come across a malicious PowerShell script and if you would like to execute it to determine its behavior:

PS C:> Set-ExecutionPolicy Bypass
PS C:> .hello.ps1
Hello World