Set-ExecutionPolicy -ExecutionPolicy default -Scope CurrentUser
also works but deployment workbench still opens.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
PS C:\Users\19163> Set-ExecutionPolicy RemoteSigned -Scope CurrentUser
Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose
you to the security risks described in the about_Execution_Policies help topic at
https:/go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy?
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "N"):
setting this to yes lets you run deployment workbench however,.....
???Once this is ran can you auto default it back if your done useing Deployment Workbench???
this is a security risk so can we default the policy all at once?
much like SFC/Scannow checks for issues
a Policy scanner that checks with a default version for changes
!!!Default and restricted do not lockout Deployment workbench again!!!
see once it was changed it stayed even if it displays restricted again.
I had a error like this before changing the execution policy. If I defaulted it how come when I change it back it no longer has this error?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi and thanks for reaching out. My name is William. I'm a Windows technical expert. I'll be happy to help you out today.
Yes, you can set it back to default, which is restricted using this command: Set-ExecutionPolicy -ExecutionPolicy Restricted -Scope CurrentUser
Can you clearly explain what it is that does not answer your question?
Deployment bench is an MMC. You can run it our any other process from PS. That has nothing to do with PS script.
Yes I have set it back however deployment workbench still runs is there a way to test to make sure this is restricted again outside of what is in the command line?
thanks for the reply