Fix 'PowerShell Not Recognized as Internal or External Command'
If you see the error 'powershell' is not recognized as an internal or external command
Checklists for software errors, setup, and tool workflows.
1. Reproduce
2. Isolate
3. Apply
4. Verify
Latest checklists
View listHow to Bypass 502 Bad Gateway in PowerShell Script
When a PowerShell script hits a 502 Bad Gateway error from a web API or server, the script usuall...
Fix Corrupted or Missing Windows Terminal settings.json
If Windows Terminal fails to open, shows a blank window, or displays an error about a missing or ...
Fix OneDrive File Locked by Office Document Sync Issue
You open an Office file from OneDrive and see an error that the file is locked or in use by anoth...
Repair Windows Security Installation via Command Prompt
Windows Security (formerly Windows Defender) can sometimes fail to open, show blank screens, or r...
Fix Windows Activation Command Not Found After Update
After a Windows update, you might run into a situation where the activation command (like s...
Topic paths
Quick titles
GitLab Runner Configuration for Queued JobsPowerShell Port Conflict Troubleshooting ChecklistComplete Outlook Migration Despite Large PSTTroubleshooting Slow PowerShell Backup and RestoreFix PowerShell Script Blocked ErrorHow to Resolve 502 Gateway Error in Windows SecurityFix Task Scheduler Update Error 0x80070005OneDrive Not Syncing After Windows 10 Update – Fixes