Master Windows Shell Scripting Reliability

Windows Shell Reliability Patterns collects best practices for running commands on Windows via PowerShell and CMD, covering seven recurring failure classes. Encoding & Redirection: PowerShell 7.4+ preserves the byte stream on stdout redirection, so UTF-8 conversion workarounds (Get-Content log.txt | Set-Content -Encoding utf8 log_utf8.txt, or 2>&1 | Out-File -Encoding UTF8 log.txt) are only needed for older PowerShell versions or already-corrupted logs - prefer native redirection as-is on 7.4+. Paths & Spaces: Windows paths often contain spaces, so both absolute and relative paths must always be quoted (dotnet build "src/my project/file.fsproj"), and if an executable path itself starts with a quote, PowerShell requires the call operator & before it.

Use it when developing or debugging scripts and automation that run on Windows, especially when file paths, character encoding, or standard CLI tools are involved.

Common Binary & Cmdlet Pitfalls maps CMD-style commands to their more robust PowerShell cmdlet equivalents: del /f /q file -> Remove-Item -Force file, copy a b -> Copy-Item a b, move a b -> Move-Item a b, mkdir folder -> New-Item -ItemType Directory -Path folder - CLI aliases like ls/cat/cp are fine interactively but full cmdlets are more robust in scripts. Dotnet CLI reliability tips: dotnet build --no-restore for fast iteration (skips redundant NuGet restore), dotnet build --no-incremental for a guaranteed-clean build, and Start-Process dotnet -ArgumentList 'run' -RedirectStandardOutput output.txt -RedirectStandardError error.txt to launch a background process without blocking the shell while still capturing logs. Environment variables differ by shell: $env:VARIABLE_NAME in PowerShell versus %VARIABLE_NAME% in CMD. Windows' default 260-character path limit can be worked around with the extended path prefix \\?\C:\Very\Long\Path\....

A troubleshooting table maps common shell errors to fixes: "The term 'xxx' is not recognized" means the path isn't in $env:PATH (use an absolute path or fix PATH); "Access to the path is denied" means a file is in use or permissions are wrong (stop the process or run as Admin); an encoding mismatch means older shell redirection rewrote the output (re-export as UTF-8 or capture with 2>&1 | Out-File -Encoding UTF8).

Developers writing or debugging Windows automation scripts who keep hitting the same handful of platform-specific gotchas - quoting, encoding, cmdlet choice, path length - and want the fix for each looked up rather than rediscovered by trial and error each time a script moves from a Linux/macOS dev environment onto a Windows target.