0028e439b5
* cleaned up typo, fixes, grammatical and other related fixes (#2) * typo in Lightshot app name * remove trailing comma in applications.json * consistent capitalization of Windows, WinGet - only user-facing text - includes update to devdocs-generator.ps1, so docs for tweaks modifying registry will have `Windows settings` rather than `windows settings` * various fixes for typos, style, punctuation and capitalization * capitalize 'AM' * Update README.md change formatting for GitHub UI interaction form code format (` `) to bold md Co-authored-by: Jay <65828559+Jay-o-Way@users.noreply.github.com> * typos and wording in docs --------- Co-authored-by: Jay <65828559+Jay-o-Way@users.noreply.github.com>
2.8 KiB
title, toc
| title | toc |
|---|---|
| Known Issues | true |
Download not working
If https://christitus.com/win is not working, or you want to download the code from GitHub directly, you can use the direct download link:
irm https://github.com/ChrisTitusTech/Winutil/releases/latest/download/Winutil.ps1 | iex
If it still isn't working in your region, it may be due to temporary ISP or network filtering of GitHub content domains. This has been reported by some users in India in the past. See: Times of India.
If you are still having issues, try using a VPN, or changing your DNS provider to one of the following two providers:
| Provider | Primary DNS | Secondary DNS |
|---|---|---|
| Cloudflare | 1.1.1.1 |
1.0.0.1 |
8.8.8.8 |
8.8.4.4 |
Script Won't Run
If your PowerShell session is running in Constrained Language Mode, some scripts and commands may fail to execute. To check the current language mode, run:
$ExecutionContext.SessionState.LanguageMode
If it returns ConstrainedLanguage, you may need to switch to FullLanguage mode or run the script in a session with administrative privileges. Be aware that some security policies may enforce Constrained Language Mode, especially in corporate or managed environments.
If the download fails:
- Try the direct GitHub link:
irm https://github.com/ChrisTitusTech/Winutil/releases/latest/download/Winutil.ps1 | iex
- Force TLS 1.2:
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
irm "https://christitus.com/win" | iex
Note
On Windows 11, you usually do not need the TLS 1.2 command. Use it only if you encounter download or security protocol errors.
Execution Policy Error
If you see an execution policy error when running the downloaded script, you can allow the current session to run unsigned scripts with this command:
Set-ExecutionPolicy Unrestricted -Scope Process -Force
irm "https://christitus.com/win" | iex
This only changes the policy for the current PowerShell process and is safe for one-off runs.
Interface Doesn't Appear
If Winutil downloads, but the GUI does not open or appear, try these steps:
- Check if your antivirus or Windows Defender is blocking the script — add an exclusion if necessary.
- Ensure you launched PowerShell / Terminal as Administrator.
- Close and reopen PowerShell, then run the launch command again.
- If the script still doesn't show, try running the script in a visible PowerShell window (avoid background/silent shells) to observe output and errors.