If you ever experienced this I’m sure you know how irritating that may be.
To fix it you have to run the command below to run Set-ExecutionPolicy and change the Execution Policy setting.
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
The command Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass sets the execution policy for the current PowerShell process to Bypass, which means that nothing is blocked and there are no warnings or prompts. This allows you to run any PowerShell script or command without any restrictions. However, this setting only applies to the current PowerShell process and does not affect the execution policy for other processes or scopes.
Some possible implications of using this command are:
You can run PowerShell scripts or commands that are not digitally signed or that come from untrusted sources, which may pose a security risk.
You can bypass any Group Policy settings that enforce a more restrictive execution policy for your system or user account.
You can avoid getting errors or prompts when running PowerShell scripts or commands that require a higher execution policy.
You can temporarily change the execution policy for a specific task without affecting the default execution policy for your system or user account.
ThatSolutionsGuy.com 