Windows 11 troubleshooting
WinUtil and PowerShell Execution Policy
Understand PowerShell execution policy without making persistent security changes just to start a utility.
Quick answer
Execution policy is one PowerShell control, not a guarantee that scripts are safe. Prefer verified sources and the least-permissive change.
Step-by-step checklist
Check the current state
Open PowerShell and run Get-ExecutionPolicy -List to see which scopes are configured. MachinePolicy or UserPolicy can be controlled by an administrator.
Distinguish errors
A blocked script, an unavailable URL, and a command that is not recognized need different fixes; record the original terminal output.
Prefer trusted instructions
Verify the source and follow published project guidance; do not globally lower execution policy, disable endpoint protection, or run unknown remote scripts.
Validate afterward
When troubleshooting ends, check Get-ExecutionPolicy -List again and ensure no unexpected persistent policy was introduced.
How to verify success
Repeat the original task under the same conditions, record the Windows build and exact error or result, and confirm Windows Update, security protection and core applications still behave as expected. If the result is worse, undo the last documented change rather than applying multiple unrelated fixes.
When to stop and ask for help
Stop when encryption recovery keys are unavailable, a work device is managed, an update contains an unfamiliar error code, or boot and recovery tools are affected. Use trusted project documentation and Microsoft support guidance for the specific build and message.
Reference points
See the WinUtil project repository and Microsoft Windows documentation for current commands and feature limitations. This checklist does not claim an independently verified fix for every system configuration.