Windows Terminal proxy error fix for Windows 11
The Problem
The Windows Terminal opens on startup with a proxy error, causing issues for users who rely on this feature. This issue affects users who have recently added Git Bash to their Windows Terminal configuration.This error can be frustrating, as it prevents users from accessing the terminal and performing tasks efficiently. In this guide, we will walk you through the steps to resolve this issue.
🛑 Root Causes of the Error
The primary cause of this issue is the addition of Git Bash to the Windows Terminal configuration. This adds a new process that requires proxy settings, which are not being written correctly.Another possible cause is an incorrect or missing proxy setting in the Windows Terminal configuration file.
🚀 How to Resolve This Issue
Resetting the Windows Terminal Configuration
Step 1: Open the Windows Terminal and press `Ctrl + A` to open the command prompt. Then, type `reset` and press Enter to reset the terminal configuration.Step 2: Next, type `settings.json` and press Enter to edit the settings file. Delete or comment out any lines that reference Git Bash or proxy settings.Step 3: Finally, save the changes and exit the terminal. Restart your computer to test if the issue is resolved.
Updating the WinHTTP Proxy Settings
Step 1: Open the Command Prompt as an administrator by right-clicking on the Start button and selecting `Command Prompt (Admin)`.Step 2: Type `netsh winhttp set proxy` and press Enter to reset the WinHTTP proxy settings. Follow the prompts to select a proxy server if necessary.Step 3: After completing these steps, restart your computer to test if the issue is resolved.
💡 Conclusion
To resolve the Windows Terminal opening on startup with a proxy error, you can try resetting the terminal configuration or updating the WinHTTP proxy settings. If neither method resolves the issue, further troubleshooting may be necessary. By following these steps, you should be able to resolve this common issue and regain access to your terminal.
Full step-by-step guide with screenshots: Read the complete fix here
Found this helpful? Check out more verified tech fixes at TechFixDocs













